Add sync support to more properties of objects

[arthuro555]

We need to ensure that all of the fields one may want to use are available to be synchronized.

Fields

• Position
• Width & Height
• Angle
• zOrder
• Layer
• Scale
• Visibility
• Opacity
• Current animation
• String of a text/text entry/text input object
• State variable
• Flipping
• Tint

Please comment any other properties you wish to be synchronized

[Keevle]

This should not just be a "send all and done",I think the Sync should only sync variables if changes occurLike if a users moving constantly only Position and angle are more likely to change so no sense in also syncing opacity and scale etc

[arthuro555]

That's already the case :) A full snapshot is only being sent to a client when it first connects, but afterwards only diffs are sent which only contain values that have changed.

See: https://github.com/arthuro555/THNK/blob/master/code/server/ObjectDiffer.ts#L28-L83

[Keevle]

amazing

[MyNameIsRinax]

You forgor to add object flip horizontally and vertically!!!

[Entr0py404]

Object tint please ;)

[Yggddrassill]

The Player Behaviors (not really) but the "Is Jumping" "Is Falling" and such, it doesn't need to sync the action because the position is already on sync, but the notion of the action taking place, that would make it easier to animate using the spritesheet animation.

[arthuro555]

Quite true! It is already planned to add a special behavior that synchronizes the platformer/top down movement behavior, in a way that:

• These conditions function
• The client can make accurate movement predictions in frames where it does not get a server update
• You can just use "simulate key press" on the client and it'll automatically send messages to the server to simulate these inputs correctly there, without writing any events on your side
• Automatically restore the object to the position & configuration it was in the moment the player did a key press (to not cause an unfair behavior if e.g. a jump that was done just in time before falling in a hole is only received by the server after it is too late due to network latency) (this one is quite complex and might require some additional time before being implemented)

:)

Track progress for this at #6