Chat event: Hide & Seek

Aberta
#3,536 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
22/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go, typescript
Domínio
backend, game-dev

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
97
Forks
61
Merge médio
4h 14min
PRs com merge (30d)
913

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de opensro-dev/opensro

Todas as issues de opensro-dev/opensro

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.