Skip to content

feat(maps): give Rockforge's dwarven teleporter a warm focal glow #99

Description

@zoeyrose

Important

Evidence policy update (2026-08-11): #66 is complete through #124; any wording
below treating it as a future prerequisite is superseded. #126/#127 retire the
committed renderer-review capture surface. The removed files were generated
review artifacts, not authored gameplay art. Any requirement below to commit
rendered screenshots, contact sheets, manifests, proof maps, or capture tooling
is superseded. Keep authored semantic review in
maps/light-source-review.json (rationales, current digests, complete coverage,
and zero unreviewed emitters). Optional smooth/discrete diagnostics belong only
under ignored build/ or deployment output; summarize conclusions in the PR,
but never commit or gate merge on those files.

Follow-up to #65 and its implementation in #67, with the compatible main integration tracked by #66.

Outcome

Give Rockforge City's unique dwarven teleporter one coherent, art-matched focal light by moving illumination ownership from four invisible helpers onto the visible multipart machine.

Keep this map-local. A single authored machine does not justify a global lighting contract for the dwarven_teleporter archetype.

Evidence

The world has one multipart dwarven_teleporter, at (6, 6) in the darkness-3 map maps/shattered_islands/strakewood_island/rockforge/rockforge_a_0301. It has no direct radius or color. Its complete 2-by-2 footprint is covered by four neutral light9 helpers at (6, 6), (7, 6), (6, 7), and (7, 7).

The machinery is visually bright, but its metal, energy aperture, and surrounding Rockforge palette need rendered comparison before a hue is selected. Established warm gold ffe060 is the starting direction; cold or arcane color should be used only if the actual animated frames support it.

This is separate from #86 and the stock-green exit work: it is a multipart map fixture, not a type-66 portal object, and it already has a deliberately large four-helper composition.

Scope

  • Render the teleporter and adjacent Rockforge rooms in smooth and discrete Classic lighting, starting from established warm gold ffe060.
  • Move the intended footprint onto the visible multipart root or another single deliberate owner; do not make each child emit.
  • Reconcile all four neutral light9 helpers atomically so the result does not become a four- or five-source stack.
  • Keep any room-scale neutral fill that serves independent navigation, but document why it remains separate from the machine.
  • Preserve multipart layout, animation, direction, destination/teleport behavior, walls, obstruction, coordinates, and every gameplay field.
  • Keep the shared dwarven_teleporter archetype non-emitting unless future placement evidence supports a separate global decision.

Acceptance criteria

  • The Rockforge machine has one coherent, reviewed focal-light owner and an art-matched established palette color.
  • The four current light9 helpers are removed, retained, or re-scoped with explicit rendered evidence; no accidental stacked source remains.
  • Light follows the visible multipart root without duplicating across child objects or leaking materially through nearby walls.
  • Teleport behavior, destination, animation, direction, multipart structure, obstruction, and every non-light field remain unchanged.
  • The room stays readable in smooth and discrete Classic lighting without becoming uniformly tinted.
  • The chore(maps): audit authored light-source colors #65 inventory, review records, map semantic digest, evidence manifest, and affected rendered evidence are refreshed.
  • python3 tools/world_content_audit.py lights --check, python3 tools/validate.py, and git diff --check pass.

Release lines

Land only after #65/#67 are integrated on 1.x and #66 supplies the matching field/audit contract on main. The affected map is compatible across the release lines. Deliver separate linked pull requests, with Classic 1.x owning rendered runtime evidence and main independently validating the authored mirror.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Fields

Priority

None yet

Start date

None yet

Target date

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions