Your AI builds the game, we give it the workbench.

8 steps

A jump that feels good

Your first platformer, or one whose jump feels off and you cannot say why.

8 steps

A story that holds together

Any game with scenes, choices or characters, before it has many of them.

8 steps

Fair randomness and loot

Anything with dice, drops, crits or chests.

8 steps

Combat that reads clearly

Action games where hits feel mushy or unfair.

8 steps

Progress that keeps players going

Games with levels, skills, unlocks or a reason to come back tomorrow.

6 steps

Saving that never loses a game

Any game longer than one sitting, before the first update ships.

Stop one player from flooding the game with moves or actions

A modified client, or just a browser tab coming back from sleep, can send hundreds of actions in one go and move a character far beyond what is fair. A strict limit per second blocks honest bursts too. Here is the allowance idea that blocks floods but forgives a hiccup.

Catch answers whose tone and effect point in opposite directions

A warm-sounding line that quietly costs the player a friend, or a harsh one that earns praise, feels like the game lying. This entry compares what each option says with what it does, and finds choices where a gentler answer is punished more.

Pay a double-speed boost correctly when it runs out while the player is away

A ten-minute boost is easy while the game is open. The trouble starts when the player leaves after four minutes and returns an hour later: giving the boost for the whole hour is too generous, giving none is unfair. Here is the exact split, plus the guard against clocks that go backwards.

Make units walk around swamp and mud, but cross it when the detour is huge

Different ground should cost different effort, so roads get used and swamps get avoided. The catch is a shortcut in the search that quietly makes it return worse routes once the ground costs differ. Here is what to watch for.

Find the short freezes in a play session and say in which place they happen

Players say the game stutters, but an average speed hides it: most moments run fine and a few freeze for a blink. This entry shows how to find those freezes in a list of frame times, group neighbouring slow frames, and report how much time each one cost and where it happened.

Two queued buildings both count on the same gold

The player queues several buildings while the treasury looks fine for each one alone. Then the first starts and the others fail, or worse, all start and the treasury drops below zero. This entry shows how to keep a promise about money.

How to Build a Branching Story That Does Not Break

Model every scene with what it needs and changes, then have a checker walk every path. It finds dead ends and gives you the exact path to each one.

How to Build Quests That Do Not Get Stuck

A quest gets stuck when a step needs something that is gone. Model who holds what, and a checker shows the exact path to each stuck quest.

How to Keep Your Game Characters Consistent

Put each character's fixed facts in a model and have a checker walk every path. It shows the exact scenes where someone acts against their sheet.

How to Make a Game Story Without Errors or Plot Holes

Have your AI model your story and run a checker over every path. It names the exact scenes that break a rule, so you fix real errors, not guesses.

How to Make Player Choices That Really Matter

A choice matters when the game remembers it and shows the result later. Model every choice and have a checker find the paths where nothing changes.

How to Make Save Games That Keep the Story

A save must store what happened in the story, not only where the player stands. Model saving and loading as steps, and a checker finds what gets lost.