Battle Arena engine for Styria Clash (job arena), port-only behind SRO_STYRIA_CLASH (epic)

Abierto
#3,648 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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
Área
backend, game-dev

Línea de trabajo

Start with the #3272 scope record (issuecomment-6902778867), which carries the client tables and the v1.188 evidence, then read how existing port-only features are gated on their flag so SRO_STYRIA_CLASH can follow the same posture. Slice 1 is the smallest entry: the schedule definitions and the arena manager NPC (NPC_BATTLE_ARENA_MANAGER, service 0x21) registration checks. Done means a Hunter and a Thief can apply, be matched into world 107, score treasure and receive the banded reward with the flag on, and nothing changes with it off.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: client area: server enhancement priority: high

Epic (owner decision 2026-11-16, on #3272): build the Battle Arena engine that Styria Clash runs on. Port-only, not native to v1.150, behind SRO_STYRIA_CLASH (off = native). Rules come from the v1.188 server where it shows them; anything inferred is recorded in a code comment.

Evidence and the client's own tables are in the #3272 scope record (issuecomment-6902778867). The arena map itself is #3272's slice 1, not this epic.

Slices (one PR each, in order)

  1. Schedule and registration. The participation and match windows (the v1.188 SCHEDULE_DEF_BATTLE_ARENA_JOB(_PARTICIPATION) shape). Applying at the arena manager (NPC_BATTLE_ARENA_MANAGER, service 0x21): a job suit worn, no party before entry, one entry per character.
  2. Matching and the instance. Hunters and Thieves split into the two sides. One INS_ARENA_JOB_WAR (world 107) per match, entered at GATE_HUNTER_SPAWN / GATE_THIEF_SPAWN. Return on the end, death or logout.
  3. Treasure and scoring. The treasure boxes (SKILL_ARENA_JOB_WAR_BOX_OPEN), the side holding more treasure wins, the draw rule, and the five arena buffs (SKILL_ARENA_JOB_WAR_*_BUFF).
  4. Rewards. Job EXP 20/3/6 (win/lose/draw), the level-banded reward, rune seals for a win, and blue/black stones 5/1/2, all from gameworldconfigdata. Also the arena exchanger (NPC_BATTLE_ARENA_EXCHANGER, 0x22) and the "Win %d Styria Clash matches" achievement.
  5. Client. The registration and score screens the v1.150 client lacks, as port-only UI behind the same posture.

Done when

With the flag on, a Hunter and a Thief can apply, be matched, fight for treasure, and get the win, lose or draw reward. With the flag off, nothing changes.

Refs #3272, #3247.

Lenguaje dominante
Go
Estrellas
97
Forks
61
Merge medio
4 h 14 min
PR fusionados (30 d)
913

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de opensro-dev/opensro

Todos los issues de opensro-dev/opensro

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.