Attendance calendar with continuity and accumulation rewards (port-only, flagged)

未关闭
#3,255 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, typescript

调研方向

The payload names no files or entry points, so first find where the existing event or reward UI lives in the TypeScript client and where per-character data is stored on the Go server. Gate new code behind the SRO_ flag and confirm the flag-off build is unchanged. Done when a daily check-in is saved per character, both reward tracks pay once per month, and the calendar and Reward tab match the screenshots.

由索引模型根据 Issue 内容生成。

描述

area: client area: server enhancement priority: high

Owner ask, 2026-11-12, from screenshots of a v2.355 third-party client (port-only, not native, so it ships behind an SRO_ flag).

Attendance calendar. A month grid where checked days are marked, a "Check Attendance" button and an END marker on the event's last day. A Reward tab has two columns:

  • Continuity Days (3, 8, 16, 23, 30 consecutive days);
  • Accumulation Days (5, 10, 15, 21, 27 total days).

Each row has an item and a Receive button.

Done when: a daily check-in is stored per character, both reward tracks pay once per month, and the flag-off build is unchanged.

主要语言
Go
星标
97
派生
61
平均合并
4 小时 14 分钟
30 天内合并 PR
913

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

opensro-dev/opensro 的其他 Issue

查看 opensro-dev/opensro 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。