← JetRift   All guides

JetRift compatibility and limits

By JetRift · Updated

JetRift hosts shared worlds for Java 26.3 and Bedrock 26.60. It runs our Butternut engine and is in early access. Use this reference before inviting friends or moving an existing save.

FeatureCurrent supportPractical limit
Java Edition26.3, protocol 777Exact supported version; older and newer clients are not promised.
Bedrock Edition26.60, protocol 2225Exact supported version; app-store updates can move ahead of server support.
CrossplayJava and Bedrock in one world, includedNo Geyser install needed. Identities and inventories remain separate across editions.
Java devicesWindows, macOS and Linux Java clientsThe Minecraft for Windows app is Bedrock, not Java.
Bedrock devicesWindows, Android, iPhone and iPadUse the dashboard’s Bedrock details, normally UDP 19132.
ConsolesNo supported direct custom-server setupXbox, PlayStation and Switch need separate workarounds. Do not assume phone instructions apply.
Free planThree servers per account, no ads or cardShared finite capacity; intended for small friend groups, not a guaranteed large-server resource allocation.
Idle behaviorSleep after about two empty minutes; wake on joinNo simulation while asleep. A manual stop or failure may require dashboard action.
Java mods and pluginsJetRift’s own plugin catalogForge, Fabric, Paper and Spigot extensions do not load. Arbitrary datapacks and vanilla parity are not guaranteed.
World importJava world ZIP containing level.datNot a Bedrock .mcworld or LevelDB converter. Check dimensions, version and custom content on a copy.
BackupsWorld downloads; optional Google Drive connectionConfigure backups and keep an independent copy. Do not treat idle storage as your only backup.
Resource packsEdition-specific behaviorJava resource packs are not converted for Bedrock.

Player accounts and permissions

Java players use their Java identity. Bedrock players sign in with Microsoft/Xbox; the server adds a dot to their names and replaces spaces with underscores. For example, Sam Builder becomes .Sam_Builder. Use that exact name when managing the whitelist or operators. A matching visible name across editions does not merge progress.

Engine behavior

Butternut is a separate implementation, not Mojang’s server, Paper or a mod loader. Support for a client version means the client can connect; it is not a promise that every block, mob, redstone contraption or imported save behaves exactly like vanilla. Check known issues and test the mechanics your group relies on before a migration.

Capacity and performance

A free server does not reserve an unlimited CPU, memory or storage allocation. Startup can be delayed or fail when capacity is unavailable or a service is unhealthy. We do not publish a universal player-capacity promise: world size, loaded chunks, entities and plugins change the workload. Our benchmark page records the actual test environment and its limitations.

Before moving a world

Keep an untouched export. Test the Overworld, Nether, End, inventories, permissions and important builds on a copy. A world from a newer release, modded blocks or a different identity mode may require work outside the import tool. See the Aternos migration checklist.

If something here changes

This reference is checked against our engine protocol constants, dashboard and hosting configuration. Last checked 3 November 2026. The dashboard’s current join details take priority for your server. Report a mismatch using the feedback button so we can update the page and affected guides.

Joining instructions · Connection troubleshooter · Hosting chooser