Grim Feast and weapon swapping

In the last patch there was a change to how energy shield works with weapon swapping. Basically if you have 5k energy shield on one weapon, then swap to another weapon with a 10k max, it won't be at 10k, it will be at 5k.

I assume this is an intended change, so this post is not about this, it's about a minor detail in the implementation that causes annoyance and might be a bug.

1. Have 2 weapon sets, one with e.g. 8k/4k and one with 10k/5k energy shield max (the problem happens as long as the two sets have a different max ES).
2. Be at 10k/5k with Grim Feast.
3. Swap weapons. Energy shield will drop to 8k/4k. This is expected - 8k is the max on this weapon set, so the value had to go down from 10k to 8k.
4. Swap weapons again. Energy shield won't proportionally go up to 10k/5k - it will now be at 8k/5k - this is the recent change. Assuming this is intended by the devs, everything is still as expected.
5. Swap weapons again -> this is what I think is a bug -> energy shield will go down to around 7k/4k. But there is no reason for this. You made the change where the shield doesn't proportionally go up, it also shouldn't proportionally go down. This weapon set's max is 8k, there is no reason for it to drop to 7k.
6. If you keep swapping, your ES will drop down to 4k eventually.

Basically if you weapon swap a lot it's better to find a lower ES item for your "better" set to bring it down in line with the lower ES set, because the best outcome (taking the least amount of "weapon swapping damage") happens when the ES values are as close together as possible. If the values are identical, then the problem is avoided completely.

Or in other words, the newly added "weapon swapping damage" you take is proportional to the difference between the max ES values on the two sets.

The solution is that there is no reason for ES to proportionally drop when swapping to a lower ES set, now that it doesn't proportionally grow in the other direction any more. Of course, if it has to drop to respect the max value (10k->8k), that's fine, but it shouldn't drop even further (8k->7k). So in step #5 it should go from 8k/5k to 8k/4k.
Last edited by pasanac#7823 on Jan 19, 2025, 11:39:18 PM
Last bumped on Jan 19, 2025, 11:43:50 PM
This does not look like intended, as it does not happen with non overflown ES it seems.
Just to add some more info on how this affects gameplay and gearing decisions now that I've "fixed" my problem through counterintuitive gearing.

I was taking hundreds of "damage" from weapon swapping as described already, so I decided to find a new focus that would give me the same ES I have on my other set which is 4594 (without Grim Feast).

Eventually I managed to hit 4595 (just a 1 difference compared to the other set) by buying a specific focus and upgrading its quality to exactly 18% for a total of 80 ES.

Now I lose only 1 ES from weapon swapping which is minor, I would need to swap back and forth a thousand times in a row to take 1k damage. If I keep swapping the ES goes 9190->9188->9187->9186->9185->9184... The bolded part is what I believe to be the bug (or poor design) - but I've reduced its magnitude to just 1 damage by "optimizing" my focus ES value.

For comparison, if I equip a 315 ES focus (which should be a better item) instead of the 80 ES one, and I keep swapping weapons, the ES goes 11076->9188->8244->7300->6356..., with the bolded part being the bug. Effectively, I take around a thousand damage any time I swap to my off-set and back, just because my off-set ES is too high! If I try a lower ES instead (like 40 instead of 80), again I lose ES from swapping, now from my off-set ES being too low. 79-80 ES is the "sweet spot".

I feel like needing to have the the same ES on both weapon sets and being punished for equipping a better item is really weird. The fact that my focus will become worse if I upgrade its quality from 18% to 20% is also weird. The bolded numbers should all be 9188 in both cases.
Last edited by pasanac#7823 on Jan 19, 2025, 11:42:59 PM
This is very likely not intended. Myself and others had this bug prior to the patch, but it resolved itself. Now it appears to be permanent.

Report Forum Post

Report Account:

Report Type

Additional Info