project-architecture

Project Architecture - MyProject2

Fundamental Principles

1. Data-Driven

CRITICAL RULE: All rules come from Data Tables or Data Assets, NEVER hardcoded in code.

Implementation:

• Use UDataTable for tabular data (races, classes, items)
• Use UDataAsset for complex configurations (character sheets)
• Validate data in editor with UDataAsset::PostEditChangeProperty()
• Use FTableRowBase for data structures

Example:

// ✅ CORRECT - Data-Driven
UPROPERTY(EditDefaultsOnly, Category = "Data")
UDataTable* RaceDataTable;

// ❌ WRONG - Hardcoded
const float DwarfConstitutionBonus = 2.0f;

2. Modularity

CRITICAL RULE: Code organized by domain, each part with single and clear responsibility.

Directory Structure:

Source/MyProject2/
├── Characters/          # Characters and races
├── Components/          # Reusable components
│   ├── Data/           # Data components
│   ├── Features/        # Feature components
│   └── UI/             # UI components
├── Data/               # Data Assets and Data Tables
├── Gameplay/           # Game mechanics
└── Utils/              # Utilities

Rules:

• Each module must be independent
• Use interfaces for communication between modules
• Avoid circular dependencies
• One .h and .cpp file per class

3. Editor-Friendly

CRITICAL RULE: System must work perfectly in editor, allowing configuration without running the game.

Implementation:

• Use WITH_EDITOR for editor-specific code
• Validate data in PostEditChangeProperty()
• Use UPROPERTY(EditAnywhere) for editable properties
• Provide visual feedback in editor when possible

Example:

#if WITH_EDITOR
void UCharacterSheetDataAsset::PostEditChangeProperty(FPropertyChangedEvent& PropertyChangedEvent)
{
    Super::PostEditChangeProperty(PropertyChangedEvent);
    ValidateData();
}
#endif

4. Multiplayer Preparation

CRITICAL RULE: System prepared for multiplayer from the start, don't refactor later.