ogrechkoandClaude Sonnet 5
c035650063
Full redesign of the Maze template (same templateType: "maze" — plain text column, no migration needed): dots (*) to eat, power pellets (O) that frighten ghosts, ghost spawns (G, 0-4), and continuous glide movement with buffered turns instead of one-cell-per-keypress. Win condition confirmed with the user explicitly: collect every dot and pellet, then reach the exit — kept the exit tile rather than switching to classic Pac-Man's "no exit, board-clear wins," since this app's maze identity is built around it. Ghosts chase via BFS pathfinding (reusing the same BFS shape the maze's own reachability check already used, just retargeted at the live player position each tick) and flee via simple greedy distance-maximizing when frightened. The reachability check itself generalized from "is the exit reachable" to "is every dot, pellet, and the exit reachable" — same guarantee, now covering the actual win condition instead of just the exit. Verified precisely: a maze with a reachable exit but one walled-off dot is correctly rejected. Continuous movement is tick-based, not real physics: a repeating timer steps the player in the buffered direction (or continues straight) if open, tweening the sprite's pixel position between cells for a glide feel rather than snapping. Same 3-lives-on-capture, coarse-grained resume (position + collected keys + lives, ghosts reset to spawn on reload) as the other templates' resume behavior. The one existing maze game on production validated cleanly against the new schema unchanged (lives defaults to 3, its dots were already reachable) — no data migration needed this time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QcXH24ky6zjk2UyK5oZUPH
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.