How tranhaok4/hyperspace-cosmo-clash works
Project type and purpose
• This is a Unity‐based 2D/3D game project (“Hyperspace-Cosmo-Clash”).
• It comprises game scenes, assets (sprites, materials, audio, VFX), ScriptableObject data, prefabs, and C# gameplay scripts.
File structure
• Top‐level Unity folders:
• Assets (Animate, Data, Materials, Music, Prefabs, Scenes, Scripts, Sprites, TilePalette)
• Packages, ProjectSettings, UserSettings
• Under Assets/Scripts, directories group by feature: CommonScripts, Player, Ship, Enemy, Bullet, Obstacles, Spawner, Stages, UI, Music, VFX, Item, Enhancement, etc.
• Data folder stores ScriptableObject definitions (e.g. ShipProfileSO, BossAbilitiesData, SceneMusicData).
• Scenes folder holds Unity scene files (GameMenuScene, ShipSelectionScene, Map1, PrototypeScene).
README
• Minimal content (“# Hyperspace-Cosmo-Clash”), but structure implies a data-driven architecture: ScriptableObjects driving game parameters.
Main components and their interactions
a. Core engine (Unity)
b. Input subsystem
• InputManager → receives player input → dispatches to ShipController, UI
c. Gameplay manager layer
• GameCtrl / GameLevelManager → orchestrates scene loading, stage progression
• StageSpawnerManager & SpawnerStage → spawn waves of enemies, meteorites
d. Entity layer
• PlayerShip (ShipCtrl, ShipMovement, ShipShootByMouse)
• Enemies (EnemyCtrl, BossCtrl, movement/AI scripts)
• Obstacles (MeteoriteCtrl)
• Projectiles (BulletCtrl, MissileFollowEnemy)
e. Data layer (ScriptableObjects)
• ShipProfileSO, BossAbilitiesDataSO, EnhancementDataSO, SceneMusicDataSO
• These feed into controllers (e.g. ShipEnhanceManager reads EnhancementDataSO)
f. Visual/Audio layer
• Sprites, Materials, Animations, VFX prefabs (Animate folder, VFX scripts)
• AudioManager / GameMusicManager → plays SceneMusic, SFX via SoundEffectDataSO
g. UI layer
• HUD controllers (CoinHUD, ExpLevelHUD, UIEnemyHPBar, PauseMenuHUD, ShipSelectionUI)
• BaseUIComponent provides common behavior
Architectural patterns and principles
• Data-driven: ScriptableObjects define parameters, so designers tune without code changes.
• Separation of concerns: Input → Gameplay logic → Entities → Rendering/Audio → UI
• Manager/controller pattern: central “GameCtrl” and specialized managers (AudioManager, GameLevelManager).
• Spawner and StageController manage lifecycles, decoupled from entity behaviors.
• Observer/Notificater pattern: scripts like Notificater, PlayShipSkillNotificater broadcast events.