World: eastward moves refused at region 0x6397 (586, 516) on the Hyeongcheon road, bone props
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, typescript
- Domain
- game-dev
Research direction
The issue pinpoints the failure but not the cause: start by replaying the captured movement.json window around 817.7 s so the nine refused eastward clicks at (586, 516) are reproducible, then compare the server's collision/navmesh data for region 0x6397 against the native client walking the same spot. Check whether the bone props' footprint is being registered as blocking geometry when it should be decoration only, and consult #2359 for prior placed-object collision work. Done means eastward movement at (586, 516) is accepted and the corrections in that region drop away.
Written by the indexing model from the issue text.
Description
From a player's in-game report, BR-261114-2319-0295 (Discord bug thread 1571303520941113456, 11-14 23:19Z). The player wrote that "something is blocking me" and that they could see "little bones in ground".
What the diagnostics show
- Where: region 0x6397 (25495), at local (586.3, -11.3, 515.9), on the sand road through the Hyeongcheon guard area. The "Urochi has appeared in Tarim Basin" notice is up.
- The block (
movement.json, last 25 s before the report):- from 817.7 s the character stands at (586, 516);
- nine eastward clicks follow (targets x 670–833). Each is accepted with the full target as its
serverGoal, then corrected back to (586, 516), distance 0.0; - request 244 (target 833, 602) comes back with
serverGoal= the current position (586.3, 515.9). The server refuses the whole segment.
- Earlier in the same session: 57 corrections in 103 moves, several of 27–43 units, all in the same regions (25494–26006).
- Replay (22 s, checked as frames):
- 0:00–0:14: fighting along the road; the view jumps where the corrections land;
- 0:15–0:21: the character stands beside a Hyeongcheon guard and does not move east. Small bone props lie on the ground just east of it, which is what the player calls "little bones".
What to find
- What blocks eastward travel at 25495 (586, 516): an object's collision, possibly the bone props' footprint, or a navmesh edge.
- Whether the native client walks through the same spot. The bone props are decoration, so a native client should not be stopped by them.
Related: #2359 (character wedged between placed objects; a different shape: here the character can move, just not east).
- 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