Use Case Description Detail: Allowing the user to build their deck in the deckbuilding screen to be used in the game.
Related Requirements: Finished card design, finished logic of game menus in unity to allow access to the deckbuilding scene.
Goal In Context: Allowing the player to build and edit their deck in the game with local unity implementation.
Preconditions: Completion of issue #12 to have data to work with, albeit locally.
Successful End Condition: A functioning deckbuilding scene is fully developed with or without sprites, where cards can have different values and the deck does not allow the user to override the deck restrictions.
Failed End Condition: A partially functional deckbuilding scene is developed, or not functional at all.
Primary Actors: Game developer.
Secondary Actors: N/A
Trigger: The user clicks the deck creation button.
Main Flow:
The user can click on available cards to add them to the deck.
The user can click on cards in the deck to remove them from the deck.
The user can only save the deck once the requirements are accomplished (23 cards, 3 identity cards, the rest is free for the user to choose.)
Use Case Description Detail: Allowing the user to build their deck in the deckbuilding screen to be used in the game.
Related Requirements: Finished card design, finished logic of game menus in unity to allow access to the deckbuilding scene.
Goal In Context: Allowing the player to build and edit their deck in the game with local unity implementation.
Preconditions: Completion of issue #12 to have data to work with, albeit locally.
Successful End Condition: A functioning deckbuilding scene is fully developed with or without sprites, where cards can have different values and the deck does not allow the user to override the deck restrictions.
Failed End Condition: A partially functional deckbuilding scene is developed, or not functional at all.
Primary Actors: Game developer.
Secondary Actors: N/A
Trigger: The user clicks the deck creation button.
Main Flow:
Extensions: N/A