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

Aperta
#3,531 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
97
Fork
61
Merge medio
4h 14m
PR unite (30g)
913

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di opensro-dev/opensro

Tutte le issue di opensro-dev/opensro

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.