[SP] Force power Timing Fix

[BE-Arbiter]

Fix Force power activating to many time per second at high fps.

[ensiform]

This adds new fields to saves breaking compat, however.

[BE-Arbiter]

Having a better alternative ?

[ensiform]

Don't put in playerstate

[BE-Arbiter]

Where would you put it ? Isn't ent->s also save breaking? In a logic standpoint it's where all force properties are stored and its not like a table of size max_entities would be an elegant solution...

[ensiform]

Where would you put it ? Isn't ent->s also save breaking? In a logic standpoint it's where all force properties are stored and its not like a table of size max_entities would be an elegant solution...

Any reason why it has to be in the entity state or player state at all, not just part of the client struct?

[BE-Arbiter]

it's more clean to my psychorigid mind. Will make your proposed adaptations

[BE-Arbiter]

Is it better now ? :)

[ensiform]

Well it will not compile, you put it in entity structure and reference it in client structure.

[BE-Arbiter]

There.