Lunar Impact
Features
01.
General Information
02.
My experience
03.
My contribution
04.
Github
General information
Teamsize: 5
Platform: unity
Genre: Platformer
My experience
This project I made during the last period of the first year
In this project, I worked together with five others, including four game artists and another developer. This was one of the first projects I worked on, so everything felt new, but I look back on it with a good feeling. I believe I certainly positioned myself well within the team.
Together, we brainstormed ideas to create a fun and unique game. My role was to develop the concept and work out the gameplay mechanics. We collaborated well, utilizing each other's strengths to achieve a great final result.
In the end, Lunar Impact became a project I'm very proud of. It's special to me, not only because of the theme but also because of the strong collaboration and the process of creating something beautiful together.
GitHub
Due to a lack of structure in how GitHub was used, the repository eventually became disorganized. This led to the GitHub structure breaking down, and we had to make the decision to create a new repository. For this reason, you will find two links below: the first leads to the original GitHub repository I set up, while the second directs you to the lead artist’s repository, where the latest and most stable version of the project is available
Branches
This project was my first experience with GitHub, and I was tasked with setting up the repository for the team. I created different branches for each team member, allowing everyone to maintain their own workflow. While this approach should have worked well in theory, the game artists found it inconvenient to constantly switch between branches. As a result, they often ended up working in each other’s branches, which led to conflicts and merge errors. Over time, this caused the GitHub repository to become disorganized and difficult to manage
My Contribution
Due to a lack of structure in the use of GitHub, the repository eventually became disorganized. In the end, the GitHub structure broke, and we had to decide to create a new repository. For this reason, two links are available below: the first link leads to the original GitHub repository that I set up, and the second to the repository of the lead artist, where the final and most stable version of the project can be found.
SpacePart Collection
In this game, the player must collect parts of a spaceship in order to travel to the next planet (the new level). The parts are scattered throughout the level, and the player has to find and pick them all up. Once the player has collected all the parts, they can go to the spaceship.
When the player touches the spaceship, the level is completed, and the game ends.
Weapon
In the game, the player eventually encounters an obstacle that cannot be passed. The obstacle must be destroyed with a specific weapon: a laser weapon. Once the player obtains this weapon, the obstacle can be destroyed, clearing the path to proceed.
With the laser weapon, the player can not only destroy obstacles but also defeat enemies. Some enemies are too strong to be defeated with normal weapons, but the laser weapon gives the player the ability to effectively take them down.
Health
In this game, the player's health is visually represented on the user interface (UI) through a series of hearts. Each heart signifies a specific portion of the player's total health, making it easy to track how much health is available at any given moment.
As the player takes damage during gameplay, the hearts will gradually fade or disappear, giving an immediate visual cue about the player's remaining health. This system is designed to be intuitive and easy to read at a glance, so the player can quickly assess their survival status without breaking their focus on the action. It's a simple yet effective way to keep the player engaged and aware of their condition in the game