Job honor: daily honor points, tiers and the Job Honor Rank window
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- go, typescript
Línea de trabajo
This is design work, not a starter task: the owner still has to decide what earns points, what each tier grants and whether the Job Temple part exists. Read AGENTS.md for the non-native rule and the SRO_JOB_HONOR flag, and find the existing job ranking handled by native opcode 0x737E. Done means the server ledger with daily cap and tier change is tested, and the window is built from existing CIF parts behind the flag.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Seen in the owner's screenshots of a downstream fork's client (2026-11-15). We have nothing like it: the native job ranking (0x737E, activity/contribution) is the only job board.
What it does
- Honor points earned by job activity (trader and thief), counted today and this month, split per job, with a daily cap (the reference shows 1000 / 1000 left).
- Tiers (None, Silver, Gold, King) recomputed at a fixed time each day ("Tiers change 05:00"). Each row shows the current tier and the tier the player will hold after tonight's change ("tonight: Gold").
- Ranking window with tabs All / Trader / Thief and Current / Previous (the previous period), columns #, Name, Job, Points, Tier; "You are not in this ranking." when the viewer has no row.
- My honor panel: today, this month (trader / thief), daily cap left, place, tier, time until the tier change, and Job Temple time left today (a tier grants hours in a job temple area).
- The board refreshes on a schedule ("Updated 02:08, next 02:38").
Open design calls for the owner
- What earns points (trade runs by value/stars, thief steals, hunter kills?) and the cap.
- What each tier grants (the reference ties tiers to Job Temple hours).
- Where the Job Temple is, or whether that part is dropped.
Done when
- Server: points ledger (per character, day, month, job), daily cap, tier job at the daily time, previous-period snapshot; persisted; abuse-safe (points only from server-verified job events).
- Wire + client: the ranking window and My honor panel in native style.
- Tests for the cap, the tier change and the previous period.
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_JOB_HONOR (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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de opensro-dev/opensro
-
area: client enhancement priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#3681 ·
Los mantenedores suelen responder en 1 día
-
area: client bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
opensro-dev/opensro#3228 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Format one minified client file with dprint (ongoing: one file per PR)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea: client enhancement good first issue priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#1 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: server bug priority: medium
Dificultad 3/5 Medio día Aptitud para principiantes 55/100
opensro-dev/opensro#3687 ·
Los mantenedores suelen responder en 1 día
-
area: ops bug priority: high
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
opensro-dev/opensro#3685 ·
Los mantenedores suelen responder en 1 día
Todos los issues de opensro-dev/opensro
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
unbound-force/gaze#353 ·
Los mantenedores suelen responder en 1 día
-
bug cross-seed ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
OneBusAway/maglev#2102 ·
Los mantenedores suelen responder en 2 días
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Los mantenedores suelen responder en 1 día