67 lines
3.8 KiB
Markdown
67 lines
3.8 KiB
Markdown
# Walkthrough: building a living district sheet
|
||
|
||
District sheets sit before establishment rendering. They register a close district bitmap to the whole-city map,
|
||
carry forward established pins, and fill unused label capacity with clearly marked proposals. Those background places
|
||
make the city feel inhabited without spending tier-1 effort on every doorway.
|
||
|
||
## 1. Keep both source scales
|
||
|
||

|
||
|
||
Start with the whole-city map and the untouched district bitmap. Do not re-export either to make them fit. Match
|
||
several distinctive roof patches, estimate one scale-and-translation transform, and inspect the residuals. In the
|
||
worked north sheet, 25 full-resolution patches gave scale 0.30233, translation (568.72, 191.08), and RMS error 0.06
|
||
sheet units.
|
||
|
||

|
||
|
||
Project the existing whole-city pins through that transform. A pin stays attached to its real map building. If it
|
||
falls under the template veil or outside the placeable window, omit it or create another district sheet—never slide it
|
||
to a convenient roof.
|
||
|
||
## 2. Define the district before adding places
|
||
|
||

|
||
|
||
A district boundary may be absent from the art. Trace it from street geometry and mark it **PROPOSED** until the GM
|
||
rules on it. The boundary decides which sheet owns border establishments and constrains where new places may be sited.
|
||
|
||
## 3. Populate the template
|
||
|
||

|
||
|
||
The sheet template supplies 22 label/subtitle slots, a legend, a parchment veil, and a placeable map window. The build
|
||
stage:
|
||
|
||
1. clones icon geometry from the template legend;
|
||
2. projects established pins from the whole-city map;
|
||
3. snaps each new proposal to an actual drawn roof, with water and neighbor clearances;
|
||
4. assigns labels to slots and routes leaders at 0, 45, or 90 degrees;
|
||
5. rejects line crossings, foreign-icon hits, legend crossings, and pins outside the placeable window;
|
||
6. exports a table carrying name, tagline, wealth tier, source status, and render tier.
|
||
|
||
In this example, the north sheet filled all 22 slots: seven established places, one previously unnamed marker, and
|
||
fourteen **PROPOSED** establishments. The proposals were not silently promoted by appearing on the map; the sheet and
|
||
its companion table kept the status explicit.
|
||
|
||
## 4. Spend detail by effort tier
|
||
|
||
Most padded places are city texture, not immediate play locations. Give them wealth tiers so architecture and goods
|
||
can be described consistently, but assign render effort separately:
|
||
|
||
- **T3:** one representative exterior when a place is likely to be noticed soon;
|
||
- **T4:** map pin, name, tagline, and a short fact only; no render until play promotes it;
|
||
- **T1/T2:** reserve for established or high-focus destinations that need multiple angles, interiors, or matrices.
|
||
|
||
This distinction is the economy of the stage: a district can feel full before the campaign pays to visualize every
|
||
shop. If play turns a proposed background pin into a destination, promote its effort tier and begin the normal
|
||
map → model → plate → frame chain.
|
||
|
||
## Template note
|
||
|
||
The source SVGs were inspected before publication. They had no SVG `<text>` nodes—the visible words were converted to
|
||
paths—and the district files linked private bitmap filenames while the whole-city file embedded hundreds of megabytes
|
||
of map data. Because path-outlined wording cannot be audited reliably by a text scan, those campaign-specific SVGs
|
||
are intentionally not redistributed here. Build from a fresh 1600 × 900 SVG with your own title, legend, veil,
|
||
22 label/subtitle groups, and linked district bitmap, then keep all live wording as `<text>` for future audits.
|