HOME THEMES · drawn by the game, not pictures
You didn't like the season look on Home, and you want control over it. Here every month's theme is redrawn from a tiny recipe (colours + a sky + 1-3 flat silhouette rows + one light + at most one light weather). This page draws them live from those recipes, the same way the game would. Your fighter and the buttons stay the hero: the world sits low and quiet behind them. Pick a level (OFF, B, A or today's CURRENT), then keep or drop each month. Tap any screen to see it big.
Try them on Home
Pick a month and a level. The box beside it is the whole theme: what the server would send.
Pick how much theme Home gets
Same month (SILENT NIGHT) at four levels. This sets the level for every month; you can still drop single months below.
All 12 months: A minimal · B palette + light
A = sky, 1-3 silhouette rows, one light, light weather. B = even simpler: just the month's colours and its light, no shapes. Keep A or B per month, or DROP a month (Home stays plain that month). REC marks the version I'd ship for that month.
The range: minimal + one custom art piece
Defaults stay minimal. When a month deserves a moment, the theme adds one custom art piece (an art.custom block: a vector piece made once in the engine, checked, then reusable by maps and Home). Still flat, still behind your fighter.
"Should we create art dynamically through the backend?"
Short answer: yes to the backend controlling it, no to the backend painting pictures.
What we're doing (your call: reuse the map engine)
The server sends a recipe, the game draws it. A Home theme is a small content-engine document (about 1 KB), built from the same look blocks the map engine already has: palette.set (four colours), a sky, 1-3 silhouette layers from a built-in kit (city, mountains, dunes, palms, pagoda roofs, pines, waves, lanterns, fence, ruins...), one light, map.weather, and optional shape.lib / art.custom pieces. The game draws it once into the Home background in a few milliseconds. Same tools, same checks, same agents as maps.
RECIPE FROM THE SERVER
- New or changed theme = no app update, live in minutes
- A few KB, not 200 KB pictures per month
- Always the same calm, clean style: shapes come from our kit
- Cheap on a Samsung A22: flat fills, drawn once, not every frame
- You can edit colours and shapes in the dashboard and see it straight away
AI PICTURES MADE AT RUNTIME
- Quality changes from picture to picture; some come out wrong
- Costs money per picture and needs a server queue
- Big downloads on phone data
- Store review risk: content we never checked shows in the app
- Hard to keep the fighter + buttons readable on top
AI still helps behind the scenes: an agent can write a new recipe ("Ramadan nights: crescent moon, lanterns, domes") and you approve it in the dashboard preview. The game only ever draws checked recipes.
What you get in the dashboard
Edit · THE HUNT
Layers (1-3)
Light / weather
Preview on Home
OFF: Home is the plain Spotlight room all year. PICK PER MONTH: you choose the theme for each month (or none). AUTO CALENDAR: each month wears its own theme automatically. Editing changes the next Home a player opens; no update, and the phone keeps the last recipe so it works offline.
For ENG-HOME: the document shape (map-engine terms)
A home document like a map document: { doc, id, rev, engine, name, blocks[] }, each block { b, id, p }, lengths as unit strings in Home-stage metres (the stage is 16 m x 7.375 m, y up from the floor line, podium centre x 7 m). tone 0 = sky bottom colour, 1 = @bg. Colours are #hex or @slot.