ipacketserializationservice
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| ipacketserializationservice [2026/08/15 07:17] – diviner | ipacketserializationservice [2026/08/15 07:23] (current) – diviner | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== IPacketSerializationService ===== | ===== IPacketSerializationService ===== | ||
| - | This service is responsible for serializing [[IEntity|Entities]] into [[EntityPacket|EntityPackets]] and applying EntityPacket data back onto existing Entities. Component state is serialized through the packet serialization strategy associated with each supported [[IComponent|Component]] type. Only Components that have a registered serialization strategy are serialized; Components without a corresponding strategy are ignored and do not contribute data to the EntityPacket. | + | This service is responsible for serializing [[IEntity|Entities]] into [[EntityPacket|EntityPackets]] and applying EntityPacket data back onto existing Entities. Component state is serialized through the packet serialization strategy associated with each supported [[IComponent|Component]] type. Only Components that have a registered |
| Component packets may be serialized using either encoded packet identifiers or packet type names. Encoded packets reduce serialized size by replacing type names with numeric identifiers, | Component packets may be serialized using either encoded packet identifiers or packet type names. Encoded packets reduce serialized size by replacing type names with numeric identifiers, | ||
ipacketserializationservice.1786778256.txt.gz · Last modified: by diviner
