Recreating a project for the Actor architecture
START WITH THE BIG PICTURE
What does this part of Epok do?
Older Entity/Behaviour projects need to be recreated for the current Actor architecture.
- 01Keep the original project
- 02Create a current project
- 03Copy source assets and recreate maps and gameplay
What is happening under the hood?
- Legacy Entity/Behaviour maps and old Blueprint versions are rejected rather than converted.
- Maps use one Actor collection with transforms on spatial root components.
- There is no automatic migration layer.
Field note: Keep the original project and its source assets until the recreated version has been verified.
The Actor architecture is a breaking change. Previous Entity/Behaviour maps, older Blueprint versions and .epokscript sidecars are rejected with a diagnostic. Opening them does not rewrite or convert their files.
Create a new project using the current Basic, Sample or Third Person template. Copy reusable source assets into the new project, recreate the map with Actors, and reimplement scripts as C++ or Blueprint ActorComponents or Actor subclasses. Keep the original project separately while recreating its content.
Maps now store version 6 with one actors collection. Spatial values are stored on root components, custom logic is attached as ActorComponents, and C++ metadata comes from annotated classes. Blueprints use version 5 and the generated reflection cache uses schema 9.
There is no automatic compatibility or migration layer. See Actors and components for the creation, attachment and reuse workflow.