SoarKickOff2

 Soar Kickoff 2

Kicking off sprint 2 I assigned the group the tasks that they needed to complete for the two weeks that we had. I assigned myself with the UI of handling the main menu, pause menu, and the game over screen. The first thing that I tackled was the main menu screen so when people get to playtest the game they will be greeted with a screen with the name of our game, and buttons to either play, go to controls, or to quit.

 

I wanted the main menu to have a background to be something close to our game's gameplay, so I chose the mountains with chasms. During gameplay the player will be flying through chasms being met with challenges and being able to fly above and enjoy the view of the sky. I provided the player the option to look at the controls to have a clue on how the player controls work before going straight into the game.

I provided pictures for the player with text explaining what each button shown on screen does. After I got the main menu down, I went to the next task, the pause menu, so the player has the ability to stop the game in case they need to get up and stretch or drink some water.

I give the player the ability to resume the game or if they have had enough of the game they can return back to the main menu. The problem that we have right now with this menu is when we merge everything together into one scene the resume button stopped working.  The problem as of now hasn’t been fixed but research or asking for help will help with this problem. The second problem is the game will still be active even when pressing the escape key to bring in the pause menu. I will be asking for help and even research so I can have a fully functional pause menu for the game Soar. The last thing I did for this sprint was the game over screen. I stalled for a couple of days, because I thought that I was blocked from doing the UI for the fact of it involving the player. I didn’t realize that it wasn’t a problem after all when asking about the problem. I now know what blocked means while developing a game and once I knew I could do it without messing with team members' scripts I took the challenge and completed it.

The Game over screen is going to change for the fact that the font doesn’t match the game, but for now this is the screen. To test that it actually worked I created a cube and stretched it out like a platform and connected the script to the floor. The script has an if statement explaining if the tag “player” collides with the floor it will change scene to the game over screen like the player died. The player cube didn’t have any gravity to it so it stayed in the air while I hit play and didn’t understand why. I looked up my problem and all I needed to add to the cube was a rigid body and solved my problem that I was facing. The buttons work perfectly. The scenes change when the buttons are pressed, but one still needs fixing. Once all the UIs were done, I went to the build and profiles to align the scenes in order. In the scripts I plugged in the number of what each scene was to have fully functional UI scene changes. Sprint kickoff 3 is about to start and as producer I have tasks ready to give out and it's going to be another 2 weeks of grinding.