EventBot: host for automated chat events (whisper to join, rounds, rewards)

Offen
#3,533 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
backend, game-dev

Rechercherichtung

This is an epic: each event is a separate issue that plugs into the host, so start by reading the schedule feed work in #3520 and the AGENTS.md non-native rule, which governs the SRO_EVENT_BOT flag and the Experimental client row. Before writing code, the owner needs to settle the reward values and the anti-abuse rules, and the done list requires a frozen-clock test suite. Pick one slice, such as the scheduler data file, and ask on the issue before building the whisper handling.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area: server enhancement priority: high

Seen in the owner's screenshots of a downstream fork's client (2026-11-15): "Whisper EventBot to take part." Their calendar runs several automated chat events a day. We have none.

What it is

A server-side event host that appears as a chat participant named EventBot: it announces events, takes whispers as entries/answers, runs rounds on timers, and grants rewards through the normal item path (audited). Each event below is its own issue and plugs into this host.

Done when

  • Scheduler driven by a data file (time, event, rounds, round length, reward), published to the schedule feed (#3520).
  • EventBot whisper handling, round timers, winner selection, reward grant with an audit row.
  • Rate limits and anti-abuse (one entry per character per round; botting is allowed on this server, so rewards must not reward scripted speed alone where that breaks the event).
  • Tests with a frozen clock.

The owner sets the rewards (the reference gives Silk Scroll (10); owner: always free, rewards should beat the hourly Silk).

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.