2025 COMSM0166 group 18
Your game lives in the /docs folder, and is published using Github pages to the link above.
Include a demo video of your game here (you don't have to wait until the end, you can insert a work in progress video)
Important
Our team previously developed and modified code in this 📦 GitHub repository
| Name | GithubID | Role | Completed Work | |
|---|---|---|---|---|
| Tianyu Qi | [email protected] | qtyohh | TBD | TBD |
| Likun Liang | [email protected] | lycorisadiata | TBD | TBD |
| Yutong Liu | [email protected] | WILLOW579 | TBD | TBD |
| Zihao Xia | [email protected] | WeirdDruid | TBD | TBD |
| Guanglong Xia | [email protected] | X-Theodore | TBD | TBD |
-
Game background
- The game depicts conflicts and technological changes driven by rising sea levels. In the early 22nd century, climate change caused a dramatic rise in sea levels, submerging most land. Humanity survives on floating cities, sea bases, and artificial highlands, but resource scarcity and environmental decline fuel tensions. Major factions battle for islands, ruins, and ocean resources, while corruption, pirates, and mercenary groups threaten the survivors.
- The protagonist, a vengeful exile, lost their home to these upheavals. Navigating between floating cities and ruins, they face pirates, corrupt forces, deep-sea monsters, sudden superstorms, and mysterious ocean anomalies.
-
Game mechanics
- This game features a highly replayable roguelike core loop, where each playthrough presents unique strategic choices. Key mechanics include procedurally generated levels, diverse weapon and skill combinations, progressively increasing difficulty, and a reward and penalty system, ensuring fresh challenges and opportunities in every run.
- Players will engage in a continuous cycle of “Start - Explore - Battle - Decision-Making - Death/Victory - Progress/Restart”, gradually enhancing their abilities, unlocking new content, and delving deeper into strategic gameplay. The game aims to deliver intense combat experiences while fostering a sense of achievement and enjoyment through repeated trials and growth.
-
Game innovation:
- A roguelike shooting survival game where each playthrough is unique, requiring players to fight, survive, and strategize in an ever-changing environment. Features various weapons and skill combinations, along with resource collection and upgrades, allowing players to enhance their abilities while facing intense combat.
- A dynamic climate system where weather and environmental changes directly impact gameplay. Superstorms may alter navigation routes, ocean currents affect movement speed, and mysterious ocean anomalies introduce new biological threats. Players must adapt to extreme weather conditions, adjusting their tactics to survive and fight effectively.
- An environmental pollution system where pollution levels fluctuate based on player and enemy activities, affecting the ecosystem, resource availability, and enemy strength. High-pollution areas may spawn mutated creatures, lower resource yields, and corrosive ocean conditions, while reducing pollution can unlock technological upgrades and allied support. Players can either purify the environment for long-term benefits or exploit pollution-induced chaos as a tactical advantage.
| Bot | User Story | Acceptance Criteria |
|---|---|---|
| Action Shooter Enthusiast | As an action shooter game enthusiast, I have a lot of time recently, but most action shooters are too repetitive. I want to play a game that includes more randomness. | 1. Enemies, weapons, and battlefields are randomly generated in each session. 2. The difficulty of the game and the types of enemies dynamically adjust based on player progress. 3. The game has multiple random event triggers, such as sudden tasks and randomly dropped powerful equipment. 4. Players can experience a different gameplay process and challenges every time they play. 5. There is a random mode where players can choose to generate different challenges randomly. |
| Rogue-like Enthusiast | As a roguelike game enthusiast, I've played many roguelike games, but few of them incorporate battlefield changes as part of the strategy. I want to play a roguelike game that includes battlefield changes as part of the strategy. | 1. The battlefield changes dynamically based on game progress or player choices. 2. The battlefield changes affect the player’s tactical decisions, such as the addition of obstacles or environmental changes (e.g., hazardous areas, terrain traps). 3. Players can actively alter the battlefield using specific skills or items. 4. Changing the battlefield requires players to weigh their strategy and resource management. 5. The impact of battlefield changes is clearly feedbacked in the game, such as increased combat difficulty or tactical advantages. |
| Casual Gamer | As a casual gamer, I’ve always wanted to try roguelike games, but the learning curve of games like The Binding of Isaac and Slay the Spire is too steep for me. I find it hard to keep playing. I want the ability to customize the game difficulty so I can choose the difficulty based on my gaming level. | 1. The game offers multiple difficulty settings that players can adjust based on their skill level. 2. The game includes tutorials or guidance to help new players understand the basic gameplay. 3. The game provides progressively unlocked difficulty options, allowing players to gradually challenge higher levels as their skills improve. 4. At lower difficulties, enemy attack strength and numbers are reduced, making tasks easier to complete. 5. The game provides clear progress tracking and feedback, allowing players to see their achievements in the game. |
| Game Auditor | As a game auditor, I want the game to have a wider audience, so I need to minimize graphic violence. | 1. The game avoids excessive graphic violence, including bloody or overly gory scenes. 2. Combat effects can be represented through non-lethal means, such as stunning or controlling, instead of direct killing. 3. The game’s content complies with age classification standards, avoiding excessively violent or disgusting elements. 4. The game avoids using vulgar, insulting, or extremist language or visual effects. 5. If necessary, the game provides adjustable violence levels to suit different audiences. |
| Colorblind Player | As a colorblind player, I often find it difficult to distinguish between characters, items, etc., in fast-paced action games. I hope the game features elements with clear visual effects, such as different colored outlines, to improve my visual experience. | 1. Each character, item, enemy, and other elements in the game have clearly distinguishable marks, such as different colored borders or outlines. 2. The game offers colorblind modes or customizable color options to help colorblind players differentiate between elements. 3. The UI elements in the game (e.g., menus, buttons) are designed with colorblind players in mind to ensure all information is clearly visible. 4. Environmental and combat elements in the game are differentiated through shapes, textures, and other features to reduce reliance on color for identification. 5. The game offers visual effect options, allowing players to adjust visual markers according to their needs. |
- Player Units:
- Character Status: Health, Mana (for skills), Buff/Debuff, Attack Power, Damage Bonus, Movement Speed, Armor
- Weapons: Types (melee, ranged), Parameters (damage, range, etc.), Ammunition management
- Skills: Targeted or area-based, Cooldown, Effects, Skill upgrades (level scaling)
- Equipment: Types (armor, accessories), Parameters, Effects, Limited quantity (e.g., consumables)
- Companions/Summons: Number, Positioning, AI behavior, Attributes (health, attack power)
- Enemy Units:
- Character Status: Health, Buff/Debuff, Attributes (damage, armor, etc.)
- Weapons: Types, Parameters (damage, range)
- Skills: Independent skill set, AI-controlled usage (attacks, special moves)
- Equipment: Impact on behavior or strength (e.g., more armor, stronger attacks)
- Special Cases: Spawn locations, Strength scaling with progression, Unique behavior patterns (e.g., retreat when low health)
- Neutral Units:
- Interaction: Players can interact (e.g., trading, quest giving, combat)
- Other Functions: Environmental impact (e.g., triggering events), NPC behaviors (e.g., healing, providing information)
- Environment:
- Destructible Objects: Interactive barriers, traps, walls that can be destroyed or altered by players (using weapons or skills)
- Indestructible Objects: Static obstacles that remain throughout gameplay (e.g., terrain, background scenery)
- User Interface & Interaction:
- Reward System: Distributed based on performance (e.g., combat efficiency, quest completion), Scaling rewards based on progress (e.g., more powerful items as players advance)
- Portals & Teleportation: Activate portals with specific conditions (e.g., key item, skill), Random destination selection for exploration
- Other Interactive Elements: Shops (purchase items with in-game currency), Dialogue (with consequences for decisions), Decision-making events (moral choices, combat choices)
- Randomization & Procedural Elements:
- Enemies: Random selection from enemy types or predefined boss list based on player progression
- Weapon Acquisition: Random drops from enemies, higher chance of finding similar weapons (based on player progression), Tiered unlocking system for better equipment
- Attribute/Buff Enhancements: Random or tiered system (e.g., low-level buffs at the beginning, powerful buffs later)
- Random Events: Pool of diverse events (e.g., ambushes, discoveries), Ensure no consecutive repeat events, Event dependencies (e.g., some events only trigger after certain conditions are met)
- Initially, we planned to develop a Rogue-like dungeon-crawling game, drawing inspiration from classic titles such as The Binding of Isaac and Soul Knight. Based on these influences, we designed the core development modules and created preliminary sketches to visualize the game's overall structure and artistic style (as shown below).
-
However, during subsequent discussions and iterations, we realized that our game lacked sufficient innovation and engaging gameplay elements. To address this, we held multiple discussions to explore possible improvements and ultimately decided to reimagine the game’s setting and mechanics. After careful deliberation, we shifted the game’s background to the vast open sea, allowing players to embark on an adventurous maritime journey across uncharted waters.
With this new direction in mind, we redesigned the game's initial concept, including multi-view ship models, conceptual environment art, and revamped gameplay mechanics (as shown below). This transformation not only gave our game a more distinctive theme but also provided a richer creative foundation for further development.
| Vessel | Terrain | Multi-view |
|---|---|---|
 |
 |
 |
- 15% ~750 words
- System architecture. Class diagrams, behavioural diagrams.
-
15% ~750 words
-
Describe implementation of your game, in particular highlighting the three areas of challenge in developing your game.
-
15% ~750 words
-
One qualitative evaluation (your choice)
-
One quantitative evaluation (of your choice)
-
Description of how code was tested.
-
15% ~750 words
-
Teamwork. How did you work together, what tools did you use. Did you have team roles? Reflection on how you worked together.
-
10% ~500 words
-
Reflect on project as a whole. Lessons learned. Reflect on challenges. Future work.
- Provide a table of everyone's contribution, which may be used to weight individual grades. We expect that the contribution will be split evenly across team-members in most cases. Let us know as soon as possible if there are any issues with teamwork as soon as they are apparent.
You can delete this section in your own repo, it's just here for information. in addition to the marks above, we will be marking you on the following two points:
-
Quality of report writing, presentation, use of figures and visual material (5%)
- Please write in a clear concise manner suitable for an interested layperson. Write as if this repo was publicly available.
-
Documentation of code (5%)
- Is your repo clearly organised?
- Is code well commented throughout?