Patrick God posted new notes

I don't have a reliable count of the prompts it took to build Fallen Nights. Some asked for features. Others explained a bug, included a screenshot, or changed the direction. Sometimes I just had to explain why the last result wasn't what I wanted. That part belongs in the story too. The first playable version came together quickly. Getting from there to the Steam demo took many rounds of playing and fixing.

"Invalid request" leaves the person using your app with another problem to solve. In my Minimal API validation example, the response names the field and explains the rule: Quantity must be between 1 and 100. That gives the interface something useful to show next to the input. Rejecting bad data is only part of the job. The person also needs to know how to fix it.

After one playtest, I thought my son did not like building in the learning game I made for him. That was my explanation. It was not what I had actually seen. A later test changed the picture. He liked building. The island already looked finished, so adding something barely changed it. Before asking AI to rebuild a feature, I want to separate what the player did from my guess about why.