Hacking Games and Why You Should Do It
summary
Demonstrates concrete hacks: open DevTools, find game object on window, change properties like stats.gold to 999990 to win, or run a setInterval exploit to auto-click; sets candiesPerSecond to 1337 and gets 2.9 trillion cookies per second in Cookie Clicker. Shows bookmarklets to automate OGame fleet screens, and using cheat engine to edit memory in Flash games. Explains which games need backend sync to stop cheating and which single‑player games are usually left vulnerable.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:18Hacking Games and Why Should You Do It
- 2:13Check the Sources
- 6:26Candy Box
- 10:53Cookie Clicker
- 13:33Source Code
- 18:26Cheat Engine
- 25:30Questions
- 27:13The Cheat Engine
- 29:31Local Storage
related talks
58mHacks and ham from JS game‑dev for bicycle optimizations of web apps
43mHacking Minecraft
29mOnce Upon A Time, Somewhere Between Your Console And Browser
31mHacking Programmer Patterns into Age of Empires
23mThe best of Chrome games
29m"JavaScript as Play"
24mWe Will All Be Game Programmers
25mJavascript as Play A Primer on Getting Started with Video Games