Project Foundations

Project Foundations is the layer underneath everything else: the naming, tags, data habits, folder ownership, template rules, and shared mapping logic that keep a large modular project from becoming chaos. These pages explain the thinking behind the ecosystem, not just the steps.

Related setup: Migrate and Integrate Hyper, Customize Your Datatables.

Why This Matters

When a project grows, the hard part is not adding one more Blueprint. The hard part is keeping hundreds of assets, tags, data rows, systems, and overrides understandable six months later. Hyper leans heavily on stable identifiers, gameplay tags, structured data, child assets, and clear folder boundaries so systems can scale without every feature becoming a custom exception.

What This Category Covers

• Gameplay tag structure for systems, states, teams, settings, item behavior, and project logic.
• Data management patterns for data tables, JSON workflows, data assets, and project-specific overrides.
• Folder structure and ownership rules so shared Hyper content and your custom project content stay cleanly separated.
• Shared infrastructure such as unified tag mapping and integration helpers that reduce repeated glue logic.

Working Advice

• Treat these docs as the rules of the road. If you follow them, the rest of the ecosystem becomes much easier to reason about.
• Prefer child Blueprints, project-specific data, and clean overrides over editing shared base content.
• Keep names and identifiers boring, stable, and exact. That is what lets the larger system stay flexible.