World: eastward moves refused at region 0x6397 (586, 516) on the Hyeongcheon road, bone props

Open
#3,667 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
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

area: server bug priority: medium

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

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.