Building Forgie Into an AI Game-Development Partner
We’ve been sprinting toward an early alpha of Forgie: a mobile-first tool that helps nontechnical creators build small 2D games through conversation.
Forgie already has many of the foundations of a real game editor. Creators can add and arrange objects, configure physics and player controls, build collectibles and counters, define simple interactions and win conditions, preview their game, and safely undo or revisit accepted changes. The underlying philosophy is that Forgie should make one small, visible, recoverable change at a time—not generate an entire opaque game in one shot.
Recently, we introduced interactive Game Plans for three supported game loops: a Coin Collector, a Button and Door Puzzle, and a Bounce/Hazard game. These plans derive their progress from the game itself and guide the creator toward one useful next action. We also experimented with Groq-powered idea classification, allowing naturally worded game ideas to select one of those plans.
Testing revealed an important limitation: choosing a template is not the same as understanding the creator while they build. Forgie can safely perform many useful actions, but its chat still relies too heavily on exact wording and local phrase matching. A creator should be able to add a Platform and say, “Make it hard ground,” without knowing terms such as “static solid” or navigating through technical settings.
That insight is shaping our next phase.
Rather than trying to teach a local parser every possible phrase, we want AI to become Forgie’s language and reasoning layer. The model should interpret what the creator means and select from a growing catalog of safe, modular game-building actions. Forgie’s local code will still resolve the exact object, validate the request, show a review, apply the deterministic change, and preserve recoverable history.
In other words: AI understands the request; Forgie remains in control of the game.
Our next proof will focus on naturally configuring an object as solid ground, movable, a trigger zone, or non-physical. From there, we can extend the same approach to Player setup, appearance, object creation, counters, interactions, and increasingly varied 2D game mechanics.
The destination is a genuine creative partner: something that understands the game being discussed, helps plan it, performs bounded work through reusable building blocks, and lets the creator shape the result through an ongoing conversation.
Log in or sign up for Devpost to join the conversation.