Engines · Intermediate · Cohort
Engine Scene Graph Habits
Learn how to structure scenes so a team of six can merge without chaos. Covers naming conventions, prefab boundaries, additive loading, and editor tooling hooks.
₩1,240,000
8 weeks · informational pricing
Request informationInclusions
- Prefab contract templates
- Additive scene loading patterns
- Editor validation scripts
- Naming convention linter
- Merge conflict reduction playbook
- Async load profiling checklist
- Handoff docs for artists
Outcomes
- Refactor a sample project to team standards
- Automate three validation rules in-editor
- Run a load-order audit on a multi-scene flow
Lead instructor
Sora Kim
Curriculum designer for engine workflows; shipped three co-op titles.
FAQ
Primary labs use Unity; Godot track mirrors concepts with equivalent tooling.
Reviews
Client in mobile games — our additive loading bugs dropped after the audit template.
Clear on prefab contracts. The linter scripts needed minor tweaks for our naming scheme.