Chat event: Random Unique

Offen
#3,537 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go, typescript

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Go
Sterne
97
Forks
61
Ø Merge
4 Std. 14 Min.
Gemergte PRs (30 T.)
913

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus opensro-dev/opensro

Alle Issues in opensro-dev/opensro

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.