36 lines
1.5 KiB
Markdown
36 lines
1.5 KiB
Markdown
|
# Step 0 / Step 1 implementation
|
||
|
|
|
||
|
|
## Step 0 — Seam diagnostics
|
||
|
|
|
||
|
|
Patch preview/application now records and displays:
|
||
|
|
|
||
|
|
- inspected seam-band cell count
|
||
|
|
- land→sea and sea→land flips
|
||
|
|
- existing transport cells converted to sea
|
||
|
|
- pre-existing road/rail seam portals and post-patch connection status
|
||
|
|
- new municipal/prefecture boundary edges created in the seam band
|
||
|
|
- near-parallel/overlapping boundary pairs
|
||
|
|
- abrupt elevation edges
|
||
|
|
- map markers and the seam outline
|
||
|
|
|
||
|
|
The overlay is enabled by default and can be toggled with **Layer → Seam diagnostics**.
|
||
|
|
Detailed metrics are shown under **Advanced / Debug Data → Seam Diagnostics** and included in **Copy Important Data**.
|
||
|
|
|
||
|
|
Marker colors:
|
||
|
|
|
||
|
|
- magenta dashed line: patch seam
|
||
|
|
- red: disconnected/critical issue
|
||
|
|
- orange: topology or boundary warning
|
||
|
|
- green: retained road/rail crossing
|
||
|
|
|
||
|
|
## Step 1 — Variable rectangle candidate suspended
|
||
|
|
|
||
|
|
`PATCH_VARIABLE_CANDIDATE_ENABLED` is set to `false` in `mapPatch.js`.
|
||
|
|
Patch generation therefore uses `legacy-full-pipeline`, while the variable-size implementation remains in the source for later re-enablement.
|
||
|
|
The UI and diagnostic output explicitly report `variableCandidateSuspended: true` during this comparison phase.
|
||
|
|
|
||
|
|
## Validation performed
|
||
|
|
|
||
|
|
- Syntax check passed for every JavaScript file.
|
||
|
|
- Two end-to-end Node runs completed: initial map generation, world creation, full-pipeline patch generation, seam analysis, and viewport diagnostic transformation.
|
||
|
|
- Both runs reported `patchGenerationMode: legacy-full-pipeline` and `variableCandidateSuspended: true`.
|