Streamlining Code Structure for Composite Fields

[Kmsxkuse]

I’ve made a previous request like this a few months back:

Add a "Composite" bool to [GhostComponent] that sets one change bit for an entire component

In [GhostField] there exists an option "Composite" that, when set to true, generates a single change bit for an entire struct. For example a float4x4 would normally require 16 change bits, one for each float value, but with composite on, only a single change bit would be written for all four floats. This would mean that where normally if a float in that float4x4 would change, only the float would be serialized and sent to the client for changing. When composite is true, all sixteen floats woul…

At the current moment I’ve taken the advice in that thread to make my own custom code-generated serializers which works for one-off components but very tedious for multiple.

I’m happy to see some attributes being brainstormed to make the process automated.