Job honor: daily honor points, tiers and the Job Honor Rank window

Ouverte
#3,530 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
8/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
go, typescript

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area: client area: server enhancement priority: high status: claimed

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.

Langage dominant
Go
Étoiles
97
Forks
61
Merge moyen
4 h 14 min
PR mergées (30 j)
913

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de opensro-dev/opensro

Toutes les issues de opensro-dev/opensro

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.