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

Offen
#3,667 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go, typescript
Bereich
game-dev

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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).

Vorherrschende Sprache
Go
Sterne
97
Forks
61
Ø Merge
4 Std. 14 Min.
Gemergte PRs (30 T.)
913

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus opensro-dev/opensro

Alle Issues in opensro-dev/opensro

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.