The movement burst is now attributed: IffyBinkie6134 moved too quickly! -3556.6858076401522,-8.0,1147.6740068444371 -- the human Bedrock player, with a single delta of thousands of blocks, so the Java server kept snapping their position back. That is what feels like rubber-banding on entry, and it bothers the player more than the 172 ms ping does.
The translator is Geyser, not ViaProxy: ViaProxy 3.4.13 runs the Geyser plugin, and Geyser is what turns Bedrock movement into Java movement. The two editions move differently and upstream has not resolved it -- GeyserMC/Geyser#3407 is still open, and the Spigot/Paper thresholds it mentions (moved-too-quickly-multiplier, moved-wrongly-threshold) do not exist on a Fabric server. In that issue a reporter set the multiplier to 1000000 and it changed nothing.
TooFast is the server-side mixin that removes the vanilla speed check: toofast-1.19-1.0.0.jar, Fabric, Minecraft 1.19-1.19.2, MIT, environment 'server-side only'. The download is pinned by…
Install Voyager the way its README documents
naldo
652cf29
The Space cloned the pinned upstream and then only pointed PYTHONPATH at it:
the documented 'pip install -e .' had never been run, so the package was never
installed as a distribution.
Run the documented editable install and verify it took effect before learning,
enforce the README's Python >= 3.9 and Node.js >= 16.13.0 floors at boot, and add
the upstream requirements the Space was missing (tqdm, requests). cchardet stays
out on purpose: it is chromadb's optional accelerator and building it would fail
the Space build.
Document the full conformance table and every remaining deviation with its
reason, and cover the install with tests so it cannot drift silently again.
