Sent with QoS 0, not retained, and updated quickly in regular intervals (except if the
table is idle, e.g. without any cards).
It has a very flat layout, and information on what card belongs to what stack and to
what player is discarded.
Let us know if you need both:
1) lightweight, and fast card position updates
2) and information on player and stack to which they belong to
This is a data oriented layout, to save bandwidth on the network and for better cache
locality (assuming you are not using python like we are currently ;) ).
All three lists are guaranteed to have the same length.
This is a data oriented layout, to save bandwidth on the network and for better cache
locality (assuming you are not using python like we are currently ;) ).
All three lists are guaranteed to have the same length.
Same definition as player_cards