Teleport level refusal names the level: "... does not meet the requirement. [LVL: 90]"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, javascript, typescript
Research direction
Start with buildTeleportDataAsset.mjs, which produces teleportData.json, and find where the teleportlink condition kind 1 level band (columns 6-20) is read. Then trace the travel-gate command from the UI to the worker, where noticeText receives the new suffix. Done means the catalogue carries the band, the refusal shows [LVL: 90] or [LVL: 1-20] behind an Experimental row, that row can be switched off, and tests cover both bands and the off case.
Written by the indexing model from the issue text.
Description
Owner's ask (2026-11-15). The native line UIIT_MSG_INTERACTION_FAIL_OUT_OF_REQUIRED_LEVEL_FOR_TELEPORT ("Cannot transport because your level does not meet the requirement.", 0xB495 {2, 0x15}) does not say which level.
Plan (branch feat/teleport-level-tag)
- The teleport catalogue (
buildTeleportDataAsset.mjs-> teleportData.json) carries each link's level band (teleportlink condition kind 1, columns 6-20). - The UI puts the chosen link's band on the travel-gate command; the worker appends the tag to the refusal through a
suffixon the notice (noticeText). - Tag:
[LVL: 90]for an open band (max 999: Alexandria 90-999, DH cave exit 50-999),[LVL: 1-20]for a capped band (the 18 beginner gates, where the player is too high). - Port-only, not native: an Experimental row; the wire is unchanged.
Done when
- Catalogue, notice suffix, Experimental row; tests for both bands and the row off.
- 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