Battle Sphere-Nightmare

Game arena 2
Game Arena 1
Home Screen
End Screen
Instruction Screen

Introduction

The project aimed to develop a game similar to Agar.io in Java, involving multiple collaborators. This was an exciting challenge that combined game development, version control, and collaborative coding.

What it does

"Battle Sphere" immerses players in a dynamic universe where they navigate their spheres, aiming to absorb others while avoiding threats. Core game mechanics include player movement, growth upon collisions, and player elimination based on size differentials.

How we built it

Project Structure and Collaboration: We set up a GitHub repository for efficient collaboration. With each collaborator handling their unique branch for specific features, we could isolate changes and reduce merge conflicts.
Graphics and Design: We emphasized the game's aesthetics, by using the Bagel Package(https://people.eng.unimelb.edu.au/mcmurtrye/bagel-doc/), curating the theme, background, and player image. A deep dive into various resources helped us cherry-pick unique images which we later tailored to resonate with our envisioned game style.
Collision Logic: Through iterative testing, we formulated algorithms to discern player collisions, deduce collision outcomes (like merging or elimination), and recalibrate player sizes post-collision.

Challenges we ran into

Our journey wasn't without hurdles. Merging different branches and addressing merge conflicts proved demanding. Moreover, hunting for appropriate images to align with our game's essence was a meticulous task.

Accomplishments that we're proud of

Functional Gameplay: We breathed life into the core game mechanics.
Smooth Collaboration: Leveraging Git branches and maintaining open communication lines, we navigated the intricacies of collaborative coding.
Custom Graphics: Our game boasts a distinct visual character, thanks to the tailored graphics.
Collision Logic Mastery: Achieving precise and fair collision detection and resolution has been a highlight.

What we learned

Planning: The significance of having a lucid project plan before diving headfirst into coding can't be overstated.
Communication: Consistent team interactions are the bedrock of ensuring synergy and evading misunderstandings.
Version Control Nuances: A robust grip on Git and version control best practices is indispensable for seamless collaboration.
Embrace Flexibility: Game development is fluid. It necessitates adaptability, especially when revisiting designs and code.

What's next for Battle Sphere

Building on this foundational experience, we envision enhancing "Battle Sphere" with more features, refining gameplay mechanics, and potentially expanding the game's reach to a broader audience and could possibly be a mobile game. Our journey has just begun!

Github repository: https://github.com/winarmarco/cissa-hackathon

Technologies Used

Bagel

Authors

Daniel Stanley Angdinata, (Student ID: 1360689)
Peter Darmadji, (StudentID: 1360675)
Winar Marco, (StudentID: 1360686)

Acknowledgements

This project draws inspiration from Agar.io, a popular online game known for its unique gameplay mechanics and engaging multiplayer experience.

Demo link

Demo Video

Built With

bagel
java

Submitted to

Catalyst 2023

Created by

I worked on the game design such as implementing the home screen and how the game stops once the timer ends. The unique feature of the players such as the skin and different shapes of particles are added as well to enhance the creativity of the game. The foundations of the movement created by my peers are then developed further to create similar logic for a concept of a "multiplayer" game. Finally, we made some minor changes and fixed few bugs to improve the game and enhance the game to reach its final state of perfection.

danielstanleyy Angdinata
I worked on the back end of the BattleSphere game. These are the foundations of the player-to-player and player-to-particle collision system, player scaling and scoring system, multiplayer behavior, player out-of-bounds behavior, creating a player entity with all its attributes and methods, implementing background music, choosing the perfect non-copyright audio, and laying out the idea for this game in the beginning. All of these are not solely created by me but the team as a whole with Winar Marco and Daniel Stanley also tampering with my codes which led to further improvements.

Peter Darmadji
Computer science sophomore at The University of Melbourne passionate about learning to be a full-stack developer
Winar Marco