Besides the set-up for the presentations/check-ins on Friday this past week was establishing the backbone for saving and loading a player’s card collection, utilizing Unity’s built-in JSON utility to record changes. Working under this premise I started on the design for title, login, and registration screens with the associated buttons.
I originally started out with each of the screens (main menu, login, and registration) as separate scenes within Unity, but found that changing scenes took more processing than treating each screen as its own prefab. By doing this I could fit all the information and assets within a single scene, turning prefabs on/off as needed. This also enabled me to not worry about continually preserving the information between scenes until changing over to the gameplay scene.
The login screen will be the first screen that a player will encounter, requiring them to either access an existing account, or to register a new one to begin playing.
If a player does not already have an account, they can set one up by choosing one of the two starter deck factions and with a username of their choice.
The Title screen is primarily going to be a where the player chooses what they will be doing, playing against the computer currently or managing their deck.
Beyond the GUI elements that have been implemented, each screen has required behavioral scripts to manage their behavior, buttons calling the correct screen, text input being saved, etc. I am still experimenting with the JSON format and Unity to find the best way to load a collection of cards, mark that the player has access to a specific card, or some other approach. As I said, still trying to work that out.
Going forward, I am anticipating that persistent accounts will be fully implemented by week 6, as well as the logic to reward a game winner with a new card.