CRAMSHIFT

CRAMSHIFT

About

Released 2026-10-12Category New
CRAMSHIFT Move the rooms. Bring everyone home. Create a complete polished browser puzzle game through iDos AI Coder. It is a living dollhouse: the player slides rows and columns of dormitory rooms while autonomous students walk inside. This replaces the previous QONAQ idea entirely. STORY: The night before final presentations, The Registrar, a comically literal campus allocation machine, discovers Block Zero, a dorm missing from its map, and begins packing it away. You are the student Shiftkeeper. You can move architecture on hidden rails, but cannot control residents. Reunite them with their rooms, recover the group project and reclaim the building. Later, player-authored floors form the Afterhours Campus. Show story through small notices, furnished rooms and short resident lines; first action before exposition. CORE RULES: Start with a 4x4 board. A room has N/E/S/W corridor connections (4-bit masks). Slide a row left/right or a column up/down by one cell, with wraparound on a visible loop rail. Residents ride with the shifted room. Their destination doors are anchored to board coordinates and do not move. After each shift, the bell advances one beat; each unsaved resident walks one cell along the shortest connected path to their destination; tie order is North, East, South, West. If no path exists they wait. Entering their goal saves them. Show predicted moves before committing. Planning is untimed; characters animate between beats. A win means everyone home within the beat budget. Support Undo, Reset, Wait and replay; undo truncates replay. Score is beats, never wall-clock timing. Preserve a pure deterministic engine, versioned floor schema and compact actions for later on-chain replay verification. Validate imported floors and bound replay length. CAMPAIGN: Ship at least five genuinely solvable authored puzzles, each with a tested winning replay. Level 1 teaches a row shift and carry with one resident. Level 2 has three students and a satisfying single shift that reconnects several routes. Then introduce marked quiet-hour hazard beats, a project-desk waypoint before home, and the final reclaiming of Block Zero. Keep mechanics small if necessary: core correctness and readable puzzle design before extras. Never ship a puzzle without validating its solution. VISUAL: A large beautiful dorm model is the main screen, not a dashboard. Deep blue night, paper-white walls, coral furniture, lilac shadows, bright blue loop rails and warm lamps. Tiny expressive students have matching colour+shape+door symbols. Give each tile recognisable room furniture: kitchen, bedroom, laundry, study, party. Animate rows physically sliding and students riding. Bold CRAMSHIFT wordmark, compact chapter/people-home/beats HUD, tasteful notices from The Registrar. Clear touch row/column handles and keyboard controls; reduced motion, mute with procedural audio, EN/RU toggle, readable at 360px. Immediate guest play; no wallet needed for campaign. EDITOR: Let players paint corridor connections, set up to three starts and matching goals, choose budget, test and solve their level, export/import a versioned JSON and share it. Local saved floors persist. Community floors and records must be real or clearly empty, never invented. SOLANA TARGET: This is essential to the continuation: solve -> prove -> author -> share -> challenge -> remix. A custom devnet program stores immutable small floor payloads with author, rules version and parent remix address. It replays bounded move sequences and verifies that the residents got home; it computes beat counts instead of trusting client scores. Publishing requires a winning solution witness. One best-result account per floor+solver prevents duplicate first-clear records and worse-score replacement. Another player loads the exact floor from its address and competes/remixes it. Use a separate typed chain adapter so a local agent can build/deploy that program after export. Do not replace this with an unch