Open Zomis opened 6 years ago
It's also customary in a lot of board games to determine the starting order at random, e.g., flip a coin, roll a dice, etc. I think this should also be made an option.
An option for future player-individual options (such as game deck in a Cardshifter-style game) would be to store "saved-actions" in database, such as: player:<playerid>
for partition key and sort key of the form save-action:<gametype>:<actionType>:<name-of-the-saved-action>
, to query them it's possible to use the filter "begins with save-action:<gametype>:<actionType>:
"
Concrete example:
player:cb580d1e-6c1c-4263-9618-4dbe1522f290
save-action:Cardshifter-Mythos:chooseDeck:My Aggressive Super-Awesome Greek Deck
{ cards: { 'SuperCard': 5, 'OtherCard': 3, ... } }
Then whenever it's time for chooseDeck
action, database is queried for the PK, all SK's are returned and filtered for which options are allowed.
Mark in DSL somehow which actions supports saved-actions. action(chooseDeck).saveableAction()
?
Also consider options for when there's no database backing this, possibility to store data in client? Or in a file etc.? Depending on which way the games are running.
Some players might prefer to start, others might prefer to not start. Also, in some future games there might be other options for each player to choose.