One Button Ball is a client based game made for the Charity called "Everyone Can" which specialises in providing gaming experience to disabled children. It was a game we had to do as a part of our Professional Development Coursework.
The main focus of the game was that it should be a product that can be played entirely by the use of One Button while maintaining the "fun" aspect. Although the game has been completed for the coursework it also has a potential for expansion which we are planning to do shortly.
I was in a team of five and I was involved in programming aspect of the game.
What I did:
- At first I was involved in researching the aspects of games that can easily get overlooked. So I started looking at the screen transition techniques.
- Co-wrote the code with the project lead in real time and I looked after the codes that had been written by the project lead. Especially while developing the multiplayer feature and the addition of "arena modifiers".
- Sketched additional level design ideas which later were improved upon by the project lead.
- Mainly did programming work such as:
- Separated scoring system for multiplayer mode.
- Fixing a bug where the colours of the game balls were not being displayed after building the game.
- Adding levels.
- Fixing a bug where the level randomisation and level counters were not working properly.
- Fixing a bug where the score would not register to the correct player after the camera is switched between the players.
- Adding levels and ending scene.
- Displaying texts every time a player scores to make the game visually better.
- Did other non programming things like initialising documentation work with the project lead. For example we had to pitch our game to the university tutors for that, we needed a plan. So i took it upon myself to go to the project lead's house and initialise the plan for the pitch. Likewise, we also had to prepare the Technical Document for the game, so again I and the project lead initially identified the topics that we had to explain and include in our document .
- Where I later wrote the sections like Implementation, Player Controller, Arena Modifiers, Two Player Mode and the Game Modes in Implementation section as well as Controls of the User Guide Section. I also wrote the "Hand Over Report" section specifically the Official Unity Documentation and The Source Code sections. With it the How it works, Aesthetic,Score Multipliers and Scoring sections of the Game Balls and Score Multipliers section were also written by me.
What I learned:
- The most important thing would be team work and communication between the team members. I cannot say enough about the importance of effective communication and I have got the experience of effective team work through communication.
- Version Control through GitHub. I previously had some experience in using GitHub. But while making this game, I have learned how to control the versions, branching and merging in more depth. I can say that I am fairly confident in using version controls now.
- Different project management techniques like rapid prototyping, Kanban and Scrum. Even though we used rapid prototyping technique for this project, I got to learn that there are other management techniques as well.
We later had to showcase the game where different people ranging from students, employers , tutors had come to see the different projects.
Role: Developer/Designer/Programmer