Caret Coordinates

All notable changes to Caret Coordinates are documented here.

Fixed

//pos1 and //pos2 now work correctly with caret (^ ^ ^) coordinates. Previously, resolving a caret triple split the result into three separate command parameters (e.g. 123.4567 65.0 458.125). //pos1 //pos2 only accept a single combined coordinate argument, so the extra two parameters were rejected outright: Too many parameters! Unused parameters: 66 87.5 Usage: //pos2 [coordinates]

Only the first axis was ever applied, and the position was never actually set as intended.

Caret coordinates resolved for //pos1///pos2 are now merged into a single comma-joined token (x,y,z) instead of three space-separated tokens, matching the argument format these two commands expect. Those merged coordinates are also now whole block numbers (-111,79,89) instead of decimal values (-111.25,79.0,89.5), since //pos1///pos2 don't accept (number).(number) input — only plain integers. Notes This change is scoped to pos1/pos2 only. Every other caret-aware command (/summon, /tp, /execute, Motion:[^x,^y,^z], etc.) is unaffected and still resolves to full decimal coordinates as before.