Game
Project Smile
7 years ago

Devlog #13 - Pages and Menu.


Greetings

I’ve been working on the menu system for the most part. This has included work on the page system as the pages are now accessible from both the main menu and the pause menu. I am also preparing for the final push together with Max.

The Main Menu

Earlier the main menu was being worked upon by Erik who gave it a fitting creepy look.

5d0a77fb2572d.png

The link to the page system is hidden in this screenshot because the player has not yet picked up a page. Once the player has done that the menu changes the next time the menu is accessed. This is no matter if the player goes back to the main menu from the pause menu or quit the game and restart. PageGameInstance loads the save game for pages before the menu needs to know if there is any pages the player has picked up.

5d0a77fd909bd.png

PageGameInstance

Gameinstance is a base class handling data independently from levels and is created before the first level is loaded. There can only be one of them running at a time and the class selected cannot be changed during play. PageGameInstance is the subclass used in this project.
All the page functions from SaveLoadSystem was moved there and it also holds a reference to a PageDisplay object.

Displaying pages

PageDisplay is the class used for displaying pages. PageDisplay contains buttons to turn pages and will always start at the earliest page the player has discovered if accessed from a menu. The red exit button returns the player to the previous screen, either the game, the main menu or the pause menu.

5d0a7800742c1.png

The Pause Menu

The pause menu is displayed when the player presses the p or escape key.

5d0a78034ea00.png

The shot was against a black background in my test level.
It has the added options of being able to go to the main menu and resume the game. The load game button is not implemented yet because doing so will require additional work with the save/load system.

The final push

My personal goal during this project has been working with the save/load system and with the project nearing completion the final pieces has to be assembled. As I have not worked on level design the last work will have to be made together with Max.

Our current plan is to make the game load the interactive objects status at the beginning of each level. We also need to add buttons to the objects in the MySaveGame class and a string or int to handle the current level the player is in. We probably need to add an integer for the current checkpoint.

One big decision we need to make is how much data to save.
If the levels are one-way passages then there is no need to add much more data. If there is two-way passages then the current system will need to be expanded to handle arrays of arrays in order to store the status of objects in multiple levels.

Others

Dennis has been working on the AI project and has added proper battery meshes. Erik continues work on the flashlight.
Max has worked with level design, level streaming, interaction images, doors and buttons.



0 comments

Loading...

Next up

Path of Kami: The Evolution of the Lore

Heya there! I really wanted to show you all a little gameplay preview of the first boss fight i'm currently working on i hope you like it ^^

Have a good Boi

Runestones: from concept to in-game model🗿

"Our work is never over" they said.

An infected room from the second part of Cybel ! Are you up for some cleansing?

Today I tackled drawing different variations of facial expressions for one of the main characters in Eden. What do you think of it? :) Eden: https://gamejolt.com/games/Eden/592698

My D&D art for my family so far (WIP if you couldn't tell)