Playtest Simulator

[r0adkll]

Idea

Create a "dumb" simulator that allows the user to play out a game by giving them all the possible actions and letting them handle all the enforcement and rules. Such as letting them place cards from hands, choose attacks, apply abilities and damage, tools, supporters.

This feature should at least govern the basic rules of a turn, such as:

• Dealing / Prizes
• Turn draw
• Status effects (burn/poison/confusion/paralyze)
• Only allowing one supporter
• Only allowing one stadium
• Win conditions (deck out/prizes)

Stretch Goals

Enable multiplayer support via an invite code/link that you can send your friends and play out turn by turn simulator game to play test.

• Uses Firebase Firestore to coordinate the game
• Push notifications when the user finishes there turn, potentially with metadata about what happened ("r0adkll knocked out your X card, now it's your turn!")

Status

1. [x] Pre-planning
2. [x] Design
3. [x] Architecting
4. [ ] Implementation (In Progress)
   1. [x] Build Core Data Structure
   2. [ ] Build UI components
   3. [ ] Build Animation components
   4. [ ] Build Gameplay Engine
   5. [ ] Build Persistance Management
   6. [ ] Build Playtest Analyzer
5. [ ] Beta Testing
6. [ ] Release

[r0adkll]

~Due to my error of how I architected this application to store the entire card data in decks in Firestore, I was unable at the time to store Attacks data on cards. So all the user's decks are composed of unoptimized card data that is also an incomplete form which would require me to refresh their data from the API.~

~So there needs to be an upgrade mechanism that converts these deck objects to use an array of the card's Id instead of the whole object and have the application load the cards from the API and cache them.~

~This problem will be a necessity to complete the simulator~

Edit: ~I suppose this issue could be mitigated by also having a sort of 'loading' screen when starting play test simulations that loads/reloads all the card data from disk cache or the API This would probably be the path of least resistance~

This is now resolved as of https://github.com/r0adkll/DeckBox/commit/4466f213d6a0d576fa02aad6698923fad95b3d0c

[ivantyr]

In case this might be of use a popular japanese website seems to have a simulator like this https://www.youtube.com/watch?v=7NmGGibhvWI it grabs the decks using the IDs of the decks people save on that site

This isn't multiplayer but it can give you a good idea on how well a deck setups itself and whatnot