Contributor title: Discord Contributor role shows a yellow title in game (port-only)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, typescript
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- 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