Eclipse Protocol is a top-down sci-fi survival strategy game set inside a failing space station.
You play as a maintenance robot trying to restore critical power systems, survive hostile drones, and reach extraction before systems collapse.
The project focuses on clean architecture, physics-based player control, procedural level flow, and state-driven enemy AI.
- Explore connected station rooms.
- Collect energy resources.
- Repair damaged power nodes.
- Survive escalating drone pressure.
- Reach the extraction point to win.
- Health reaches zero.
- Time deadline passes
- 3D Rigidbody player movement with responsive top-down control.
- Dash ability with cooldown, energy cost, and temporary invulnerability (I-frames).
- Enemy AI using finite state machines (Patrol, Chase, Return, Attack).
- NavMesh pathfinding for reliable navigation around obstacles.
- Procedural room spawning with modular prefabs and anchor-based placement.
- HUD with real-time health, energy, cooldown, and mission feedback.
- URP lighting, VFX feedback, and spatial audio routing.
- Engine: Unity (3D)
- Language: C#
- Rendering: URP
- AI:
NavMeshAgent+ FSM logic - UI: Unity Canvas
- Audio: Unity Audio + AudioMixer
- Version Control: Git + GitHub
| Action | Keyboard/Mouse |
|---|---|
| Move | WASD |
| Dash | Space |
| Interact | E |
| Pause | Esc |
Assets/
Scenes/
_project/
Audio/
Documents/
Prefabs/
Rooms/
Enemies/
Gameplay/
Materials/
VFX/
ScriptableObjects/
Scripts/
Core/
Player/
AI/
World/
UI/
Audio/
- Unity Editor: v6.4
- Git
- Clone this repository.
- Open the project with Unity Hub.
- Open
Assets/Scenes/Phase1_Sandbox.unity. - Press Play.
- Open
File -> Build Settings. - Select target platform.
- Add required scenes in build order.
- Build and run.
- Course GDD:
Assets/_project/Documents/Game Design Document (GDD).md - Exported GDD PDF:
Assets/_project/Documents/EclipseProtocol_GDD_v1_0.pdf - Phase 1 evidence captures:
Assets/_project/Documents/Evidence/
- Member 1: Momen Mahmoud
- Member 2: Rana Dief
- Keep commits small, meaningful, and frequent.
- Use descriptive commit messages.
- Maintain modular code organization.
- Document major system changes in the GDD or project notes.
Creative Commons CC0 1.0 Universal