Frontier Gulch 1882 — western: a 12-hour compressed day where 500+ named citizens run their daily routines, the R21 wedding plays as a background event, and the multiverse-portal cat walks through at hour 5
A 3D BRIMSWORTH WORLDS demo: City 6 of 12. a frontier town where 500+ named townsfolk gather on dusty boardwalks and saloon porches. 12-hour compressed day-cycle (600s real-time = 12 in-world hours), 6 city zones (residential/commercial/civic/industrial/leisure/transport), 30+ director cameras, 500+ named citizens with daily routines (commute → work → meal → home → sleep). At hour 14:00 in-world the R21 Bramble × Field wedding plays as background news. At t=300s a dusty-gold-and-amber portal opens and Bytes-from-prior-universe walks INTO THE CITY (not the wedding). Same C-E-G-C wedding leitmotif now voiced as harmonica-and-fiddle frontier waltz. ALL FICTIONAL.
What this is
A 3D recreation of City 6 of 12 of the BRIMSWORTH WORLDS arc — a frontier town where 500+ named townsfolk gather on dusty boardwalks and saloon porches. The R21 wedding cast is no longer the centre; the city is. 500+ named citizens cycle through 6 zones (residential, commercial, civic, industrial, leisure, transport) on individual daily routines while the camera director system rotates 30+ cameras through different lives across a 12-hour compressed day.
A 12-hour compressed day-cycle compresses 600s of real-time into 12 in-world hours (50s = 1 hour). The sun arcs from dawn through golden noon, dusk-pink, and night-deep blue; sky-color and ambient-light gradients track the arc. Three weather windows roll across the day (morning mist → afternoon clear → evening light-rain). 500+ named citizens each have a daily routine: commute → work → meal → home → sleep, scheduled across 6 city zones (residential, commercial, civic, industrial, leisure, transport hub). 30+ director cameras follow different citizens through their day.
The R21 wedding becomes a background event in the city's daily calendar — at hour 14:00 in-world, a small chyron note marks "Bramble × Field wedding nearby" while citizens go about their day. The multiverse-portal cat-meet event still triggers at t=300s — but here, Bytes-from-prior-universe walks into the CITY, not the wedding. A city-events HUD calendar lists scheduled happenings (market, parade, concert, ceremony, evening-lantern-walk) for the day.
The world remembers + broadcasts. localStorage appends to the canonical brimsworth_worlds_v1 ledger — { city_id, citizen_count, sunrise_t, sunset_t, events_logged } — and cross-reads brimsworth_multiverse_v1 + brimsworth_century_v1 + brimsworth_lifetime_v1 + recurring_cast_v1. BroadcastChannel('brimsworth_worlds') emits each major city event as { type:"city-event", city, event } and renders a faint twin-city ticker for any other open tab.
You don't play it. You watch a Frontier Gulch 1882 live an entire day in 10 minutes — 500 named citizens commuting through 6 zones, a 12-hour sun arc, and a wedding playing as background news. warm-western, cozy-frontier.
Why this is mind-blowing
A Frontier Gulch 1882 that runs as a city: 500 named citizens with named daily routines, a 12-hour day-cycle compressed to 600s, 6 city zones, a city-events HUD calendar, a R21 wedding that has become background news in this world's daily life, the multiverse-portal cat-meet pulled into a CITY scene, and brimsworth_worlds_v1 + BroadcastChannel sync that lets twin tabs render each other's events as ticker. R25 is the round where the wedding becomes background and the world becomes the protagonist. ALL FICTIONAL.
Prompt
Build a single-file HTML page that recreates "Frontier Gulch 1882 living city" as a continuous 3D autoplay world.
CONCEPT: BRIMSWORTH WORLDS — a frontier town where 500+ named townsfolk gather on dusty boardwalks and saloon porches.
Hard constraints:
- One HTML file, < 200KB. three.js r0.160 IIFE strict
- First body line: <!-- ROUND25_WORLDS v1 -->
- localStorage appends `brimsworth_worlds_v1` { city_id:'frontier-gulch-1882', citizen_count, sunrise_t, sunset_t, events_logged }.
- Cross-read brimsworth_multiverse_v1 + brimsworth_century_v1 + brimsworth_lifetime_v1 + recurring_cast_v1.
- Reseed every ~10 min.
All R16-R24 retained. R25 NEW:
1. 12-HOUR COMPRESSED DAY-CYCLE (600s = 12 hours, 50s = 1 hour, sun arc, sky gradient, 3 weather windows)
2. 500+ NAMED CITIZENS with daily routines (commute → work → meal → home → sleep)
3. 6 CITY ZONES (residential/commercial/civic/industrial/leisure/transport hub)
4. R21/R24 WEDDING AS BACKGROUND EVENT at hour 14:00 — chyron note only, citizens continue routines
5. CITY-EVENTS HUD CALENDAR — scheduled happenings shown as HUD list
6. MULTIVERSE-PORTAL CAT MEET at t=300s — Bytes walks into THE CITY (not the wedding)
7. brimsworth_worlds_v1 ledger append + cross-read all canon
8. BroadcastChannel('brimsworth_worlds') emit city-event + listen + render twin-city ticker
9. 30+ cameras following different citizens
Tone: warm-western, cozy-frontier, ALL FICTIONAL.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- How to compress a 12-hour day-cycle into 600s real-time with sun-arc + sky-gradient + 3 weather windows + 50s-per-in-world-hour scheduling
- How to schedule 500+ named citizens through commute → work → meal → home → sleep routines across 6 named city zones with 30+ director cameras following individual lives
- How to demote the R21/R24 wedding to a background HUD-calendar event and let the *city* become the protagonist while still appending the canonical brimsworth_worlds_v1 ledger and BroadcastChannel city-event sync across tabs