Tom

I'm getting this on 2.7.3 and 2.7.2 too. VSCode OSS 1.53.2 on Linux

>How exactly would those functions determine that the attribute is uninitialized? They can just check if an attr.ib registered on the class is actually set, using `hasattr`. Just a check...

Perhaps bulkrename could use a label 'editor-wait' which falls back to 'editor', so that users can get both behaviours if they want. I like to use E key to edit...

Or maybe `bulkrename` can accept the command to edit with as an optional argument.

If players can also blink through, I vote to leave this - seems pretty rare but both cases seem like a fun(?), memorable interaction

I agree with the above comment. I like most the idea of a prompt to choose to attack a discordant ally

(3) - that is one of the ideas above: scale mail gains more armor points per enchant (1) - the idea is that the expected damage for each weapon vs...

Oh, I was thinking about absorption being proportional to incoming damage. % damage resistance, essentially

Thanks for the great comment. You're right that we are trying to solve two issues here - they are split into two lists in the original, but grouped under armor...

The most glaring problem I see is how hit effects (acid, weakening, knockback) should work. Absorption is a pretty big nerf if they work as normal.