Teleport level refusal names the level: "... does not meet the requirement. [LVL: 90]"

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

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

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

area: client enhancement priority: medium

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 suffix on 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

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.