To Reproduce
It will probably happen on every test where you want to double the Modifier that system already calculates. So when you want to move from +10 to +20 or from +20 to +40. Application ignores this value, because it is perceived not as 10+10, but "was 10, is 10 - nothing changed".
To achieve that +40 (because range is in fact point-blank, not short range) I had to:
type 10 in Modifier field, so it switched to 30
type 20 in Modifier field, now it switched to 40
With new auto-calculated modifiers it would probably be nice to have separate field for "Modifier Offset" (to add our own offset to calculated modifier) or even "Modifier Override" (so we can type whatever value we want to see as total Modifier ignoring any automated calculations).
Detected on 7.2.2 version
To Reproduce It will probably happen on every test where you want to double the Modifier that system already calculates. So when you want to move from +10 to +20 or from +20 to +40. Application ignores this value, because it is perceived not as 10+10, but "was 10, is 10 - nothing changed".
To achieve that +40 (because range is in fact point-blank, not short range) I had to:
type 10 in Modifier field, so it switched to 30
type 20 in Modifier field, now it switched to 40
With new auto-calculated modifiers it would probably be nice to have separate field for "Modifier Offset" (to add our own offset to calculated modifier) or even "Modifier Override" (so we can type whatever value we want to see as total Modifier ignoring any automated calculations).