[email protected]

## [1.11.0] - 2025-12-12

### Added

* New Prefab List menu item and playmode tools button to quickly list all ghost prefabs in your project or scene hierarchy.
* Internal changes to support GameObject ghosts. More to come later. See Discussions post talking more about this work in progress.
* [Potential Breaking Change] Moving server side's ghost spawn writes from BeginFrame ECB to new PresentationGroup ECB.
* [Potential Breaking Change] GhostAuthoringComponent's content has been moved to a base class.
* Netcode profiler received new tooltips and warning icons. These will show if compression efficiency is low or the snapshot size is approaching max message size.
* Static ghosts now aggressively attempt to avoid looking up snapshot data (via `SnapshotData.GetDataAtTick`) inside the `GhostUpdateSystem.UpdateJob`, and the job itself early outs if there are no ghosts needing to restore, leading to a ~90% reduction in job timings. Profiler markers have also been added to this job, denoting which ghost types (and API calls) are taking the time.
* Users can now migrate non ghost data using the `IncludeInMigration` component and the associated `NonGhostMigrationComponents` buffer.
* Non-Ghost Components marked for migration on a Ghost Entity will now be automatically migrated to the correct Ghost.

### Changed

* Corrected ghost-types-templates docs regarding the packed vs unpacked format of `bool`, `byte`, `sbyte`, `float`, and `double`.
* Improved the `bool` serialization template, improving packed and unpacked costs (~4 bits to 1 bit, and 32 bits to 8 bits, respectively).

### Fixed

* An issue with static optimized ghosts, where incorrect logic in the `GhostUpdateSystem` caused them to not have their `CopyFromSnapshot` called even once in rare cases, which led to `[GhostFields]` like `StaticAsteroid.SpawnTick` (which need additional processing via the `CopyFromSnapshot` code-gen) to be incorrect on the client.
* `NetworkEndpoint` serialization inside GhostField's, which were mistakenly using `SerializeNetworkEndpointUnpacked` in a packed case.
* Missing average per entity column for per ghost type overhead sections in the profiler.

Author: Unity Technologies

.attestation.p7m

@@ -1 +1 @@
-{"timestamp":1763565376,"signature":"gjfzyCpyeFwn7eVrPrSwc17RJFFFkGFkkrcdiAwNQdvKmqcyFGyUAGQEQdGnWBAwzZTRBp/81w6W4WYcR21F0KlhM5JITXktlpGWncZyNdTuoOE/mss8BMoK49OkDxzHwlaikl0z64Rf3ZY/8Nam5mL6CrL7PtaPOBbr7Bja2IISDSkGqk5HFJd8HyHgcFL6w6GIVKnyO3cDrGTLs236fMsNgeYx1eFmMeOqy6R+A/M1Ho5xX4gg5mlzdx7q6MFR2HINY0KIuGy/fp/2/VNuXyL28wh9t9ua+UfWENeVMK8fbIuXIwPTLCf9+CC55gC2hnEvaSbgmbjNwGnewCzCawSkpda6jQ9Qrhiiw3nHR/5XwivnJ8EWNLA4iBrM/MLqYNbT9lM9R2ywjqpHEBrF+W7m0DH74LMCDhPsYs867KgYOViFvBUdAnZ9Go7VIwfmMcs+yR+LoeqHfTbG/KK91BHiAAPR3CI5aAjFknMxTQ4CpF90PFwUzprN/yEw4aPy","publicKey":"LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0KTUlJQm9qQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FZOEFNSUlCaWdLQ0FZRUFzdUhXYUhsZ0I1cVF4ZEJjTlJKSAordHR4SmoxcVY1NTdvMlZaRE1XaXhYRVBkRTBEMVFkT1JIRXNSS1RscmplUXlERU83ZlNQS0ZwZ1A3MU5TTnJCCkFHM2NFSU45aHNQVDhOVmllZmdWem5QTkVMenFkVmdEbFhpb2VpUnV6OERKWFgvblpmU1JWKytwbk9ySTRibG4KS0twelJlNW14OTc1SjhxZ1FvRktKT0NNRlpHdkJMR2MxSzZZaEIzOHJFODZCZzgzbUovWjBEYkVmQjBxZm13cgo2ZDVFUXFsd0E5Y3JZT1YyV1VpWXprSnBLNmJZNzRZNmM1TmpBcEFKeGNiaTFOaDlRVEhUcU44N0ZtMDF0R1ZwCjVNd1pXSWZuYVRUemEvTGZLelR5U0pka0tldEZMVGdkYXpMYlpzUEE2aHBSK0FJRTJhc0tLTi84UUk1N3UzU2cKL2xyMnZKS1IvU2l5eEN1Q20vQWJkYnJMbXk0WjlSdm1jMGdpclA4T0lLQWxBRWZ2TzV5Z2hSKy8vd1RpTFlzUQp1SllDM0V2UE16ZGdKUzdGR2FscnFLZzlPTCsxVzROY05yNWdveVdSUUJ0cktKaWlTZEJVWmVxb0RvSUY5NHpCCndGbzJJT1JFdXFqcU51M3diMWZIM3p1dGdtalFra3IxVjJhd3hmcExLWlROQWdNQkFBRT0KLS0tLS1FTkQgUFVCTElDIEtFWS0tLS0tCg"}
+{"timestamp":1766487700,"signature":"oGK7SYP2P0QN6DmOOMrEnaJXCcfbs9X2VjGNf+A7NsdR17/Xu5rqAyrZ7cs/ppNnWxHu/0oHs/JY2qvCWHepIfKYnx6nHBjyAftKMiu0+v3Xu3/N0jipoPgoMZVWZxGz8XCS/HACWifSwgpSBy4zbKWaDVXFdcpj5f38ZRVQrsF07qH8wzP4Tz/5kVX5OdpFiQYaIjrFjW05DiVy3jMrriakeRrM5p3azCDKKgU0z6lxhg5NeRHh9OOy6zo3Pa0pOmPRLWLuf2L+YxIjGaJpN2Uy47rcqUL0Wu5IlO70lQock/0LxHaYohjYRFdLzvAGbML8BD4SAMvjVRtGwRykJHMP4NniyHbqqkTkRZYS4kGTgCYPgPf9bFePxuCko6RNTG3Y1UUp45qy0UZdmPuR+hU5cWJWPHh3FZbW3VxUF7ic4NuoEFESYI0TNqLqZ0OVAwVhxzJDApZTHjXaxwZO4O1BGtm5IGaf+jF6EflFLEwuW6dRft32NUtPozJFVv9G","publicKey":"LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0KTUlJQm9qQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FZOEFNSUlCaWdLQ0FZRUFzdUhXYUhsZ0I1cVF4ZEJjTlJKSAordHR4SmoxcVY1NTdvMlZaRE1XaXhYRVBkRTBEMVFkT1JIRXNSS1RscmplUXlERU83ZlNQS0ZwZ1A3MU5TTnJCCkFHM2NFSU45aHNQVDhOVmllZmdWem5QTkVMenFkVmdEbFhpb2VpUnV6OERKWFgvblpmU1JWKytwbk9ySTRibG4KS0twelJlNW14OTc1SjhxZ1FvRktKT0NNRlpHdkJMR2MxSzZZaEIzOHJFODZCZzgzbUovWjBEYkVmQjBxZm13cgo2ZDVFUXFsd0E5Y3JZT1YyV1VpWXprSnBLNmJZNzRZNmM1TmpBcEFKeGNiaTFOaDlRVEhUcU44N0ZtMDF0R1ZwCjVNd1pXSWZuYVRUemEvTGZLelR5U0pka0tldEZMVGdkYXpMYlpzUEE2aHBSK0FJRTJhc0tLTi84UUk1N3UzU2cKL2xyMnZKS1IvU2l5eEN1Q20vQWJkYnJMbXk0WjlSdm1jMGdpclA4T0lLQWxBRWZ2TzV5Z2hSKy8vd1RpTFlzUQp1SllDM0V2UE16ZGdKUzdGR2FscnFLZzlPTCsxVzROY05yNWdveVdSUUJ0cktKaWlTZEJVWmVxb0RvSUY5NHpCCndGbzJJT1JFdXFqcU51M3diMWZIM3p1dGdtalFra3IxVjJhd3hmcExLWlROQWdNQkFBRT0KLS0tLS1FTkQgUFVCTElDIEtFWS0tLS0tCg"}

.signature

@@ -2,6 +2,30 @@
 uid: changelog
 ---
 
+## [1.11.0] - 2025-12-12
+
+### Added
+
+* New Prefab List menu item and playmode tools button to quickly list all ghost prefabs in your project or scene hierarchy.
+* Internal changes to support GameObject ghosts. More to come later. See Discussions post talking more about this work in progress.
+* [Potential Breaking Change] Moving server side's ghost spawn writes from BeginFrame ECB to new PresentationGroup ECB.
+* [Potential Breaking Change] GhostAuthoringComponent's content has been moved to a base class.
+* Netcode profiler received new tooltips and warning icons. These will show if compression efficiency is low or the snapshot size is approaching max message size.
+* Static ghosts now aggressively attempt to avoid looking up snapshot data (via `SnapshotData.GetDataAtTick`) inside the `GhostUpdateSystem.UpdateJob`, and the job itself early outs if there are no ghosts needing to restore, leading to a ~90% reduction in job timings. Profiler markers have also been added to this job, denoting which ghost types (and API calls) are taking the time.
+* Users can now migrate non ghost data using the `IncludeInMigration` component and the associated `NonGhostMigrationComponents` buffer.
+* Non-Ghost Components marked for migration on a Ghost Entity will now be automatically migrated to the correct Ghost.
+
+### Changed
+
+* Corrected ghost-types-templates docs regarding the packed vs unpacked format of `bool`, `byte`, `sbyte`, `float`, and `double`.
+* Improved the `bool` serialization template, improving packed and unpacked costs (~4 bits to 1 bit, and 32 bits to 8 bits, respectively).
+
+### Fixed
+
+* An issue with static optimized ghosts, where incorrect logic in the `GhostUpdateSystem` caused them to not have their `CopyFromSnapshot` called even once in rare cases, which led to `[GhostFields]` like `StaticAsteroid.SpawnTick` (which need additional processing via the `CopyFromSnapshot` code-gen) to be incorrect on the client.
+* `NetworkEndpoint` serialization inside GhostField's, which were mistakenly using `SerializeNetworkEndpointUnpacked` in a packed case.
+* Missing average per entity column for per ghost type overhead sections in the profiler.
+
 ## [1.10.0] - 2025-11-09
 
 ### Added
@@ -27,8 +51,6 @@ uid: changelog
 * Shorts are now properly supported in components and commands.
 * Missing Physics-related API docs have been re-added.
 
-
-
 ## [1.9.1] - 2025-10-11
 
 ### Changed

CHANGELOG.md

@@ -33,6 +33,7 @@
     * [Host migration API and components](host-migration/host-migration-api.md)
     * [Add host migration to your project](host-migration/add-host-migration.md)
       * [Host migration requirements](host-migration/host-migration-requirements.md)
+      * [Host migration considerations](host-migration/host-migration-considerations.md)
       * [Host migration systems and data](host-migration/host-migration-systems.md)
       * [Lobby and Relay integration](host-migration/lobby-relay-integration.md)
     * [Limitations and known issues](host-migration/host-migration-limitations.md)

Documentation~/TableOfContents.md

@@ -22,7 +22,7 @@ For example, if a client predicted spawns a missile, then, although that client
 
 The recommended method for handling user inputs is to create an input component data struct that inherits the [`IInputComponentData`](https://docs.unity3d.com/Packages/com.unity.netcode@latest?subfolder=/api/Unity.NetCode.IInputComponentData.html) interface. Then you can add command data to the buffer and retrieve it when processing. Unity handles inputs automatically through code-generated systems, as long as you set up the input gathering and input processing systems separately.
 
-Because the input struct implementing `IInputComponentData` is baked by `ICommandData`, [the 1024 bytes limit for the payload](#ICommandData-serialization-and-payload-limit) also applies.
+Your `IInputComponentData` component needs to be on the target ghost at baking time, then Netcode for Entities baking will set up and generate appropriate commands and serializers for you. Because the input struct implementing `IInputComponentData` is baked by `ICommandData`, [the 1024 bytes limit for the payload](#ICommandData-serialization-and-payload-limit) also applies.
 
 > [!NOTE]
 > Per prefab overrides done in the ghost authoring component inspector are disabled for input components and their companion buffer. You can add a ghost component attribute on the input component in code and it will apply to the buffer as well.

Documentation~/command-stream.md

@@ -89,10 +89,10 @@ Some types have multiple templates that provide alternative ways to serialize th
 
 For types with multiple templates, the available options are as follows:
 
-| Setting | Options | Description |
-|---|---|---|
-| Quantization | Quantized or unquantized  | Quantization involves limiting the precision of data for the sake of reducing the number of bits required to send and receive that data. For example, a float value `12.456789` with a quantization factor of `1000` is sent as `int 12345`. Unquantized means the float is sent with full precision. Refer to [quantization](compression.md#quantization) for more details. |
-| Smoothing method | `Clamp`, `Interpolate`, or `InterpolateAndExtrapolate` | Smoothing method specifies how a new value is applied on the client when a snapshot is received. Refer to the [`SmoothingAction` API documentation](https://docs.unity3d.com/Packages/com.unity.netcode@latest?subfolder=/api/Unity.NetCode.SmoothingAction.html) for more details. |
+| Setting          | Options                                                | Description                                                                                                                                                                                                                                                                                                                                                                  |
+|------------------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Quantization     | Quantized or unquantized                               | Quantization involves limiting the precision of data for the sake of reducing the number of bits required to send and receive that data. For example, a float value `12.456789` with a quantization factor of `1000` is sent as `int 12345`. Unquantized means the float is sent with full precision. Refer to [quantization](compression.md#quantization) for more details. |
+| Smoothing method | `Clamp`, `Interpolate`, or `InterpolateAndExtrapolate` | Smoothing method specifies how a new value is applied on the client when a snapshot is received. Refer to the [`SmoothingAction` API documentation](https://docs.unity3d.com/Packages/com.unity.netcode@latest?subfolder=/api/Unity.NetCode.SmoothingAction.html) for more details.                                                                                          |
 
 Each of these options changes how the original value is serialized, deserialized, and applied on the client, and each template uses different, named regions to handle these cases. The code generator chooses the appropriate regions to generate, and bakes your user-defined serialization settings for fields on your types directly into the serializer for your type. You can explore these generated types in the projects' `Temp/NetCodeGenerated` folder (note that they're deleted when Unity is closed).
 
@@ -109,7 +109,9 @@ When fixed-size list are serialized in RPC/Command or as a field in replicated c
 | IInputComponentData | 64         |
 
 When fixed-size list fields are replicated in RPCs the maximum allowed capacity (and thus length) for any fixed size list field element is limited to 1024 elements.
-> Remark: Notice that becase sending RPC larger than 1MTU is not currently supported, the packet size induce an instrisict limitation on the maximunumber of serializable elements that can be way lower than 1024.
+
+> [!NOTE]
+> Sending an RPC larger than the max transmission unit (MTU) isn't supported. This limitation on packet size means that the maximum number of serializable elements can be lower than 1024, depending on the [size of your MTU](https://docs.unity3d.com/Packages/com.unity.transport@latest?subfolder=/api/Unity.Networking.Transport.NetworkParameterConstants.html#Unity_Networking_Transport_NetworkParameterConstants_MTU).
 
 When fixed-size list fields are replicated in `IComponentData`, `IBufferElementData`, `ICommandData` and `IInputComponentData` the maximum allowed fixed-list capacity is capped to 64 elements.
 
@@ -129,10 +131,10 @@ The cap (of 64) is intentional; it is a good compromise between flexibility (as
 
 For Inputs (commands) the common use case we are optimizing for is that input should be in general small. So we preferred to enforce the rule to constrain input size. Further, because inputs can be replicated for other players (via the presence of the `[GhostField]` attribute - and associated `GhostComponent` flags), we would had a very strange and non-uniform behaviour in such case.
 
-#### Why don't RPCs have a larger maximum allowed capacity ?
+#### Why don't RPCs have a larger maximum allowed capacity?
 The main reasons are:
-- RPCs are meant to be sent unfrequently
-- They our most flexible and unique tool for message passing.
+- RPCs are meant to be sent infrequently.
+- They are the most flexible tool for message passing.
 - They don't have any particular needs for complex change mask generation that justify applying the limit either.
 
 ## How types are serialized
@@ -141,23 +143,26 @@ Netcode for Entities serialize the supported types over the network by using eit
 "un-packed" (full bits) format.
 
 #### packed vs unpacked format
-| Type           | unpacked          | packed                                                                        |
-|----------------|-------------------|-------------------------------------------------------------------------------|
-| sbyte          | 32 bit            | zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket)       |
-| short          | 16 bit            | zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket)       |
-| int            | 32 bit            | zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket)       |
-| long           | 64 bit            | zig-zag encoded, 2 x (4 bits + variable size payload (huffman/golomb bucket)) |
-| byte           | 32 bit            | 4 bits + variable size payload (huffman/golomb bucket)                        |
-| uint           | 32 bit            | 4 bits + variable size payload (huffman/golomb bucket)                        |
-| ushort         | 16 bit            | 4 bits + variable size payload (huffman/golomb bucket)                        |
-| ulong          | 64 bit            | 2 x (4 bits + variable size payload (huffman/golomb bucket))                  |
-| float          | 32 bit            | 0: 1bit otherwise 32 bits                                                     |
-| double         | 64 bit            | 0: 1bit otherwise 64 bits                                                     |
-| FixedStringXXX | 8bit + len * 8bits | 4 bits + varialbe size payload (len) + len * (4 bits + varialbe size payload) |
-| float2         | 2 * 32bits        | 2 * packed float size                                                         |
-| float3         | 3 * 32bits        | 3 * packed float size                                                         |
-| float4         | 4 * 32bits        | 4 * packed float size                                                         |
-| quaternion     | 4 * 32bits        | 4 * packed float size                                                         |
+| Type                    | unpacked            | packed                                                                                  |
+|-------------------------|---------------------|-----------------------------------------------------------------------------------------|
+| bool                    | 8 bits              | 1 bit                                                                                   |
+| sbyte                   | 8 bits              | zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket)                 |
+| short                   | 16 bits             | zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket)                 |
+| int                     | 32 bits             | zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket)                 |
+| long                    | 64 bits             | zig-zag encoded, 2 x (4 bits + variable size payload (huffman/golomb bucket))           |
+| byte                    | 8 bits              | 4 bits + variable size payload (huffman/golomb bucket)                                  |
+| uint                    | 32 bits             | 4 bits + variable size payload (huffman/golomb bucket)                                  |
+| ushort                  | 16 bits             | 4 bits + variable size payload (huffman/golomb bucket)                                  |
+| ulong                   | 64 bits             | 2 x (4 bits + variable size payload (huffman/golomb bucket))                            |
+| float (full precision)  | 32 bits             | 0: 1bit otherwise 32 bits                                                               |
+| float (quantized)       | 32 bits             | quantized, then zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket) |
+| double (full precision) | 64 bits             | 0: 1bit otherwise 64 bits                                                               |
+| double (quantized)      | 64 bits             | quantized, then zig-zag encoded, 4 bits + variable size payload (huffman/golomb bucket) |
+| FixedStringXXXBytes     | 8bits + len * 8bits | 4 bits + variable size payload (len) + len * (4 bits + variable size payload)           |
+| float2                  | 2 * 32bits          | 2 * packed float size                                                                   |
+| float3                  | 3 * 32bits          | 3 * packed float size                                                                   |
+| float4                  | 4 * 32bits          | 4 * packed float size                                                                   |
+| quaternion              | 4 * 32bits          | 4 * packed float size                                                                   |
 
 ### How to support unions
 The `[GhostField]` attribute enables two netcode sub-systems; serialization, and client prediction (backup & restoring).

Documentation~/ghost-types-templates.md

@@ -18,6 +18,8 @@ Understand the host migration API, components, and component options.
 | `HostMigrationInProgress` | This component is used to detect when a host migration is in progress and when it's complete. |
 | `HostMigrationConfig` | A singleton component that exposes a few options to modify in the host migration system. |
 | `HostMigrationStats` | A few statistics about the lobby operations like the data blob size. This component also contains the last update time of the host migration data which can be used to see when it's time to upload it again.|
+| `NonGhostMigrationComponents` | Used to specify which components on entities marked with the IncludeInMigration component will be migrated. |
+| `IncludeInMigration` | Used to tag entities containing non-ghost components for migration. Only components specified in the NonGhostMigrationComponents buffer will be migrated. |
 
 The `HostMigrationConfig` component has the following options: