Persistence contract
What RAPTOR keeps stable in saved scenes and prefabs across versions.
Unity saves a component by its script and field names. RAPTOR keeps these stable across versions, so scenes and prefabs from older versions still open when the C# API changes.
| What is kept | Detail |
|---|---|
| Runtime components | Type names, assemblies and saved field names. A moved or renamed type carries [MovedFrom], so Unity finds it under the new name. |
| Per-Block data | The assembly, namespace and class name of each RaptorBlockModifierData class. These are written into scenes and prefabs. |
RaptorSettings.asset | The project's RAPTOR settings, read through RaptorProjectSettings. A key is never reused with another meaning. |
| Logic | The component types RaptorLogic.RaptorLogicObject, RaptorLogic.Session.RaptorSessionMarker and Raptor.Components.RaptorLogicAssembly, every node and capability id, shortcut ids starting RAPTOR/Logic and registry ids starting raptor.logic. |
Your module's part
Apply the same rules to anything your module saves:
- Treat ids, setting keys and the names of saved data types as permanent once a version is out.
- If you must move or rename a saved type, add
[MovedFrom(true, sourceNamespace, sourceAssembly, sourceClassName)]with the old names. - A saved type whose module is removed loads as an empty entry and stays in the file. Adding the module back restores it.