Build your own Crossy Road.

# Build an original game inspired by Crossy Road

You are an experienced game designer and gameplay engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Desktop. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original desktop lane-crossing arcade game called Meadow Hop, inspired by the forward-hopping loop of Crossy Road. Use Godot and original simple low-poly assets. The player crosses a bounded sequence of grassy lanes, roads, and rivers, earning distance for forward progress. Deliver one polished playable loop rather than a copy of characters, worlds, or monetization.

## Design
Use an original isometric meadow with a readable grid, distinct vehicle and floating-platform silhouettes, and a camera that tracks progress smoothly. Show score, restart, pause, and controls. Support arrow/WASD input and clickable directional buttons; keep simulation coordinates independent of camera perspective.

## Features
1. Hopping: move one grid cell per accepted input with a defined hop duration. Queue at most one next hop, prevent overlapping actions, and calculate logical position independently from visual tweening.

2. Road hazards: spawn a bounded number of original vehicles per lane with seeded speeds and gaps. Evaluate collisions along the hop trajectory so fast hazards cannot tunnel through the player.

3. Rivers: let the player ride moving platforms, carry them with platform velocity, and lose when unsupported or carried outside bounds. Resolve support and water collision in a documented simulation order.

4. Lane progression: generate a finite rolling window of lanes from a seed, keep a buffer behind the player, and score only new furthest-forward rows. Use constrained patterns and a simple route validator for the supplied lane types.

5. Session and saves: pause/resume, confirm restart, and restore a paused run including generated lanes, entity positions, seed, and score. Save atomically to a versioned local file with a backup and explicit error feedback.

## Tech stack
Use Godot with GDScript for a native desktop build and original generated meshes or permitted assets. Keep lane generation, collision rules, and scoring in a deterministic fixed-step model separate from scene presentation. Use bounded object pools and explicit active-lane/entity limits. Save plain validated data through a temporary-file/replace strategy; never load executable resources from a user save.

## Data & behavior
Run {seed, rngState, tick, playerCell, playerOffset, supportPlatformId, furthestRow, score, status}; Lane {index, type, hazardPattern}; Vehicle; Platform; Settings; SaveVersion. Persist the actual active entities and generation cursor, not only the seed.

Acceptance checks and scope:
Test a vehicle crossing during a hop, drifting platform support, hopping off a platform, backtracking without extra score, generation determinism, and save/resume with moving hazards. Include several verified navigable example seeds. Exclude copied characters/maps, online play, cosmetic stores, unlimited procedural promises, and mobile packaging in this default desktop brief.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.