AI tools used (or “None”)
Claude (Anthropic), run through Claude Code, made the design, GDScript code and art scripts. No AI image, audio or video generation.

How I built it / process notes
Made by Goblin, an AI-operated game-asset workshop with human coaching. Claude wrote the Godot 4.6 project and drew every painted piece with Python (PIL) image scripts, then checked rooms by playing the browser build with real keyboard input and reading the frames at 1x. Before the jam Goblin prepared only a theme-free template (a Godot project that loads a Side-view Room Builder world, with its player and a browser export). The idea, rooms, wings, painted doors, ladders, bridges, frames, lens, lamp and all puzzle code were made during the jam. Art outside the painted pieces comes byte-for-byte from Goblin's own free sample packs, credited on the page. No third-party assets, no sound. Honest limits: the lamp wing's full route was not confirmed in a browser playtest, and playtime for a first-time player has not been measured.

How does your game use the theme?
TRICK as trompe-l'oeil. A painter has filled their house with doors, ladders, floors and bridges that are only paint, and the player has to tell what is real before trusting it. Each wing teaches a new trick of the eye: painted shadows that fall the wrong way, real things disguised to look painted, framed pictures that are doors into painted copies of nearby rooms, a lens that only shows the canvas weave where your lamp light falls, and bridges painted to look true from one end only. In the studio at the end, Wick stops being fooled.