The target-agnostic NES tooling: rendering, and Mesen (emulator) integration. KOEI-specific tooling — the VM decompiler, the walk pipelines,
games.toml— is not here; it lives in koei/.
Links: system → NES · KOEI toolchain → koei/ · hardware → PPU · mappers
nes-render (archived 2026-10-26)| Field | Value |
|---|---|
| Logical name | nes-render (private, ARCHIVED 2026-10-26) · github.com/chrisaacson69/nes-render |
| Sibling path | none: local clone removed 2026-10-26 |
| Contents | now emu-harness emu_harness/machines/nes/ppu.py (+ canvas.py, ppuport.py); the archived repo’s nes_render.py is an alias of it |
| Role | generic PPU / rendering core; target-agnostic |
| Depended on by | nothing: the last importer, Mappy render_level.py, moved onto the library 2026-10-26 |
Graduated out of NA1 when Mappy needed it — the moment a second app wanted it, it became a real
dependency with exactly one home. (The na1_font_atlas.png still riding along is a leftover of that
extraction; it is NA1-specific data in a generic package.) Then folded into emu-harness (its row O,
2026-10-23) when the console-RE toolset consolidated, and archived once nothing imported it (2026-10-26).
Mesen label/workspace generation is how a decompiled symbol table gets back into a debugger. It is currently scattered across three homes:
| Tool | Lives in | Scope |
|---|---|---|
mesen-labels.py, mesen-workspace.py |
game-annotation/tools/ |
the comparisons monorepo |
| label emission | koei-nes/tools/ |
KOEI NES |
gen_mlb |
koei-snes |
KOEI SNES |
⚠️ Duplication flagged, not fixed. Three implementations of “emit emulator labels from the symbol
table” is exactly the drift-by-re-derivation the SDK warns about — but consolidating them requires the
repos cloned and a judgment call about which is canonical. Recorded here so the next person finds all
three instead of writing a fourth. See [feedback: drift is re-derivation] in the memory area index
area_re_method.
Also in the comparisons monorepo’s tools/: asm-relabel.py and vm-disasm.py — the latter predating
the NA1 extraction, so verify against na1-decompiler before reusing it.
⚠️ Nothing here is cloned on this machine (2026-07-21).