iconic/stash weapon crafting specs not dropping

[FaythsRequiem]

I've killed both Ayer and Sidorova, but the crafting specs for Psalm 11:6 and Buzzsaw wasn't in their inventories. Anyone else run into same issues, whether with these two or with other stash crafting specs not dropping?

Makes it tough to complete the stash walls if I can't craft/get the weapons needed to do so :/

[SirWtf]

Same happend to me. I got drop for Comrades Hammer but when I opened my inventory nothing.

[FaythsRequiem]

ok, I just KO'd the mech needed to get the Headsman crafting spec; saw the spec in it's inventory before looting it, but it does not show up at all in my crafting/inventory at all. Which means there's effectively no way for ppl who are encountering this bug to complete stash weapon collection until it's fixed.

[arti_llery]

Originally posted by SirWtf:

Same happend to me. I got drop for Comrades Hammer but when I opened my inventory nothing.

You get the blueprint for it. Check crafting. Blue weapons.

[FaythsRequiem]

Originally posted by arti_llery:

Originally posted by SirWtf:

Same happend to me. I got drop for Comrades Hammer but when I opened my inventory nothing.

You get the blueprint for it. Check crafting. Blue weapons.

Nope. You can see the spec/blueprint for it in the inventory of NPC before looting, but when you go into crafting there is nothing for those weapons. And FYI, the tier lvl/color changes depending on your lvl when looting them, which means you should check ALL weapon crafting specs to make sure you don't have it.

[Sidwa]

i do get the blueprints like headsman, wondering what messes it up, mods perhaps?

[FaythsRequiem]

I'm not using any mods, so that's not it, for me at least. At least it's not a game breaking bug, but it's still annoying.

[Resokai]

i have no mods, happened to me with psalms 11:6 too for some reason

[hugedata]

Same here for Psalm. Has this been removed from the game?

[Zoid13]

Originally posted by FaythsRequiem:

Psalm & Buzzsaw

i bought the plans from the black market vendor.
they craft as white tier for me even at level 60

[palathas]

I didn't think that plans for iconic weapons existed anymore. I started a new playthrough when PL dropped and have only been finding the actual weapon and the only way to make them better is to got to Crafting -> Upgrade tab.

Edit: Actually I found a Buzzsaw recently from a Maelstrom ganger. I can't recall where though because I don't use power weapons with my Netrunner. I'll have to look at my schematics because I've done very little crafting this playthough.

[Ishmael]

So is it just random now how you get psalm and buzzsaw? whether it´s through a vendor or a random drop?

[Unlucky]

This has been a bug in the game for pretty much as long as I can remember... :/
I was hoping they would have fixed it but yeah... ran into it myself again a few times the other day.

The cause is very simple:
If you load a game INSIDE of a mission-area where an important named-enemy has already spawned, they will NOT drop their special loot items, such as iconic weapons/blueprints.

The workaround is equally as simple:
SAVE your game OUTSIDE of all mission-areas BEFORE starting any mission and before stepping foot into the area. DO NOT kill, attack, or even go inside of the area without a save point.
( If you do go in to an area by accident then just make sure you haven't killed the named-boss yet and leave the area and do other missions for a while and it will be fine. I've done it several times and... I think? I still get everything....? I hope anyways lol )

No idea why they haven't fixed this yet. I've played the game since release day and I'm pretty sure I've known about this bug since then, or at least within that same week.

Edit: This is easily repeatable & testable with any of the named-enemy missions. I have tested it tons. The only thing I've NOT done is report the bug.... Mostly bc I was too lazy to look up how to report bugs for this game... heh. :)

[1+1=10]

Originally posted by Unlucky:

This has been a bug in the game for pretty much as long as I can remember... :/
I was hoping they would have fixed it but yeah... ran into it myself again a few times the other day.

I am very sure this was fixed in an older version but seem to be back since 2.x