Working with AI
Learning paths through this topic
My images are small files, yet the game runs out of memory on older phones
The download is tiny and the game still crashes while loading. A picture takes far more room once the phone has opened it than it does as a file. This entry adds up what your pictures really cost and names the ones that eat the budget.
My level checker says a puzzle is impossible, but it may just have given up
AI-made puzzle levels often get a quick check that answers yes or no. A silent no can mean the level really cannot be won, or that the checker ran out of patience. Here is a solver that tells these two answers apart and returns the shortest way when there is one.
On some levels nobody can reach three stars, because the target was a guess
The AI wrote a target number of moves for each level, but never played them. Some targets are better than perfect play can reach, others are so loose that three stars come for free. This entry compares each target with the real best result and names the levels that are off.
Translated button text spills out of the button on small phones
The English labels fit nicely, then the German ones arrive and half a word hangs outside the button. Squeezing the screen only shows it on some phones. This entry gives your AI a quick check that lists every label that will not fit and the biggest letters that would.
Playing on two devices, the last save wipes out what I earned on the other
A player finishes levels on the phone, then plays a bit on the tablet, and the tablet's older save replaces everything. Choosing one save and throwing away the other is the easy answer and the wrong one. This entry merges two saves field by field, including coins.
Undo brings back the wrong board or changes old moves too
You press undo and the board jumps to a state you never had, or fixing the present quietly rewrites the past. The cause hides in how the saved states were copied. This entry gives your AI a checker that shows exactly where the copies are tied together.
The AI changed twenty files and I cannot tell which ones could break my game
After a big edit you cannot read everything, and the longest change is rarely the most dangerous. This entry gives your AI a short ranked list of what to look at first, based on where the file lives, so a tiny edit to the save code outranks a huge edit to level data.
My AI said it finished the boss fight but parts of it do nothing
AIs often leave empty stand-ins for the parts they meant to do later and still report the job as done. This helper scans the code for those stand-ins, notes, empty bodies and functions that always give the same answer, and lists them by line.
My AI left player2.js and player_new.js next to my real player file
Over a long session an AI sometimes writes a new version of a file next to the old one instead of replacing it, and then edits the wrong one. This helper finds files that are almost the same and shows which one the rest of the game really loads.
My AI rewrote a file and the dash I had before is no longer in the game
When an AI rewrites a whole file it can drop things it considers unused. This helper compares the old and new text of your code and lists the abilities that disappeared, which ones were probably only renamed, and ignores code that is merely commented out.
My AI keeps trying the same fix for the same crash and gets nowhere
After a few rounds an AI can circle: the same failure again and again, or one fix that brings back an older failure and a second that brings back the first. This helper notices the loop in your error messages so you can change the approach in time.
My AI says the shooter is finished, but I cannot tell if it really is
A confident "done" is not a result. This small runner makes your AI turn each promise into a check that must answer yes, and it treats a silent or crashing check as not done instead of quietly counting it as fine.