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

Abierto
#3,531 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
97
Forks
61
Merge medio
4 h 14 min
PR fusionados (30 d)
913

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de opensro-dev/opensro

Todos los issues de opensro-dev/opensro

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.