3.1

Changelog

• Fixes GrabCards failing verification when grabbing 5 or more cards
• Fixes commands not verifying when they contain a hidden card

Security enhancements

Changelog

• No longer possible to impersonate a user - user actions must be signed
• Library updates
• Join game API changes including signature: signature and logical clock validation
• Renamed package to cardgame-simulator

Bug fixes

Changelog

• Personalise game restarted event so the right player can display their hand

Gathering cards and points

Changelog

New features

• You can now configure a game with players having gathering piles
• Define how points are given based on cards players have gathered. A sample deck for https://en.wikipedia.org/wiki/Bastra is provided

Bugfixes

• Logical clock syncing fixes

Play game via websocket

Changelog

• Websocket replaces server sent events and game actions done via http. This helps reduce the probability of throttling if game is played via reverse proxies (e.g. ngrok)

Idempotent events + new configuration

Changelog

Gameplay improvement #3

Avoid duplication of events and players going out of sync by introducing a logical clock protocol based on vector-clocks

Discard cards in the beginning of the game #4

There is new configuration support now for the starting rules.
A discardAll can be configured in the starting rules with the names of the cards that should be discarded before the players start the game.

First cardgame server release

First release

Server supports:

• Game admin creating games

• Multiple players can join the game

• Actions supported:

  • Draw cards (from top and bottom)
  • Borrow cards from deck (must be returned by end of turn)
  • Players switching turns
  • Stealing cards from each other
  • Throwing cards to discard pile
  • Retrieving cards from discard pile
  • Throwing dice
  • Shuffling hand
  • Returning a card back to deck at any position, face up or face down
  • Players can leave the game if they have an empty hand
  • Players can switch direction of play (just indicative)

• Actions are done through http

• Results are retrieve via a server sent event stream

• If clients get out of sink they can retrieve the whole game state