Contributor title: Discord Contributor role shows a yellow title in game (port-only)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 12/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, typescript
调研方向
This is a design-heavy port feature spanning server, client and reverse-engineering research, so it is not a first task. Start by reading the Contract section: the contributors.json and contributor-titles.json files in the shard directory, the 0x3FC1 roster packet, and the SRO_CONTRIBUTOR_TITLES switch. Done means the native title routines are labelled in both Binary Ninja databases and the summary is posted here.
由索引模型根据 Issue 内容生成。
描述
Owner ask (2026-11-12): every Discord member with the Contributor role carries a yellow Contributor title in game, seen by everyone. On by default; a contributor can turn their own title off, and that choice is a server setting (every viewer sees the same state), not a client cosmetic.
Port-only, not native: behind SRO_CONTRIBUTOR_TITLES (off = native, nothing on the wire).
Contract
- Source of truth:
contributors.jsonin the shard directory,{"accounts":["<account id>", ...]}, written atomically by an ops sync (Discord role members -> linked game accounts). The GameWorld re-reads it when it changes (polled each minute); a missing file means no contributors, a corrupt one keeps the last good set and logs. - Opt-out:
contributor-titles.jsonin the shard directory, owned by the GameWorld only ({"hidden":["<account id>"]})./contributor offand/contributor onin chat change it for the speaker's account; a non-contributor gets a system line saying so. - Wire: S->C
0x3FC1(port-only, next free after 0x3FC0) carries the shown roster:u16 count, count x { u16 len, ascii name }, the character names currently online in the division whose account is a contributor and not hidden. Sent to a session on world entry and to every session in the division whenever the roster changes. - Client: a player whose name is in the roster gets a yellow
Contributorrow over the nameplate (above the guild row); chat lines from that sender get a[Contributor]tag that stands out from the yellow global channel.
Native research (same ticket)
Label every title-related routine in both Binary Ninja databases (client: CPSTitle/pstitle.txt, the com_honor_level_%d icon users incl. sub_6757a0/sub_6758e0, stall title mode 4 on the nameplate, siegefortressbattlerank.txt users; server: the matching senders). Record what v1.150 actually shows over a name and how it is switched on, in ../research and a summary here.
- 主要语言
- Go
- 星标
- 97
- 派生
- 61
- 平均合并
- 4 小时 14 分钟
- 30 天内合并 PR
- 913
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
opensro-dev/opensro 的其他 Issue
-
area: client enhancement priority: low
难度 2/5 1-3 小时 新手友好度 75/100
opensro-dev/opensro#3681 ·
维护者通常 1 天内回复
-
area: client bug priority: low
难度 2/5 1-3 小时 新手友好度 78/100
opensro-dev/opensro#3228 · 1 条评论 ·
维护者通常 1 天内回复
-
Format one minified client file with dprint (ongoing: one file per PR)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭area: client enhancement good first issue priority: low
难度 2/5 1-3 小时 新手友好度 75/100
opensro-dev/opensro#1 · 1 条评论 ·
维护者通常 1 天内回复
-
area: server bug priority: medium
难度 3/5 半天 新手友好度 55/100
opensro-dev/opensro#3687 ·
维护者通常 1 天内回复
-
area: ops bug priority: high
难度 4/5 3-5 天 新手友好度 32/100
opensro-dev/opensro#3685 ·
维护者通常 1 天内回复
查看 opensro-dev/opensro 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
unbound-force/gaze#353 ·
维护者通常 1 天内回复
-
bug cross-seed ready-for-human
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
OneBusAway/maglev#2102 ·
维护者通常 2 天内回复
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
维护者通常 1 天内回复