Team and role
O2D was created for GN! Game Jam #15 by an eight-person team spanning project management, game design, programming, and art.
Role: Programmer. I co-implemented the player controller and oxygen loop within the eight-person team.
Player controller and oxygen systems
O2D
Eight people built this Unity 6 jam game about defending an oxygen base from alien waves, gathering fuel, crafting upgrades, and using player abilities.
- Role
- Programmer
- Context
- Eight-Person Team
- GN! Game Jam #15
- Period
- November 2024
- Status
- Completed game-jam project
- playable Windows builds
Player controller and oxygen
- Co-implemented the Unity Input System player controller: movement and input, dash, teleport and clone abilities, cooldowns, and health and oxygen events for UI updates.
- Implemented the ScriptableObject-configured oxygen base. Its energy level changes the visible bubble radius and matching 2D collider.
Design decisions
- Oxygen as shared pressure
- The base oxygen level gives combat, fuel collection, and return-to-base decisions one common survival constraint.
- Modular weapon progression
- Attachable upgrades give the player a compact way to customise combat during a short jam experience.
What was hard
- Coordinating eight contributors within a five-day jam window.
- The team used defined roles and documented tools including Jira and Miro while integrating a tightly scoped playable loop.
Delivered builds
The team submitted before the jam deadline and later documented a post-jam bugfix build. Both the original jam build and the post-jam Windows build remain publicly playable.
What I took from it
- How clear roles and scope control support integration in a larger short-deadline team.
- How one survival resource can connect combat, exploration, crafting, and return-path decisions.
Project media
