Step
3e: the war room (Dillon’s design, 2026-11-12). Part 1 built 2026-11-13
(96c3589); part 2 built 2026-11-13; part 3 built 2026-11-15; part 4
built 2026-11-15. Part 4 (the corridor) replaced by Step 3f,
DESIGN-3f-base.md
Dillon’s
words (MaxTerm chat, 2026-11-12 ~19:5x CST), verbatim
“i want like in xcom a room that looks at the world map. Which will
be represented as a map on the table with moving pieces like on old war
table. So in a almost 3rd person sort of view it will be as if you are
entering the room to look at a map on a table of a command room to a
bunker, with staff and other doing thing in the background. Once in view
of the map it will be an old pre war map of missouri with various toy
like pieces representing, Where points of interest are. Then keep that
third person perspective when going to facility to facility. I want
there to be time taken to go from point to point which will be visually
represented by the piece prepresenting the squad moves to the targeted
area.”
Our own art and names; nothing taken from XCOM.
Approach:
2.5D in the engine we have (tkinter), unless Dillon chooses a 3D
engine
- A small camera module (
p02/scene.py): world points (x,
y, z) → screen through a pinhole projection (camera position, yaw,
pitch, focal length). Everything is flat shapes projected: floor, walls,
table, staff, pieces. Draw far to near (painter’s order by depth).
- The Missouri map is VECTOR (missouri.json: county outlines, rivers,
fort), so it can be projected onto the tabletop plane exactly; no image
warping needed. Old pre-war paper look: sepia land, faded ink edges, a
printed grid, a stain or two, a title cartouche (“MISSOURI”, our own
text).
- Pure logic stays in campaign.py. The scene only reads Campaign
state.
Parts
(each its own commit, tests, mutation check, GUI smoke, deploy, tell
Dillon)
- THE ROOM. The Fort tab’s flat map becomes the command room: walls, a
lamp, the table with the projected map. Entering: the camera glides from
the doorway to over the table (~1.5 s, eased). Staff in the background:
simple figures (radio operator at a desk, clerk walking between
cabinets, an officer by the board), animated with
after()
loops.
- THE PIECES. Toy-like tokens drawn as projected solids: the fort (a
block bunker), missions (pins with numbered flags), regions’ holders
(wooden blocks in the group’s colour, ally/hostile marked), the unit
(two toy soldiers on a base). Click a piece → its briefing (hit-test on
the projected outline). Keep the map’s colours for lean/owner.
- TIME ON THE TABLE. When the unit sets out, the days pass one at a
time and its piece slides from the fort to the target (fraction = days
gone / days on the road), with the day counter ticking; arrival → the
camera leans into the table, then the battle. Home: the piece slides
back. (Logic needs launch() split into steps, or a per-day callback;
wait() already goes day by day.)
- FACILITY TO FACILITY. Third person through the bunker: a corridor
with doors (one per built facility, rubble where a plot is unbuilt);
choosing one glides the camera down the corridor and in. Each room has
its own scene and staff, and holds the controls that exist today
(armory, convoy, building, roster).
Open questions put to Dillon
- 2.5D in the current engine (recommended: keeps everything working,
on his PC now), or move the game to a real 3D engine (much bigger:
models, lighting, a rewrite of the windows)?
- Facility to facility: a short camera walk, no game days; only the
map journey costs days. CONFIRMED by Dillon 2026-11-12: “assumption is
correct”. Engine choice still unanswered.
DECIDED by
Dillon, 2026-11-13 00:0x CST: “3D engine”
Engine: Panda3D (Max’s call, told to Dillon, who can
overrule). Why: - It’s Python, so p02/data.py, tactics.py and
campaign.py, the 106 tests, and his saves all carry over untouched. Only
the windows (view.py, campaignview.py) get rebuilt in 3D. - It’s free
and open source (BSD licence), and installs with pip on Windows. - Godot
was the alternative: a stronger editor, but every rule would be
rewritten in GDScript and the tests lost. Models: built in code from
simple solids first (boxes, cylinders, our own shapes), so nothing is
copied. Any outside asset pack has to be CC0, downloaded, hashed and
checked BEFORE use, and named in the README. Testing: Panda3D can render
offscreen. Try xvfb + software GL on WSL for screenshots. If that fails,
use offscreen buffers on his PC via a scheduled task (NEVER a window
over ssh; feedback_no-gui-smoke-tests-over-ssh). FIRST STEPS for the
next session: 1. pip install panda3d in a venv on WSL; render one
offscreen frame, take a screenshot. 2. On Dillon’s PC:
py -m pip install panda3d (he chose this, but tell him
before it installs). Keep it for the game: ideally a venv under C:. 3.
Part 1 the room, then the pieces, then time on the table, then facility
to facility. The tkinter windows stay working until the 3D one does what
they do.