---
title: In-game minimap UI
trigger_condition: After map-editor milestone delivers authored maps and at least 2 zones exist in LDtk
planted_date: 2026-05-18
status: seed
---

# In-game minimap UI

## Idea

In-game minimap surface showing:

- Current zone's local map (player position, visited area, points of interest)
- Inter-zone adjacency / theoretical relative placement of zones on an overworld

## Why now (seed, not phase)

Composing piece of the next milestone alongside map editor + publish workflow. Captured here so it isn't lost during editor-tooling work — but should be planned once authored maps exist to design against.

## Trigger

- Map-editor milestone has produced LDtk projects for ≥ 2 zones, AND
- Decision on multi-world overworld composition has been made (see [research/questions.md → zone adjacency](../research/questions.md))

## Approach hooks

- **LDtk multi-worlds + GridVania/Free layout** is the natural authoring surface for zone adjacency. Minimap can read the same `.ldtk` project's world layout directly.
- **Per-level/per-room minimap** is independent: render IntGrid + entity-of-interest positions to a downscaled canvas.
- **Player position** comes from existing protocol state (already authoritative).
- **Visited area** is per-player state; persistence model = TBD (could ride on SQLite + Litestream alongside character data).

## Out of scope for this seed

- Fast-travel UI (separate seed if/when surfaced)
- Map-editor support for minimap-specific overlays (defer until in-game side proves it needs them)

## See also

- [notes/map-editor-decision.md](../notes/map-editor-decision.md)