# Hole that swallows a low-poly city

> Void City, a hole.io-style game: steer a hole through a low-poly town, swallow benches, cars, and eventually whole houses, and grow before the timer runs out. Codex with GPT-5.6 Sol built it from a three-sentence prompt kept simple on purpose.

- Kind: Game
- Page: https://meetreference.com/v/hole-that-swallows-low-poly-city/
- Ready-to-use agent handoff: https://meetreference.com/v/hole-that-swallows-low-poly-city/agent.txt
- Exact prompt as plain text: https://meetreference.com/v/hole-that-swallows-low-poly-city/prompt.txt
- Authorship: Not stated
- Made with: Codex
- Model: GPT-5.6 Sol
- Built with: Three.js
- Style: Games; low poly, three.js, arcade, city, casual, hole.io
- Shared by @givros in X, Jul 18, 2026: https://x.com/givros/status/2078391824343880158
- Prompt fidelity: Verbatim. This is the complete prompt exactly as the creator published it.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this game

These are the creator's published instructions, unedited.

To adapt it: Replace "a moving hole that swallows houses and other city objects" with your own core mechanic, and keep the list after "Include" ("smooth controls, collision detection, a follow camera, low-poly visuals, and a responsive interface").

## Prompt

```text
Create a polished 3D browser game with Three.js where the player controls a moving hole that swallows houses and other city objects, grows as it consumes them, and earns points. Include smooth controls, collision detection, a follow camera, low-poly visuals, and a responsive interface. Organize the project into separate HTML, CSS, and JavaScript files.
```

## What it looks like

Written by Reference from the video frames, not by the creator.

A low-poly town seen from above, where a dark hole with a lilac rim slides along the streets swallowing benches, cars, hydrants, and houses as it grows.

- Color: Charcoal roads with white crosswalks, beige pavements, green lawns, and toy-bright houses and cars in red, teal, yellow, and orange; the hole is dark violet with a lilac ring.
- Type: A VOID CITY logo in the top left, a timer at top center, score panels in the top right, small floating labels as objects fall in (+80 PARK BENCH, +267 COMPACT CAR), and an end card reading VOID OWNS THE BLOCKS.
- Framing: 16:9 from a high three-quarter camera that follows the hole across a grid of blocks.
- Structure: The hole starts small on a residential block, grows to take cars and a hydrant, reaches the next size with a white flash, swallows houses near taller apartment blocks as the timer runs down, and ends on the results card over a blurred city.

Storyboard, nine frames spread across the video: https://meetreference.com/media/hole-that-swallows-low-poly-city/storyboard.webp

- Frame 1 at 2.8s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f1.webp
- Frame 2 at 8.4s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f2.webp
- Frame 3 at 14.0s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f3.webp
- Frame 4 at 19.7s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f4.webp
- Frame 5 at 25.3s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f5.webp
- Frame 6 at 30.9s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f6.webp
- Frame 7 at 36.5s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f7.webp
- Frame 8 at 42.1s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f8.webp
- Frame 9 at 47.7s: https://meetreference.com/media/hole-that-swallows-low-poly-city/f9.webp

## How it was made, per the creator

- One-shot: yes, a single prompt with no follow-ups
- Notes: The creator says one prompt turned into the game, and calls it a prototype in a reply. No live build or code was shared.

> The prompt was intentionally simple. The result was not.
> (@givros)

## Links

- Watch: https://x.com/givros/status/2078391824343880158
- Original post: https://x.com/givros/status/2078391824343880158