Contributor title: Discord Contributor role shows a yellow title in game (port-only)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 12/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go, typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Go
- Estrellas
- 97
- Forks
- 61
- Merge medio
- 4 h 14 min
- PR fusionados (30 d)
- 913
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de opensro-dev/opensro
-
area: client enhancement priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#3681 ·
Los mantenedores suelen responder en 1 día
-
area: client bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
opensro-dev/opensro#3228 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Format one minified client file with dprint (ongoing: one file per PR)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea: client enhancement good first issue priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#1 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: server bug priority: medium
Dificultad 3/5 Medio día Aptitud para principiantes 55/100
opensro-dev/opensro#3687 ·
Los mantenedores suelen responder en 1 día
-
area: ops bug priority: high
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
opensro-dev/opensro#3685 ·
Los mantenedores suelen responder en 1 día
Todos los issues de opensro-dev/opensro
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
unbound-force/gaze#353 ·
Los mantenedores suelen responder en 1 día
-
bug cross-seed ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
OneBusAway/maglev#2102 ·
Los mantenedores suelen responder en 2 días
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Los mantenedores suelen responder en 1 día