Batch craft was limited to the crafting bench; alchemy keeps its own UI, but furnace, anvil, jewelering, leatherworking, and the rest now share the same quantity buttons.
Bake sand→sand-wet within the outer 30% facing water (including diagonals). In winter only deep water counts, since shallow water is ice. Soft-terrain blending still applies; darkness stays on the lit atlas path.
The origin was the viewport centre, so it moved every frame and forced a
re-layer of the whole static world to stay consistent with entities. Quantise
it to the chunk row under the view instead: it only moves when the view
crosses a chunk border, and only then does #refreshDepthLayers run. Relative
sortY stays well inside LAYER_EDGE because chunks span the static 5x5 ring.
Layer writes now go through #setLayer, which skips the write when the value
is unchanged. A layer write costs the scene a full activeObjects sort, so a
frame in which nothing changes draw order no longer sorts at all.
Co-authored-by: Cursor <cursoragent@cursor.com>
Only baked chunk rows and per-frame entity placement re-applied the
viewport-relative depth layer, so unbaked tall blocks, doors, ground items
and static FX kept the layer they got at draw time. As the camera moved the
y-sort origin drifted away from it, letting blocks north of a southbound
player draw over him.
Also settle the camera and y-sort origin before any layer is computed in
update(); entities were previously placed against the previous frame's
origin while baked rows used the new one.
Co-authored-by: Cursor <cursoragent@cursor.com>
Disconnect during or shortly after combat leaves the entity in the world with
forced auto-cast until five quiet minutes pass; offline death forces a church
resurrection letter, and PvP logout cowardice adds skull points plus a Questward
warning (one free pass per clock hour).
Co-authored-by: Cursor <cursoragent@cursor.com>
PLAYER_RESPAWNED never sends the local client a new entity-spawn, so finishing
the red dissolve by deleting the sprite left respawn with nothing to show.
Co-authored-by: Cursor <cursoragent@cursor.com>