Issue Data
|
Issue #21291: Nuclear Physicist bugged
Steam users have found a bug with the perk nuclear physicist, the details are in the quotation:
---- Quote: So I just came back to the game to check out Nuka World, and I'm noticing this perk isn't behaving how it used to. I use the gatling laser, and with rank 3 of this perk and the repair bobblehead, shooting a full clip of 500 shots should drain a full fusion core to 54%, but it's draining my cores to 33% instead. It's on a new character. I haven't even played Nuka World on any character yet. My old character is fine just like yours is, but new characters experience this bug with gatling lasers. They must have changed something in a patch at some point. I found something interesting about the perk relating to being used in power armor though. Even further investigation with the creation kit revealed that rank 1 of Nuclear Physicist ACTUALLY increases fusion core duration when used in power armor by 50% instead of 25%, rank 2 doubles it instead of increasing it by 50%, and rank 3 brings it back down to 50% instead of doubling it. Someone at Bethesda was drunk when they messed with this perk. ---- |
Yeah, can confirm that last paragraph sorta, the bug in question is in the spell tied to the perk. It only checks for ranks 1 & 2, and applies the bonuses of 2 and 3 to them.
There's an additional bug with it too: rank 2 is giving a boost to fusion core ammo capacity, but this bonus stacks with rank 3 due to a missing perk check.
There's an additional bug with it too: rank 2 is giving a boost to fusion core ammo capacity, but this bonus stacks with rank 3 due to a missing perk check.
Right, so, I can't really tell what the actual problem is here so the only thing I've touched so far is to fix the level 2 and 3 perks stacking with each other when they're not supposed to.
I don't even know why there's an ability associated with this when it looks like the perk itself ought to be handling it just fine.
I don't even know why there's an ability associated with this when it looks like the perk itself ought to be handling it just fine.
This ticket apparently was not closed as "fixed" when v2.0 hit the stands.
Showing Comments 1 - 3 of 3