Unique Status window: which uniques are alive, when they died, who killed them, spawn alerts

Offen
#3,531 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go, typescript

Rechercherichtung

Start with AGENTS.md for the non-native rule, then find the public API's uniques source and the unique announcement packet 0x3058 to see what alive/dead and killer data already exists. The server feed goes behind SRO_UNIQUE_STATUS, and the client window must be built from the native CIF frame and parts. Done when the feed's alive, dead and killer states and the notify filter have tests, and both flag settings are verified.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area: client area: server enhancement priority: high

Seen in the owner's screenshots of a downstream fork's client (2026-11-15). We have the data (the public API's uniques source, unique announcements 0x3058, the M-map unique spawn points) but no in-game status window.

What it does

  • A window listing every unique with its level: Status (Alive / Dead), Died (server time and "50 min ago"), Killed by.
  • Tabs: All / Alive / Dead / Notify list.
  • A checkbox per unique builds the player's notify list: "Notify when it spawns", optional "Also when it dies". Notifications also reach the browser (asked on Save) while the game tab is open, even in the background.
  • Footer: times are server time.

Done when

  • Server: a state feed for the client (alive/dead, death time, killer) from the same source as the public API, sent on open and on change.
  • Client: the window in native style; the notify list saved per character; in-game notice on spawn/death for listed uniques; browser notification only after the player opts in.
  • Tests: the feed's states, the notify filter.

Look: SRO native, not the screenshot

The owner's rule (2026-11-15): the screenshots show what the feature does; its look must be SRO native. Build any window from the client's own parts: the CIF window frame and title bar, native buttons, tabs, list rows, scroll bar and the native font (the way our existing windows are built), not the flat web-style dark panels in the reference.

Flag

Port-only, not native: server side behind SRO_UNIQUE_STATUS (off is native), the client entry behind an Experimental row; test both settings (AGENTS.md non-native rule). The owner turns it on.

Vorherrschende Sprache
Go
Sterne
97
Forks
61
Ø Merge
4 Std. 14 Min.
Gemergte PRs (30 T.)
913

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus opensro-dev/opensro

Alle Issues in opensro-dev/opensro

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.