Out of range weapon damage on crafted weapons. Anyone else getting this ?.

[RimBlock]

Hi all,

I am currently levels 30/40 and bought the BM AK74 blueprint from the BoO vendor.

I will update the number when home but the ones I have put in should give an idea of the issue.

From memory, the damage range of the weapon is listed as 8799 -> 9800.

I have now crafted it 4 times and got the following scores for damage;

• 8820
  
• 8850
  
• 8200
  
• 8600
  

The first two were just low rolls and whilst disappointing, that is the way it goes.  The last two are below the minimum damage values on the blueprint......

Has anyone else been hit with this ?.

I have screen shots I will probably upload later to give a better picture  :10_wink: .

 

[Mike87]

Yeah, it's like that for me too and others.  Sometimes you can't trust the numbers on the blueprint.  For some, the RPM and Mag size is also wrong.  I don't get how the developers have not seen this as an issue/ bug to fix.

 

[ThePassionateGamer]

Happend to me too. I hope they fix that soon because right now you can't really trust the numbers or the decricptions on the blue prints. I bought a weapon sight mod BP that had on the vendors preview of the BP "weapon damage" as a fixed bonus listed. I thought it would be great to have another option to add base damage. By that day I did not know that only magazine mods could give that bonus iirc. So I bought the BP for (at that time) alot of Phoenix Credits only to see after I used up my last "tools" for crafting one, that the listed weapon damage wasn't damage but Accuracy or something else you would not buy the BP for under normal circumstances. I was pretty upset as I noticed that error.

 

[RimBlock]

Thanks Mike.

Unbelievable this is incorrect in the fist place, it got through QnA and Beta testing and is still there after the first patch.

 

[ThePassionateGamer]

Thanks Mike.

Unbelievable this is incorrect in the fist place, it got through QnA and Beta testing and is still there after the first patch.

It was already noticed in Beta testing? Really? You are not kidding me here?

Wow that must be a new record in bad "polishing" a game for release. Man...sometimes I don't believe it how much hardcore ingorance is going on in the gaming industry. I mean correcting BP value and description bugs can't be a high priority thing on their to-do list. I can understand that. But on the other side it can't be that complex of an error to take an rocket scientist to fix. So why do they need that long to fix it I am asking myself?

 

[Xeromaus]

whatever weapon is being shown in comparison to the blueprint, swap it's mods to the wep you just crafted, and the range will be correct.

 

[ThePassionateGamer]

whatever weapon is being shown in comparison to the blueprint, swap it's mods to the wep you just crafted, and the range will be correct.

Sorry but I don't get it. The BP is influenced by a weapon and the mods that I carry?

To clarify what I mean: I was talking about the window that shows the BP and it's stats like Base Damage / RPM / Magazine size or the one thing you get everytime you craft a weapon mod, that was shown completly wrong in my case. I am not refering to the preview or comparison window you can add there to compare with a weapon you carry. Nor the crafting table.

If we talk about the same thing, please try to describe a bit more what you think is causing the wrong values. Thx

 

[MurphDog6]

Go to the crafting table and bring up your blueprint for weapon. Take note of the damage range it shows and then exit the crafting table. Go to your inventory and strip your weapons of all mods and attachments.

Re-enter the crafting table and see if the damage range, rpm, mag size etc has changed. 

That would be the best way to test this theory. I would do it now but am currently in work. Can anyone test this?

 

[Xeromaus]

Go to the crafting table and bring up your blueprint for weapon. Take note of the damage range it shows and then exit the crafting table. Go to your inventory and strip your weapons of all mods and attachments.

Re-enter the crafting table and see if the damage range, rpm, mag size etc has changed. 

That would be the best way to test this theory. I would do it now but am currently in work. Can anyone test this?

^this^. I'm not in game atm either (cooking breakfast), but my BP weps always compare to my BMAK, and the BP ranges synch up when I give the newly crafted weapon the mods/attachments from my BMAK.

Strip your equipped/shown weapon of mods/attachments before looking at the blueprint, then craft the weapon. Usually, the numbers fall within the shown ranges then.

Edit: oh, and the damage range will fluctuate with your firearms stat. I know that's been mentioned before, in other posts, but it's worth noting again here.

 

[RimBlock]

It was already noticed in Beta testing? Really? You are not kidding me here?

Wow that must be a new record in bad "polishing" a game for release. Man...sometimes I don't believe it how much hardcore ingorance is going on in the gaming industry. I mean correcting BP value and description bugs can't be a high priority thing on their to-do list. I can understand that. But on the other side it can't be that complex of an error to take an rocket scientist to fix. So why do they need that long to fix it I am asking myself?

Sorry, I meant that if it is there then presumably it has always been there.  I have no idea if it was already spotted.

I think Xeromaus has hit the nail on the head though.  I think the idea that the specs from the blueprint change depending on the mods on your current weapon (which may be your secondary and not you primary if your crafting a primary).  I would rather see the specs and then compare with my relevant stripped weapon.  Seeing the damage range, rolling and getting significantly less just adds lots of confusion.  I have scrapped 3 BM 74s that could have actually been pretty good...

Oh well.  Such is life in Massives Division.

 

[ThePassionateGamer]

Ah ok now I get what you meant.

That the firearms score is taken into the value is ok for me. That only helps to show you the values the weapon will have when you craft it with your current attributes. Bad for comparing it with other agents but still ok because what you see will be what you get so that's totally ok.

I just dislike that there are more factors that they show up on a BP that are not very obvious to notice.

I mean why did they decide to use your current mods to change the values of a not yet crafted weapon? If that was intended behavior it was another rather bad decision if you ask me.

Next time I'll check a BP and decide if I wanna buy it or not I will take a unmoded weapon into my hands to make sure the BP actually shows what I'll get once I craft it. Thx for clearing that up @Xeromaus.

 

[Xeromaus]

Ah ok now I get what you meant.

That the firearms score is taken into the value is ok for me. That only helps to show you the values the weapon will have when you craft it with your current attributes. Bad for comparing it with other agents but still ok because what you see will be what you get so that's totally ok.

I just dislike that there are more factors that they show up on a BP that are not very obvious to notice.

I mean why did they decide to use your current mods to change the values of a not yet crafted weapon? If that was intended behavior it was another rather bad decision if you ask me.

Next time I'll check a BP and decide if I wanna buy it or not I will take a unmoded weapon into my hands to make sure the BP actually shows what I'll get once I craft it. Thx for clearing that up @Xeromaus.

There's a fair debate over the mods bit.

When I craft a wep out of the blueprints damage range, it's always being compared to my BMAK. As far as base damage goes, my mag on my BMAK gives +12%. When I swap the +12% mag to the newly crafted weapon, it now falls within the range shown on the blueprint.

Others have stated that the mods don't affect anything on the blueprint and it's just a visual/UI bug in the game. Still others agree that the mods CAN affect the range.

I only know what I see.