Gameplay system architecture
Practical choices for types, prefabs, state, dependencies, folders and Git.
Choose a concrete task
- How a type differs from a prefab
- Run a complete system
- Avoid unnecessary entities
- Supply an external target
- Separate settings and instance health
- Validate before mutation
- Organize project files
- Set up Git without caches or lost sources
- Choose a shared service lifetime
- Organize level structure and deletion responsibility
- Choose callbacks or notifications
Start here
If you have not assembled a gameplay system yet, start with the five-file health system. Its result is visible in the application output; then adapt the system to your game.
Reckfell Engine documentationBack to top ↑