Ask HN: Platform for 11 year old to create video games?

Hacker News Discussion ↗

Overall Focus

  • Thread asks: what platforms suit an 11‑year‑old who already prototypes games (e.g., in PowerPoint) and wants to make “real” video games.
  • Responses span visual tools, full game engines, narrative systems, modding, and even tabletop design, plus broader advice on teaching and safety.

Block-Based and Beginner-Friendly Tools

  • Strong support for Scratch and Scratch-like environments (Snap!, PenguinMod, Blockly, Microsoft MakeCode / MakeCode Arcade, Gamefroot, Bloxels).
  • Pros: very low friction, instant results, many built‑in assets, lots of tutorials, easy web sharing and “likes” keep motivation high.
  • Some find Scratch clumsy for larger projects or too “toy-like” for 11+, and worry about social/meme distraction.
  • Snap! and MakeCode are highlighted as “higher ceiling” successors, with the ability to transition to text (JavaScript/TypeScript, Python-like GDScript).

Engines with Coding (2D/Retro & General-Purpose)

  • Repeated praise for GameMaker, Godot, pico‑8, TIC‑80, Love2D, microStudio, Construct 3, RPG Maker, GB Studio, and similar 2D‑focused tools.
  • Advantages cited: fast “idea to pixels on screen” loop, constrained environments that prevent over‑scope, strong tutorials, and paths from visual logic to scripting.
  • Godot gets many endorsements as a “real” engine with an approachable language and no licensing surprises.
  • Some argue against “niche/toy engines” due to limited ecosystems and recommend going straight to mainstream tools (Unity, Unreal) if motivation is high; others say those are overwhelming for most 11‑year‑olds.

Narrative and Hyperlink-Based Game Tools

  • Twine, Adventure Game Studio, Ren’Py, Decker, textadventures.co.uk, and interactive fiction competitions are proposed for kids already making story-driven, branching games.
  • Seen as a natural evolution from hyperlinked slide decks, with optional scripting when ready.

Sandbox, Modding, and In-Game Editors

  • Suggestions include Roblox Studio, Minecraft (command blocks, mods), Fortnite UEFN, Dreams, Little Big Planet, Game Builder Garage, various map editors (Warcraft 3, Starcraft, Quake/Hammer), and tabletop simulator-style tools.
  • Benefits: riding the “where friends are” network effect, rich examples to remix, and strong motivation from collaborative play.
  • Roblox specifically is heavily debated:
    • Pro: thriving kid-centric dev ecosystem, lots of tutorials, kids can learn Lua, some make real money.
    • Con: accusations of financial exploitation, dark patterns, and serious safety concerns; some advise avoiding it entirely.

Tabletop and Non-Digital Game Design

  • Several argue to start with board/card games or paper prototypes to teach game design fundamentals and “find the fun” before coding.
  • Tools like Tabletop Simulator and print-on-demand services are suggested as bridges from paper to digital.

Teaching Philosophy and Parenting Considerations

  • Disagreement between:
    • “Pick an adult tool and learn together; don’t dumb it down.”
    • vs. “If tools are too hard, kids lose interest; prioritize fun, quick wins, and avoiding frustration.”
  • Some emphasize that the child may be more of a designer than a programmer; tools should enable expression, not force heavy coding early.
  • One long comment warns broadly about the modern gaming ecosystem (addiction mechanics, unsafe platforms) and suggests alternative constructive activities; others push back, calling this overly pessimistic.

AI-Assisted and Web-Based Paths

  • A few mention using JavaScript/HTML5 with lightweight game libraries (p5.js, Phaser, kaboom/kaplay) plus YouTube tutorials and LLMs/editors (Cursor, AI game makers) to smooth over coding hurdles.
  • Opinions vary on whether AI help enhances learning or risks obscuring fundamentals.