How thomasschemmer/bestagon works
┌─ Game Core ─────────────────────┐
• ┌─ Gameplay Systems ─────────┐ │
• GameplayAbilitySystem │ │
• Card System │ │
• Building System │ │
• Unit System │ │
• ┘ │
• ┌─ World Generation ─────────┐ │
• MapGenerator │ │
• TileMeshGenerator │ │
• WorldGenerator │ │
• ┘ │
• ┌─ Visualization ───────────┐ │
• Entity Visualization │ │
• Preview System │ │
• Indicator System │ │
• ┘ │
• ┘
Key Subsystems
a) Gameplay Ability System (GAS):
• Abilities, Attributes, and Effects
• Flow of gameplay effects
• Link to tag system
b) Building & Resource Management:
• Building definitions
• Production systems
• Resource flow
c) Card System:
• Deck management
• Card effects
• Card UI elements
Integration Points
Clear connections between:
• UI Layer ↔ Game Systems
• World Generation ↔ Visualization
• Card System ↔ Building System
Technical Details
Important technical implementations:
• Unity's Universal Render Pipeline integration
• Shader systems for visualization
• Compute shaders for world generation
• GameplayAbilitySystem implementation
The tutorial and quest systems
Use a hierarchical layout to show how these systems interact while maintaining clear separation of concerns. The GameplayAbilitySystem should be shown as a central framework that other systems build upon.
• System boundaries
• Component relationships
This will create a comprehensive visualization of the game's architecture while maintaining clarity about how the different systems interact.