It's a gas feature, basically when we need to have different behavior of an ability but based in a client-auth context who change client and server logic.
GAS have a ton of fixed arguments (Ability level, magnitude, two slot for a ptr...).
GAS provide also the possibility to have a polymorphique struct sended.
The idea would be to replicate this behavior, the issue is i don't see how we can prevent in GMC context to send those data if they are not needed, and i don't think this is possible with my understanding of GMC way to replicate thing.
I've come with some idea in mind, like adding a simple compressed bitfield with ability, but i don't know if it will be suitable.
It's a gas feature, basically when we need to have different behavior of an ability but based in a client-auth context who change client and server logic.
GAS have a ton of fixed arguments (Ability level, magnitude, two slot for a ptr...). GAS provide also the possibility to have a polymorphique struct sended.
The idea would be to replicate this behavior, the issue is i don't see how we can prevent in GMC context to send those data if they are not needed, and i don't think this is possible with my understanding of GMC way to replicate thing.
I've come with some idea in mind, like adding a simple compressed bitfield with ability, but i don't know if it will be suitable.