Tower of DLC
Use the public Tower of DLC data/resource pair as a source-reading workshop without inventing a second copy of the project. Creator pulls the configured source ZIPs directly from GitHub.
1. Import the real project source
Open Creator → Use Public Pack as Base → Tower of DLC. Start with the data component. Creator turns recognized DAI definitions into editable forms and preserves every other file unchanged.
2. Map the project before editing
- Record the namespace and stable IDsDo not rename anything until you know which files reference it.
- Group definitions by DAI systemSeparate actions, conditions, reactions, content, experience/world definitions and ordinary Minecraft files.
- Open the resource companion separatelyMap models, textures, language and presentation assets back to the data-side IDs that consume them.
- Write a dependency mapMark which behavior is DAI-owned, vanilla-owned or presentation-only before changing the project.
3. Turn source-reading into a build exercise
Choose one self-contained behavior from the imported project and rebuild it in a fresh namespace using the relevant Create Anything guide. Compare the generated JSON to the source, then test both versions in Minecraft. This makes the public pack a working reference instead of a static example.
4. Branch safely
If you create a distinct derivative, change namespace/stable pack identity deliberately, keep the generated source note, audit every data↔resource reference and follow the original project's license before redistributing code or assets.