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

Open
#3,533 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
backend, game-dev

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
97
Forks
61
Avg merge
4h 14m
Merged PRs (30d)
913

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opensro-dev/opensro

All issues in opensro-dev/opensro

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.