In-game Event Calendar window: the week's events, today highlighted
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, typescript
Research direction
Start with AGENTS.md for the non-native rule and the Experimental menu row, then find where existing CIF-native windows are built in the client. The server side sits behind the SRO_EVENT_CALENDAR flag and reads the schedule feed from #3520, which is not yet available. Done means the grid, detail panel and footer render in native style, with tests for a feed fixture, today's column and an empty day, under both flag settings.
Written by the indexing model from the issue text.
Description
Seen in the owner's screenshots of a downstream fork's client (2026-11-15). The site work is web#142 and the feed is #3520; this is the in-game window over the same feed.
What it does
- A seven-day grid (today first, highlighted) with each event's time, name and one line of rules and reward ("5 rounds · 5 min each · Silk Scroll (10)").
- A detail panel for the selected event (the reference shows the Lottery: pool, tickets, next draw, how to enter).
- Footer: how to take part and that times are server time; a "What's new" button opens the changelog.
Depends on
- #3520 (the schedule feed lists every event) and the chat-event issues filed with this one.
Done when
- Client: the window in native style, fed by the schedule feed; times in server time.
- Opens from a hotkey or the existing menu (Experimental row).
- Tests: the grid from a feed fixture, today's column, an empty day.
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_CALENDAR (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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opensro-dev/opensro
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
area: client bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opensro-dev/opensro#3228 · 1 comment ·
Maintainers usually reply within 1 day
-
Format one minified client file with dprint (ongoing: one file per PR)Possibly taken A pull request linked to this issue is open or already merged. Openarea: client enhancement good first issue priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#1 · 1 comment ·
Maintainers usually reply within 1 day
-
area: server bug priority: medium
Difficulty 3/5 Half a day Newbie friendliness 55/100
opensro-dev/opensro#3687 ·
Maintainers usually reply within 1 day
-
area: ops bug priority: high
Difficulty 4/5 3-5 days Newbie friendliness 32/100
opensro-dev/opensro#3685 ·
Maintainers usually reply within 1 day
All issues in opensro-dev/opensro
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OneBusAway/maglev#2102 ·
Maintainers usually reply within 2 days
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soOpen
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Maintainers usually reply within 1 day