The developer of Xenodochium built the game with Gemini, hit repeated errors, and worked around them by starting a fresh chat.
The developer of Xenodochium built the game with Gemini, hit repeated errors, and worked around them by starting a fresh chat.
The developer talked Gemini through the goal, expectations and existing code, then narrowed the scope over a few prompts before asking for output. Gemini returned an updated script, then the chat kept failing with a generic error. The developer opened a new chat, fed it all the related scripts plus the error, and iterated on its fixes until one worked.
They ended up with a working inventory manager for basic resources, with placeholders for more complex items. Along the way Gemini's fixes introduced new errors, and its internal markup leaked into the code output.
Chats can stall with 'Something went wrong'. Starting a fresh chat and re-supplying all related scripts got past it. The developer is considering one chat to draft the prompt and another to write the code.
Help me build an HTML5 browser game called [game name] in this project, where the player [core mechanic]. Start with a minimal playable version using plain HTML, CSS and JavaScript, then add [features] one at a time. After each change, run the game and fix any console errors before continuing. You're done when the game loads and plays with no errors.
Claude Code got an old DirectX game running on modern hardware, decompiled much of it, built a headless parallel runner, and now writes full level guides with screenshots.
Make pulls contracts from Gmail, Gemini extracts the term and notice period, and a Sheets register emails the owner 60, 30 and 7 days before each deadline.
A self-hosted n8n job reads your calendar, unread email and Notion tasks at 7am and sends one short brief of what matters today.