Roadmap FEATURE-16 · Next up · Feature
Visible event beacons
Lower priority per owner: defer dedicated in-world event beacons while refining the hunt/discovery, typed-cargo and specialist-buyer loop. Keep the event-clarity feedback: players need to understand Rift opportunities, but glowing pillars/jets are not a prerequisite for artifact hunting and should not reveal every find. Reassess alongside FEATURE-8 after core discovery design. Preserve cockpit and instrument readability.
1 blitzer supported · Updated
Activity
Visible event beacons: Under consideration to Next up.
Deferred from current slice: Deferring until we improve events...
Visible event beacons: Next up to Under consideration. [MCP] Owner requested lower priority for FEATURE-16/17 in favor of assessing discovery/artifact/specialist-trader direction. Moved out of Next into Under consideration. Numeric priority and current slice membership are unchanged: current MCP exposes neither priority editing nor slice mutation.
Visible event beacons: Next up to Next up. [MCP] Owner-approved weekend feedback refinement. New playtester evidence supports prioritizing event clarity: the Rift's purpose was unclear. Beacons must work with arrival cues, instrumentation and a concise explanation of opportunity/duration, not simply glow. Coordinate FEATURE-8; validate discovery and approach in cockpit/chase without obscuring flight instruments.
Visible event beacons: Next up to Next up. [MCP] Owner-requested backlog prioritization from playtester discussions. Next-up navigation slice, conditional on TASK-4 showing objective-finding friction. Readable beacons support playtesting before additional spectacle; do not obscure instruments.