Workflow: Large Scale Projects

Managing 100,000+ assets requires a different approach than a small game.

1. Domain-Driven Design (Clean Architecture)

Strictly enforce layers to prevent the “Big Ball of Mud”.

• Core: Pure C#, no Unity References (if possible).
• Application: Game Logic, references Core.
• Presentation (UI/View): References Application.

Rule Configuration:

• Core cannot rely on UI.
• Core cannot rely on Infrastructure (Save Systems, Network implementations).

2. Headless Validation (CI/CD)

Don’t rely on developers to run the check manually. Integrate Nexus Graph into Jenkins, TeamCity, or GitHub Actions.

Command Line Interface

Nexus Graph includes a HeadlessRunner.

# Example Command
Unity.exe -batchmode -projectPath "." -executeMethod Nexus.Editor.HeadlessRunner.RunValidation -quit

• Exit Code 0: Architecture Clean.
• Exit Code 1: Violations Found (Fails the build).
• Report: automatically generated at Build/NexusReport.xml (JUnit format) or .json.

3. Modularization (.asmdef)

Break your project into Assembly Definitions. Nexus Graph visualizes these assemblies as giant nodes.

• Ensure your Game assembly doesn’t reference Editor assembly (a common build breaker).