This replicates an anti-pattern of DCS of writing back IDs to the spawn data table to the DCS stubs. Currently, that does not cause any bugs, as the spawn data is deep-copied before use, so tests will pass, but if the deep copy is removed later, such as to re-use IDs when an asset is de-spawned and later spawned again, there needs to be special treatment to not save any runtime IDs when marshaling assets, so this change makes tests fail if the treatment is incomplete.
This replicates an anti-pattern of DCS of writing back IDs to the spawn data table to the DCS stubs. Currently, that does not cause any bugs, as the spawn data is deep-copied before use, so tests will pass, but if the deep copy is removed later, such as to re-use IDs when an asset is de-spawned and later spawned again, there needs to be special treatment to not save any runtime IDs when marshaling assets, so this change makes tests fail if the treatment is incomplete.