[TODO] Menu **Part 1**

[Bratah123]

Abstract

The menu is the first thing user's should be able to see when they first enter the website. This menu consists of various buttons.

One of the best implementation of an online game simulator is Pokemon Showdown Please take inspiration from here aswell, and some of it's techniques.

Details

As a starter, these buttons shouldn't have to be connected to anything or do anything. This should be the starting point of the project.

Art Example

Image of a Game Main Menu

Image of Pokemon Showdown

Tasks

• [x] Generic Button
• [x] Play Button
  • [x] Login (#17)
    • [ ] Else, just a field to input display name
  • [ ] Field for Lobby ID (Checks if the lobby exists)
    • [ ] Enter Button
  • [ ] Deck Selection Menu (if logged in)
    • [ ] New Deck Button
    • [ ] Checks for saved decks
• [x] Create Deck Button
  • [ ] Save Deck (if logged in)
• [x] Settings Button
  • [ ] Display Name
  • [ ] Music
  • [ ] Sound Effects
  • [ ] Light/Dark Mode?

[KOOKIIEStudios]

A few questions:

1. Should the menu be part of the Phaser application? Or should the website only load up the game app after a match has been found, and the players can be connected?
2. And on a similar note, should the deck builder be part of the same Phaser application? Or should it be its own standalone thing?
   • I.e. website that directs the players into different apps, vs one giant Phaser-based app
3. Are the spectating function going to be a thing?

[Bratah123]

A Few Answers:

1. I think for simplicity for our back-end we should continue using Phaser for the menu
2. I believe the deck builder should be in Phaser aswell.
3. Spectating functionality will be an extra thing past MVP and release I believe.

[KOOKIIEStudios]

In that case, I will look up custom buttons and menus post-brunch