Gameflow

To understand Pac Macro as a way of life, see the official specification.

Gameflow

As of the moment, gameflow consists entirely of the following combination of administrative triggers and game change triggers.

• Game initialized or reset (manually triggered by administrative endpoint)
  • Game state INITIALIZING
  • All player states UNINITIALIZED
  • All Pacdots eaten == false
• Game started (manually triggered by administrative endpoint)
  • Game state changed from INITIALIZING to IN_PROGRESS (required precondition)
  • All players with states READY changed to ACTIVE (automatic)
  • No change to Pacdots
• Pacman eats a Pacdot (i.e. Pacman's location is updated to be near a Pacdot while the game state is IN_PROGRESS)
  • No change to game state
  • No change to player states
  • The Pacdot within proximity changed to eaten == true (automatic)
• Pacman eats a Powerdot (i.e. Pacman's location is updated to be near a Powerdot while the game state is IN_PROGRESS)
  • No change to game state
  • Pacman's state changed from ACTIVE to POWERUP for 60 seconds, then back to ACTIVE (automatic)
  • The Powerdot within proximity changed to eaten == true (automatic)
• Pacman eats all Pacdots and Powerdots
  • Game state changed from IN_PROGRESS to FINISHED_PACMAN_WIN (automatic)
  • No change to player states
  • All Pacdots eaten == true (required precondition)
• Pacman contacts a Ghost while Pacman is in the ACTIVE state and the Ghost is in the ACTIVE state (triggered by manual tag on mobile application by both players)
  • Game state is changed from IN_PROGRESS to FINISHED_GHOSTS_WIN (automatic)
  • The Pacman's state is changed from ACTIVE to CAPTURED (automatic)
  • No change to Pacdots
• Pacman contacts a Ghost while Pacman is in the POWERUP state and the Ghost is in the ACTIVE state (triggered by manual tag on mobile application by both players)
  • No change to game state
  • The Ghost's state is changed from ACTIVE to CAPTURED (automatic)
  • No change to Pacdots