Failed +9 reinforcement announcements with opt-out

Open
#3,682 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, frontend

Research direction

Start with #3493 to see how the +9 reinforcement announcement was originally wired, then find where store schema versions are defined and bumped to add the schema 45 opt-out field. Trace the server path that emits reinforcement announcements to all players, and the in-game and website settings surfaces where a per-player opt-out toggle would live. Done means all four checklist items hold: schema 45 field, server-side announcement respecting the flag, and both opt-out UIs. This spans server, client and website, so expect several files and project-specific knowledge.

Written by the indexing model from the issue text.

Description

area: server enhancement priority: medium

Follow-up from #3493

Owner decision (2026-11-14): failed +9 reinforcement announcements for every player, with an opt-out in game and on the website. Needs an additive store field (schema 45).

Done when

  • Store schema 45 adds the field for failed-reinforce opt-out
  • Server announces failed +9 to all players
  • In-game opt-out is implemented
  • Website opt-out is implemented
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.