Panel: What Tools all Game Developers Should Have at Hand at all Times
summary
Teams favor practical, low-friction tools: CI/CD from day one and containerized Kubernetes deployments cut live-ops cost and scale. Use lightweight engines for servers instead of headless Unity/Unreal to avoid huge memory bills; the Colesius multiplayer engine touts a 20 MB JavaScript footprint. Prototyping with Twine, Tiled, Balsamiq or Airtable surfaces design problems early; heatmap analytics expose unexpected UX traps. Beware anti-piracy hacks that force demo modes — they trigger thousands of support tickets — and watch LLVM and web engines (Phaser, HTML5) reshape automation and iteration.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:27Introduction
- 1:43Ty Kelly
- 3:13Mikhail Akreshashev
- 7:22Tool Readiness
- 21:10Continuous Integration
- 24:01Tool Drift
related talks
40mWhat Tools Should Game Developers Have at Hand at all Times?
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
43mGame Developers Life Lessons
58mCurrent challenges for game developers
21mWhen the Shit Hits the (RGB) Fan: What Can Go Wrong When Making Multiplayer Games
26mGetting the Job Done: Using Everything to Make Your Game
47mMaintaining development costs while meeting the growing expectations of consumers
49mPanel: Reasons to Push the Limits - How can we Take Advantage of Next Gen Capabilities?