VoxelParity

VoxelParity

Smooth out Bedrock movement on Java servers without changing how Java players move.

VoxelParity is a server-side plugin for Geyser servers that fixes several movement and collision differences between Minecraft Bedrock Edition and Java Edition.

Bedrock players can sometimes be pushed back, get stuck, or collide with blocks differently from how their client expects. VoxelParity fixes those mismatches only for Bedrock players, while leaving normal Java physics untouched.

✨ What does it fix?

🎋 Bamboo

Bedrock and Java use slightly different bamboo collision.

VoxelParity gives Bedrock players the collision their client expects, reducing strange bumps and rubberbanding when moving around bamboo.

Young bamboo sprouts remain pass-through as expected.

💧 Pointed Dripstone

Pointed dripstone can also have different collision between editions.

VoxelParity adjusts its collision for Bedrock players, including:

• hanging dripstone
• upward dripstone
• different dripstone shapes and thicknesses
• movement between closely placed dripstone

🏊 Crawling and low spaces

Bedrock players may switch between standing, sneaking, and crawling/swimming poses differently from Java players.

VoxelParity accounts for these transitions so the server does not unnecessarily push a player back while they are moving through a space their Bedrock client considers valid.

The plugin does not force player poses — Geyser and the server still control them normally.

❄️ Powder Snow

VoxelParity also contains a conservative fix for powder-snow movement mismatches.

It only steps in when the Java server rejects movement that should be valid for the Bedrock player. Normal powder-snow behavior is otherwise left alone.

🛡️ Designed to stay out of the way

VoxelParity does not replace the server's entire collision system.

It only applies targeted fixes when a known Bedrock/Java mismatch is detected.

• ✅ Bedrock players get corrected parity behavior
• ✅ Java players keep normal Java collision
• ✅ Mobs keep normal Java collision
• ✅ No client-side mod is required
• ✅ No global block collision replacement
• ✅ No chunk loading just to check movement

📦 Requirements

• Minecraft 26.3
• Java 25
• Leaf or a modern Paper-compatible server
• Geyser-Spigot or Floodgate

VoxelParity is developed Leaf-first.

If Geyser is running on a proxy or another machine, Floodgate should also be available on the backend so VoxelParity can identify Bedrock players.

⚙️ Commands

Command	Description
/vp status	Shows VoxelParity status
/vp modules	Shows active parity modules and counters
/vp debug <player> [on|off]	Toggles detailed diagnostics for a player
/vp reload	Reloads VoxelParity configuration

Admin permission:

voxelparity.admin

🔍 Debugging

VoxelParity includes detailed per-player debugging for server owners and developers.

Debug mode can show movement decisions, collision geometry, powder-snow state, player pose changes, and other information useful for reproducing Bedrock movement issues.

For normal server use, you can simply leave debug disabled.

🎯 Project goal

VoxelParity is not trying to replace Geyser or rewrite Minecraft movement.

The goal is to fix specific, reproducible Bedrock ↔ Java movement differences with small and safe server-side corrections.

More parity fixes may be added as real mismatches are found and tested.