Fixing problems
Learning paths through this topic
The error message is gone after my AI's fix, but the scene still does not work
Some fixes silence a problem instead of solving it: the red message vanishes and the game just does nothing. This entry shows your AI how to scan its own changes for the spots where an error is caught and thrown away.
The game stutters for a moment during a scare, when exactly and for how long
Players say it hiccups at the worst moment, and your AI needs facts, not a feeling. This entry reads a list of frame times and reports each freeze with its start, length and worst delay, judged against how smooth the game was just before.
The same error appears 200 times with different scene names in it
Two hundred error lines can really be three problems wearing different names and numbers. This entry gives your AI a way to fold look-alike messages into groups with a count, so you see three things to fix instead of a scrolling wall.
I want to paste my log to an AI but it contains names, mail addresses and keys
Logs from a story game quietly collect player names, mail addresses, folder names and access keys. This entry swaps such details for labels before sharing, in a way that keeps two mentions of the same person recognisable.
A scare bug shows up one time in twenty and I cannot tell when it is really fixed
Five good runs in a row after a fix feel convincing, yet for a rare bug they prove very little. This entry works out how many clean runs you need for a given chance of the bug and how sure you can be afterwards.
I said only touch the dialogue, and the AI changed my saving code as well
A request to stay in one corner of the project is only a wish until something checks it. This entry gives your AI a check of the changed files against a list of allowed and forbidden places, with a rule that the forbidden list always wins.
Playtesters sent forty messages and many of them describe the same problem
Different people describe one broken scene in different words, so a plain list looks like forty bugs. This entry groups reports that talk about the same thing, so your AI gets a short list of problems with a count behind each one.
The game says my save is broken but not which part of it is wrong
A save that fails to load with a vague message leaves your AI guessing at the whole file. This entry compares a save with the shape it should have and names the exact place and what was found there, including the sneaky case of a missing number.
My AI proposed five fixes and the third one only works after the first
Applying a list of fixes in the order it was written can make a later one fail for reasons that have nothing to do with it. This entry gives your AI an ordering step that respects what depends on what and says clearly when two fixes wait on each other.
My latest save is damaged, which of the older backups can I still use
Keeping a few rotating backups only helps if the game picks the right one when the newest fails. This entry checks each slot for damage, for a version that is too new and for text that is not readable, and chooses the freshest good one.
My AI says every item on the release checklist is done, but one step never ran
A checklist that only ticks boxes can show green while the step underneath it has failed or was never looked at. This entry gives your AI a runner that marks such steps as blocked or unchecked, so a green board really means ready to publish.
A random scare went wrong once, and I cannot make it happen again
If every run rolls fresh dice, a bug seen once is gone for good. This entry shows how to roll the dice from a seed, so a bad run can be repeated exactly, and how to search for a seed that produces the strange situation you want to test.