2025-group-6

2025 COMSM0166 group 6

Puck Power Clash

Your Game

Link to your game PLAY HERE

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)

Your Group

Group Member	Name	Email	Role	GitHub Username
1	Saquib Sayeed Kazi	[email protected]	Developer/ Project Manager	@Saqsy
2	Balachander Raja	[email protected]	Developer/Sound Artist	@B-alachander
3	Rohit Bhagatkar	[email protected]	Developer/ Game Mechanics	@ro-grafd
4	Adwaith Syam Sundar	[email protected]	Developer/ Game Mechanics	@adwaith911
5	Nilay Murlidhar Bhaisare	[email protected]	Developer/ Scrum Master	@NMB99
6	Nishtha Singh	[email protected]	Developer/ UI/UX Designer	@ananish

Project Report

Introduction

Puck Power Clash is an exhilarating, high-energy arcade game that takes the classic air hockey experience and adds unique twists to make every match more thrilling. While it preserves the core idea of scoring by striking a puck across a frictionless table, the game introduces a series of innovative features to increase excitement and challenge.

A standout feature is the power-up system, where special items randomly appear on the table. When a player’s puck collides with their opponent’s paddle, they gain a temporary boost, such as increased speed, enhanced hitting power, or a shield for brief defence. These power-ups force players to make strategic decisions, weighing the value of offense versus defence in the heat of the moment.

Random obstacles also add unpredictability, altering the puck’s trajectory and requiring players to constantly adjust their positioning. These obstacles break away from typical gameplay patterns, demanding quick reflexes and creative thinking.

The adjustable goalpost system further intensifies the action. If a player scores two consecutive points, their opponent’s goal expands, making it easier for the leading player to score but also placing more pressure on the defender. This dynamic change rewards aggressive play and punishes defenders who concede too many points in quick succession.

With its vibrant neon artwork and dynamic sound design, Puck Power Clash immerses players in a fast-paced, futuristic atmosphere. It’s a game that challenges both reflexes and strategy, where every second on the table matters.

Requirements

• 15% ~750 words
• Use case diagrams, user stories. Early stages design. Ideation process. How did you decide as a team what to develop?

1. Ideation Process

The idea for Puck Power Clash emerged from brainstorming sessions where we explored different concepts for a 2D game. Our primary goal was to create a game that is simple to learn but has engaging mechanics to keep players interested. We considered various arcade-style games and ultimately chose an air hockey-inspired game because it offers:

• Fast-paced gameplay that keeps players engaged.
• A well-known concept that can be easily adapted.

Opportunities to introduce novel elements like power-ups and dynamic obstacles and goal posts.

As a team, we debated different features and gameplay mechanics. We used collaborative tools like Miro and Google Docs to map out ideas and discuss feasibility. Each team member contributed ideas, and we voted on which mechanics to implement in our first version.

2. Early Stages of Design

In the early design phase, we focused on:

• Defining core mechanics: paddle movement, puck physics, and scoring system.
• Introducing power-ups: speed boost, reverse puck direction, and freeze opponent’s paddle.
• Adding dynamic obstacles like rotating barriers to increase challenge.
• Establishing a simple, visually appealing UI using p5.js.

To visualize these concepts, we created rough sketches and flowcharts to represent the game logic. We also developed wireframes to define the layout of the game elements on the screen.

Paper Prototype

• During the initial design phase, we developed a paper prototype of the game to visualize and test the core gameplay mechanics.
• This hands-on approach allowed us to simulate player interactions and experiment with different game elements before moving to digital implementation.

3. User Stories

Wewq defined the following user stories to guide development: As a player, I want to:

• Move my paddle smoothly using keyboard controls so I can intercept the puck.
• Strike the puck with different angles and speeds to outmaneuver my opponent.
• Collect power-ups that provide temporary advantages to make gameplay more strategic.
• Score goals by getting the puck into the opponent’s goal area to win points.
• Play against a friend in a local multiplayer mode for a competitive experience.
• Restart the game easily after a match, so I can play multiple rounds without reloading.

4 .Next Steps

With these requirements outlined, our next steps are:

• Developing a prototype to test paddle movement and physics.
• Implementing core game mechanics before integrating power-ups.
• Refining UI design and adding visual effects for a polished look.
• Play-testing to gather feedback and adjust mechanics accordingly.

Design

• 15% ~750 words
• System architecture. Class diagrams, behavioural diagrams.

Implementation

• 15% ~750 words

• Describe implementation of your game, in particular highlighting the three areas of challenge in developing your game.

Evaluation

• 15% ~750 words

• One qualitative evaluation (your choice)

• One quantitative evaluation (of your choice)

• Description of how code was tested.

Process

• 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.

Conclusion

• 10% ~500 words

• Reflect on project as a whole. Lessons learned. Reflect on challenges. Future work.

Contribution Statement

• 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.

Additional Marks

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?