- A creature that was already walking when it came into view stood frozen at
its spawn point, then teleported — up to a full wander leg, 30 yards in the
worst measured case — when its next movement packet arrived. The create
packet carries the live path (where the unit is along it, how much is left)
and we parsed all of it into the void. The unit now joins its walk exactly
where the server has it: measured before/after, 13% of movement starts were
over-a-yard teleports, now effectively zero.
- Walking into Zul'Gurub or Stratholme through the portal dropped you straight
through the world. The landing check asks "is there a floor under me?" — but
on the arrival frame the loaded world is still the map you just left, and an
instance entrance is a copy of its outdoor ground at the same coordinates,
0.23 yards under your feet. The old floor said yes, then despawned. The hold
now waits for the destination's own ground to arrive, and a world that never
arrives keeps the loading screen instead of dropping you into the void.
- Same fix covers a decoder hazard found on the way: a plain two-point path
announces two points but ships only the destination, and trusting the count
over-ran the packet — it never fires on our server's pathfinder, but now it
can't.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Duels. Challenge another player from their right-click menu, or with `/duel`, and
`/forfeit` to give it up. Both popups are there — the challenge you accept or decline, and
the warning when you leave the field — with the flag countdown between them, and the outcome
printed in chat when someone is knocked out or flees. Read off the reference client's own
duel packets and the three globals it keeps client-side, which is why the challenger reads
"You have requested a duel." even though the server never echoes that back.
- Inspect. Right-click a player and open their paper doll: their nineteen publicly visible
equipment slots with icon, name, quality and a linkable item, and their body standing in
the pane, which follows along if you retarget while the window is open. No stack counts and
no durability — those are not fields another player publishes, which is exactly why the
reference client's inspect doll has never shown them either.
- Water knows where it stops. Swimming used to trigger in the dry tunnel thirty yards under
Stormwind's canal, and in mid-air over Blackrock's lava. A liquid is now the grid the map
file actually stores — one wet flag per cell, and the surface height a bilinear over the
four corners of the cell you are standing in, the same sample the reference client takes —
so the water starts at the bank and its surface sits where your eye puts it. Lava is a
liquid you swim in, an indoor liquid asks the building you are inside, and `/liquid` prints
every surface claiming your feet and where each one came from.
- Creature parts authored to appear only on death — the voidwalker, the banshee, the ooze,
the stone elemental, the infernal — were drawing the whole time: material alpha now bakes
per animation sequence and the unit lane actually evaluates it. The character and inspect
model panes are lit by the reference widget's own single light instead of blowing out white,
the rotate arrows spin while you hold them, and the transparent sort ladder had its sign
backwards, so overhead names draw over water again instead of being painted out by a canal
behind them. Underneath, the protocol writer's 95-verb drawer and its thousand-line spell
module split into per-family files — no behaviour change, just a tree you can find things in.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
