Chat event: Random Unique

Ouverte
#3,537 0 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é
4/5
Temps estimé
3-5 jours
Accessibilité débutants
22/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
go, typescript

Piste de recherche

Read AGENTS.md first for the non-native rule, then the EventBot host and schedule feed that #3533 and #3520 define; both are prerequisites and must land before this can start. Put the server logic behind SRO_EVENT_BOT with round data in the schedule file, and the client entry behind an Experimental row. Done means frozen-clock tests for entry, round end, winner and no winner pass with the flag both on and off, and rewards go through the audited grant path.

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

Description

area: server enhancement priority: medium

Seen on a downstream fork's event calendar (owner's screenshots, 2026-11-15).

What it does

A random unique spawns at a random place for a window; the killer (or top damage) gets the event reward. Reference: 30 min.

Depends on

  • #3533 (EventBot host) and #3520 (schedule feed); listed in the calendar window #3532.

Done when

  • The event's rules on the EventBot host, its round data in the schedule file.
  • Rewards through the audited grant path; the owner sets them.
  • Tests with a frozen clock (entry, round end, winner, no winner).

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_EVENT_BOT (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.