Bedrock & Geyser optimization
Built-in movement setback fixes, mobile particle limits, and smooth chunk pacing for Geyser and Floodgate players.
On this page
Running a cross-play Java + Bedrock server with Geyser and Floodgate often causes two headaches on standard servers: Bedrock players getting rubberbanded ("pulled back") on stairs, slabs, or carpets, and mobile phones overheating or freezing in busy areas.
NusaSpigot solves both natively on the server—no extra movement-hack plugins required—while keeping strict vanilla checks for Java Edition players.
Automatic Bedrock player detection
Out of the box (bedrock-optimization.enabled: true), NusaSpigot automatically recognizes Bedrock players using three layers:
- Floodgate XUID UUIDs (
detect-floodgate-uuid: true): Instantly detects Floodgate players whose UUID upper 64 bits equal0—works behind standalone Geyser or Velocity proxies. - Geyser client brand (
detect-geyser-brand: true): Recognizes theGeyserbrand payload sent on join. - Username prefix fallback (
username-prefix: '.'): Matches your Floodgate prefix (such as.PlayerName) if UUID forwarding is customized. Setusername-prefix: ''if you do not use a prefix.
What NusaSpigot optimizes for Bedrock players
| Problem on cross-play servers | How NusaSpigot fixes it |
|---|---|
| Rubberbanding on stairs, slabs, fences, and carpets | Multiplies Spigot's moved-wrongly threshold by 2.5x and grants 40 extra floating tolerance ticks for Bedrock physics differences. |
| Mobile/Wi-Fi RakNet jitter kicks | Multiplies moved-too-quickly tolerance by 1.5x only for detected Bedrock connections. |
| Mobile FPS drops in particles or farms | Caps non-forced particles to 16 per packet within 24.0 blocks (max-particles-per-packet & max-particle-distance). |
| Geyser chunk translation lag spikes | Paces chunk delivery to 2.0 chunks per tick (max-chunks-per-tick) so fast flying or teleporting does not freeze mobile clients. |
| Bandwidth & battery drain in crowded areas | Keeps entities within 6.0 blocks at 1-tick smoothness, updates distant entities every 6 ticks, skips tiny < 5.6° head micro-rotations, and batches tab-list updates into 400 ms windows. |
Recommended Cross-Play YAML tuning
The default values in nusa-global.yml already work well for most Java + Bedrock SMPs. If most of your players play on budget Android/iOS phones over mobile data, you can tighten particle and chunk pacing slightly:
bedrock-optimization:
enabled: true
detect-floodgate-uuid: true
detect-geyser-brand: true
username-prefix: '.'
moved-wrongly-multiplier: 2.5
moved-too-quickly-multiplier: 1.5
extra-floating-tolerance-ticks: 40
near-distance: 6.0
far-entity-update-interval: 8
cull-micro-rotation-updates: true
max-particles-per-packet: 12
max-particle-distance: 20.0
max-chunks-per-tick: 1.5
tab-window-millis: 400Using Anti-Cheat plugins with Geyser
NusaSpigot relaxes vanilla server movement setbacks (ServerGamePacketListenerImpl), not third-party anti-cheat checks. If you also run Grim, Vulcan, or Matrix, make sure Floodgate is installed so your anti-cheat plugin exempts or adjusts checks for Bedrock players alongside NusaSpigot.