How crocobob911/project_kiriko works
Main Components
a. Core Game Systems
• Player System
• Movement Controller
• Animation Controller
• Combat System
• Camera Controller
• Enemy System
• Input System
• Scene Management
b. Asset Management
• 3D Models
• Animations
• Materials/Textures
• Audio
┌─────────────────────────────────────────────┐
• Presentation Layer │
• ┤
• Scene Rendering │
• UI/HUD │
• Camera System │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Gameplay Layer │
• ┤
• Player Systems │
• * Movement │
• * Combat │
• * Animation │
• Enemy Systems │
• Collision Detection │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Input Layer │
• ┤
• PC Input System │
• Mobile Input System │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Asset Layer │
• ┤
• 3D Models │
• Animations │
• Materials/Textures │
• Audio │
• ┘
Technical Details
Use of:
• Unity's Universal Render Pipeline
• Cinemachine for camera management
• Animation state machines
• Input system framework
Documentation
• Component relationships
• System responsibilities
• Key design patterns used
Remember to include external tools and plugins:
• StarterAssets integration
• Third-person controller framework
• Custom input system implementation
This architecture should clearly show how the various systems interact while maintaining flexibility for future additions and modifications to the gameplay mechanics.