World map (M): the Bandit fortress is missing

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go, typescript
Domain
frontend, game-dev

Research direction

The payload names no files, so start by locating where the M world map gets its markers in the TypeScript client and how the asset pipeline supplies the v1.150 map and location data. Confirm whether the Bandit fortress entry exists in that data before touching the map code. Done when the fortress marker and label appear on the M map as the client shows them, or when a separate issue with evidence is opened for any missing world content.

Written by the indexing model from the issue text.

Description

area: client bug priority: critical

What the player sees

The M map shows no Bandit fortress. Check whether the fortress itself is missing in the world too, not only from the map.

Done when

  • The M map shows the Bandit fortress marker and label wherever the v1.150 client places it, with the client's own icon and text.
  • If the fortress is also missing in the world (NPCs, gate, structures), that is fixed or split into its own issue with evidence.
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.