UQdeco2800 / 2022-studio-1

MIT License
4 stars 0 forks source link

Guide Book Implementation #207

Open ChevScore opened 1 year ago

ChevScore commented 1 year ago

Description

The purpose of the guide book is to inform users of the game, its goals, controls, mechanics, in an aesthetically pleasing way. For goals, the guide book will briefly describe what the end goal is as well as some of the different aspects of the game. The controls and game mechanics 'page' will inform users on how to play the game, specifically what key binds exist and what movement controls are there.

Milestones

Goal 1 (16th September)

Goal 2 (19th September)

Goal 3 (23rd September)

Goal 4 (25th September)

Due on the 5th of September

Extras (optional)

Documentation

Members

Olivia Leighton (@Olivialeighton) Bagus Prabowo Reksoprodjo (@baguspr) Tara-Jade Garnsworthy (@tgarnsworthy) Syed Muhammad Zahir (@ChevScore)

jonooallen commented 1 year ago

How will the user access the guidebook? Are you guys thinking a key-bind would be best?

ChevScore commented 1 year ago

@jonooallen we are thinking that since the guide book will explain all the keybinds in the game, it will be accessed through a button click that appears on the main game screen

jonooallen commented 1 year ago

Yeah that makes sense. Will the user be able to access it while the game is being played or only ever through main game screen?

ChevScore commented 1 year ago

@jonooallen it should be accessible through the main game screen (not main menu screen) while the game is being played. It would be, like the shop or settings page, a full screen like pop-up that temporarily pauses the game. I would need a list of key binds from teams, probably starting from your team.

jonooallen commented 1 year ago

Oh I see yeah that sounds good. Structures should need no key binds pending building UI and Shop integrating their code into the game. Unified Grid System should also not need keybinds as it is a backend service.

luke4641942 commented 1 year ago

Just for note, we spoke at the studio on Wednesday about what should be put in the wiki in terms of Main Character Features and Resource Buildings and were previously implemented by us (team5).