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

Open
#3,648 0 comments 0 reactions 0 assignees View on GitHub

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

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
97
Forks
61
Avg merge
4h 14m
Merged PRs (30d)
913

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opensro-dev/opensro

All issues in opensro-dev/opensro

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.