Import the Bandit fortress from the later client
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
- Domain
- game-dev
Research direction
Start by finding how the existing later-client imports are wired (the pipeline behind refs #3512/#3513) and compare a shipped fortress such as Jangan against the v1.188 siegefortress.txt row 6 to list every field the importer must map. Read the M map page list from #3571 and the caption case for page 1002 to see where the new page and the SN_FORTRESS_BIJEOKDAN caption belong, then locate the siege-rule code shared with Jangan. Done means import tests plus a map-page test pass, and the fortress is reachable and its map page visible in game with no retail assets committed.
Written by the indexing model from the issue text.
Description
What the player sees
There is no Bandit fortress: not in the world and not on the M map's fortress pages. The v1.150 data never shipped it (#3512). The owner wants it in the game (2026-11-15).
Source
The pinned v1.188 VSRO client has it:
siegefortress.txtrow 6FORTRESS_BIJEOKDAN(SN_FORTRESS_BIJEOKDAN,GATE_CH, small-fortress flag 1, values 200 / 15 / 20 / 96 / 500000,etc\fort_bijeokdan.ddj,NPC_CH_FORTRESS_OFFICIAL);- its art:
icon/etc/fort_bijeokdan.ddj,interface/worldmap/map/map_fort_bijuckdan.ddj,icon/npc/fortress_battleaide.ddj.
What v1.150 already has: the name SN_FORTRESS_BIJEOKDAN, the NPC NPC_CH_FORTRESS_BATTLEAIDE2, and the M map's caption case for page 1002 (576949).
Done when
- The import brings in the fortress's siege row, world area (regions, navmesh, objects), structures (gates, towers, guards, command post), NPCs, teleports and texts, with nothing committed from retail, as the other later-client imports work.
- The M map has page 1002 with its art and icons, and the 1002 caption shows
SN_FORTRESS_BIJEOKDAN(the page list from #3571 takes the new row). - The server runs the fortress under the same siege rules as Jangan, with the small fortress's own values from its row. Any rule that v1.188 does not show is inferred and recorded in a code comment.
- Tests cover the import and the map page, and someone has entered the fortress and seen its page in game.
Refs #3512, #3513.
- 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