Building a Game Engine for 300 DEFCON Hackers to Smash
summary
Custom Go engine called regime runs all game state and exposes an API, six Slack bots (RTM) talk to it, and a solverbot continuously tests internet-hosted synthetic data. 300+ players on 146 teams compete for a $10,000 prize; one team finishes the whole game, one team gets banned for abuse. Uses Gorm, httprouter, EC2/RDS and DigitalOcean, autosaves answers for hot swaps, saves about 36 hours of human work and costs a few hundred dollars in infra.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:35Welcome
- 2:56DEFCON 2015
- 6:30Constraints
- 7:06Backend
- 7:16Vision
- 8:22Design Process
- 9:37Architecture
- 11:27Bots
- 12:52Go Architecture
- 14:07Using Bots
- 15:29Route Map
- 15:41Platform abstraction
- 16:06Platform interface
- 16:37Bot base
- 17:16Message handling
- 17:56Handler function
- 18:55Leaderboard
- 19:47Launch
- 21:44Abuse
- 22:31Platform
- 22:54Map
- 23:28Results
- 23:56Prizes
- 24:08Questions
related talks
37mBuilding a Game Engine for 300 DEFCON Hackers to Smash
41mFunctional Game Engine Design for the Web
06mLT: Elixir for Gaming! Using Network to Power a Sophisticated Multiplayer Simulation
35mBuilding Game Engines in Elixir
44mBuilding an Indie Game in GO
30mGaming at Scale: What we learned from building our own multiplayer environment
11mGames People Play
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.