All in one State or is it better to split properties in several States?

ThundThund
edited March 6 in BOLT Engine
Does it make any difference, in terms of network performance, to join many properties in the same state instead of splitting them into several states?

Thanks in advance.

Comments

  • An entity can only use one state. Unused state properties have no effect on network overhead or performance.
  • stanchion wrote: »
    An entity can only use one state. Unused state properties have no effect on network overhead or performance.

    I'm going to explain my question with an example:
    1 character has 1 weapon. The weapon has some attributes, so I could create a state for the character and another one for the weapon; or I could add the weapon state properties to the character's state, all in one. This is a very simple case but imagine it was bigger and more complex.
    In terms of how Bolt manages states and packages and performance, would it make any difference to choose either approach? Or are both strategies equivalent?
Sign In or Register to comment.