Proposal: interactive map elements (Lotus/Summit doors) à la valoplant#109

open1

main

research/valoplant-interactive-doors

openedAug 4, 2026byDDara Adedeji

View on GitHubTwo-way sync enabledPR last imported 3d ago

5 unresolved threads · Jump to file

Selected thread: docs/proposals/interactive-map-elements.md:142 — _🎯 Functional Correctness_ | _🟠 Major_ | _🏗️ Heavy lift_ **Model Summit as a one-way transition.** `toggle(String id)` permits `up → dropped → up`, but Line 26 says a dropped Summit wall permanently blocks the route for the rest of the round. Lines 169-174 repeat this contradiction. Current Summit references also describe dropped walls as non-reopenable during the round. ([forbes.com](https://www.forbes.com/sites/mikestubbs/2026/06/21/new-valorant-map-summit-features-dropping-walls-that-block-routes/?utm_source=openai)) Define legal transitions per `MapInteractableKind`: Lotus `closed ↔ open`; Summit `up → dropped`. Let undo restore the previous page snapshot, but do not make a second click reopen the wall. Also applies to: 163-174 <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/proposals/interactive-map-elements.md` around lines 119 - 142, Update the interactable state transition logic in InteractableStateProvider.toggle to branch on MapInteractableKind: preserve bidirectional closed/open toggling for Lotus, but allow Summit only to transition from up to dropped and ignore subsequent clicks. Keep undo behavior based on restoring the prior page snapshot rather than permitting a second toggle to reopen Summit walls, and update the related Summit descriptions to reflect the one-way transition. ``` </details>    _Source: MCP tools_

0 / 1 viewed1 file changedLine totals unavailable