Game Backend Concept

[Foxhunt]

Data shared with the Backend

• game configuration
• game id
• player name/avatar
• current game challenge/score
• item scanned
• multiplayer challenge
  • lobby
  • matchmaking?
  • live challenge data?
• completed challenge/game statistics (e.g. performance, score, time)

Backend Components

• Git-JSON-API/CMS configuration
• broker supporting: live game data updates (player name, avatar, game progress, metrics)
• database: complex queries (e.g. dashboard, internal statistic page)

Questions

• multiplayer challenges
  • how should the matchmaking work (front end)
  • what data needs to be synced during the challenge
  • how do clients sync each other
• do we need a dedicated game logic service

[xadh00m]

Life of a KSM Game

• start (with selected avatar or default) and check for a cookie which contains an old game id
• if there is a cookie ask the player if he wants to resume or restart with scanned avatar
• in case of restart or no cookie
  • create a new game id (uuid)
  • asks the player for his name
  • allows the player to change the avatar
  • store game id, name and avatar in cookie
  • connect to backend with game id as client id (on same host like the webapp)
  • set name, avatar and current challenge (to 1)
• or
  • connect to backend with game id as client id
  • read current challenge from backend
• show player where the next QR code is [player scans QR code]
• load challenge url with game id in iFrame [player completes challenge]
• increase current challenge in backend
• show player where the next QR code is until last challenge completed
• show final score

Life of a KSM (single player) Challenge

• read game id & config location from query string
• run challenge logic
• send backend when challenge complete
• send backend challenge statistics