Eg. Leap spell.

If the server has different ingredients than the client, then perform might only be called on the server, which will not trigger the movement based action.

Solution for now is to make sure that clients have the same spell config as the server.

Idea: Make interface extension for spells to send a perform packet to the client. Interface allows writing and reading from buffer data.

Or sync spell configs to the client on login. Or maybe do both.