Chat event: Hide & Seek

Open
#3,536 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go, typescript
Domain
backend, game-dev

Research direction

Start with AGENTS.md for the non-native rule, then check whether the EventBot host (#3533) and schedule feed (#3520) exist, since this depends on both. The server side goes behind SRO_EVENT_BOT, with round data in the schedule file and rewards through the audited grant path. Done means frozen-clock tests for entry, round end, winner and no-winner, passing with the flag both on and off, and a client entry behind an Experimental row.

Written by the indexing model from the issue text.

Description

area: server enhancement priority: medium

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

What it does

A GM-like NPC or EventBot hides somewhere in the world and posts hints; the first player to find and target it wins. Reference: 5 rounds, 10 min each.

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.

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.