This was due to the ServerAccountCorrector calling the economy events another time with the new account.
Directly setting the new account is the far better approach and has been adjusted for all currency events.
This resolves issues when multiple listeners try to handle the same
events e.g. for group support which would've passed it onto the normal
listeners leading to errors
Also deprecate amount and account setters on the CurrencyCheckEvent,
these values will be final in a future version. Changing them here does
not make sense in the internal structure.