ProjectKorra is the best documented starting point for bending gameplay, but it is not a native Bedrock plugin. ProjectKorra runs on Spigot-compatible Java servers. To let Bedrock players use it, run a Java server such as Paper or Spigot, install ProjectKorra for the bending systems, and add Geyser as the Bedrock-to-Java bridge. Add Floodgate when Bedrock players should authenticate with Xbox Live without owning a paid Java Edition account.
If you want to run this Java-and-Geyser stack on a hosted game server, Godlike.Host Minecraft hosting provides Minecraft Java and Bedrock hosting with a Pterodactyl-based game panel, SFTP/FTP access and up to three free backups a day with restore; see the current plans.
As an Amazon Associate I earn from qualifying purchases.
This distinction prevents the most common setup mistake: uploading a Java plugin to a Bedrock-only server and expecting it to load. The stack below gives you elemental disciplines, Bedrock connectivity and, when needed, Bedrock-friendly authentication without pretending that ProjectKorra itself supports native Bedrock servers.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWhat “a Bedrock server” means for bending plugins
Minecraft Bedrock and Minecraft Java use different server software and plugin ecosystems. A native Bedrock Dedicated Server cannot load a Spigot or Paper plugin jar. ProjectKorra’s own FAQ describes it as a Spigot plugin intended for multiplayer servers, so it must run inside a Java server implementation.
#1 Best Overall
- Invizimals: The Alliance
- Discover the community's creations in the new store
- Access new mini-games and game modes
- Play together on your sofa too thanks to the split screen
Geyser changes how players connect, not where the gameplay plugin runs. The project describes Geyser as a translator between the Bedrock client and the Java server. Bedrock players connect through Geyser, while ProjectKorra executes on the Java server and handles bending abilities, permissions, commands and configuration.
| Server design | Can it run ProjectKorra? | How Bedrock players connect | Best use |
|---|---|---|---|
| Native Bedrock Dedicated Server | No; it cannot load Spigot/Paper plugins. | Native Bedrock connection | Vanilla Bedrock gameplay or Bedrock-native add-ons |
| Java server with Geyser | Yes, when the Java server supports the ProjectKorra build. | Geyser translates Bedrock connections to Java. | Elemental bending with Bedrock cross-play |
| Java server with Geyser and Floodgate | Yes, with the same ProjectKorra requirement. | Geyser handles translation; Floodgate can authenticate Bedrock accounts without paid Java ownership. | A Bedrock-friendly community server with the fewest account barriers |
Therefore, the practical answer is not a single “Bedrock bending plugin.” It is a compatible Java plugin stack exposed to Bedrock clients.
The recommended plugin stack
1. ProjectKorra for the core bending game
ProjectKorra is the strongest documented foundation for elemental gameplay. Its official site calls it “The #1 open source Minecraft plugin for bending” and says it has powered elemental gameplay since 2014. The site currently reports more than 12 years of history, more than 1 million downloads and more than 100 plugins and add-ons. Those are publisher-reported figures, not an independent usage audit.
The core plugin supplies the disciplines and the systems around them. Its repository describes airbending as focused on mobility and defense, waterbending as focused on maneuverability and manipulation, and provides documentation for commands, permissions and server customization. Begin with this core rather than installing a large collection of add-ons immediately; it gives you a known baseline for troubleshooting.
Rank #2
- Minecraft is a game about placing blocks and going on adventures
- Explore randomly generated worlds and build amazing things from the simplest of homes to the grandest of castles
- Play in creative mode with unlimited resources or mine deep into the world in survival mode, crafting weapons and armor to fend off the dangerous mobs
- Play on the go in handheld or tabletop modes
- Includes Super Mario Mash-Up, Natural Texture Pack, Biome Settlers Skin Pack, Battle & Beasts Skin Pack, Campfire Tales Skin Pack; Compatible with Nintendo Switch only
- Gameplay: elemental disciplines and their abilities form the main bending experience.
- Administration: commands, permissions and configuration let an operator control access and server behavior.
- Extensibility: community add-ons can add abilities or related systems after the core installation is stable.
- Compatibility requirement: the ProjectKorra build must support the exact Java server version you select.
2. Geyser for Bedrock connectivity
Geyser is the compatibility layer that allows Bedrock clients to join a Java server. Install the version intended for your Java server platform and configure it according to the current Geyser documentation. It does not turn ProjectKorra into a Bedrock plugin, and it does not make a native Bedrock server load Java jars.
Think of the responsibilities this way: Geyser translates network and protocol behavior, while ProjectKorra owns bending rules. If a Bedrock player can join but an ability does not behave correctly, the problem may be a gameplay compatibility issue rather than a connection failure.
3. Floodgate when Bedrock-only account access matters
Floodgate is optional. Its documented purpose is to work alongside Geyser so Xbox Live-authenticated Bedrock users can join a Java server without owning a paid Java Edition account. The project also documents account linking and Bedrock forms.
Recommended Free Tools
Install Floodgate when your audience is primarily Bedrock players or when requiring Java ownership would exclude people you want to invite. If every player already owns Java Edition and your authentication policy does not need the extra Bedrock path, Geyser alone may be sufficient. Floodgate does not replace Geyser; it complements it.
Rank #3
- Minecraft is a game about placing blocks and going on adventures.
- Explore randomly generated worlds and build amazing things from the simplest of homes to the grandest of castles.
- Play in creative mode with unlimited resources or mine deep into the world in survival mode, crafting weapons and armor to fend off the dangerous mobs.
- Includes Super Mario Mash-Up, Natural Texture Pack, Biome Settlers Skin Pack, Battle & Beasts Skin Pack, Campfire Tales Skin Pack;Compatible with Nintendo Switch only.
- Play on the go in handheld or tabletop modes.
Community add-ons: useful, but a separate maintenance decision
Once ProjectKorra, Geyser and (if needed) Floodgate work on a test server, evaluate add-ons one at a time. Every add-on increases the number of version, permission and user-interface interactions you must maintain.
JedCore and ProjectAddons
ProjectKorra’s FAQ identifies JedCore and ProjectAddons as known community side plugins associated with bending boards and add-on abilities. ProjectKorra explicitly says these projects are not maintained by ProjectKorra and points readers toward version-specific historical downloads. Treat them as independent software: verify the supported Minecraft version, inspect the author’s release notes and test on a copy of the world before putting them on a public server.
Bending Items
Bending Items is a separate community plugin for item-driven bending mechanics. Its resource page says items are defined through YAML configuration. That can be valuable when you want a particular item to alter or trigger bending behavior rather than relying only on the core ability set.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The same page records a creation date of July 8, 2021 and a latest update of September 2, 2023. Those dates do not prove that it is unusable, but they do mean current-version compatibility must be checked rather than assumed. Test item interaction, permissions, reload behavior and Bedrock presentation before deployment.
Rank #4
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
| Option | What it adds | Maintenance status to account for | When to choose it |
|---|---|---|---|
| ProjectKorra core | Disciplines, abilities, commands, permissions and customization | Use the release that matches your Java server | Every bending server; install first |
| JedCore | Community bending-board and ability extensions | Not maintained by ProjectKorra; check its own version history | When its specific abilities are worth the extra compatibility work |
| ProjectAddons | Community add-on abilities and related extensions | Not maintained by ProjectKorra; verify the release for your server | When you need content beyond the core disciplines |
| Bending Items | Custom item-driven mechanics configured in YAML | Its listed latest update is September 2, 2023 | When custom items are central to your game design and pass current-version testing |
How to build the setup safely
Use a staging server first. A bending plugin changes player abilities, permissions and world behavior; adding the network bridge and authentication layer at the same time makes failures difficult to isolate.
- Select a Java server implementation. Choose a Paper- or Spigot-compatible server version for which the ProjectKorra release explicitly provides support. Record the Minecraft version, Java runtime and plugin versions before installing anything.
- Create a separate test instance and back up your production world. Copy the world and server configuration to a staging location. Do not test an unfamiliar add-on directly on the only copy of a live world.
- Install ProjectKorra first. Place the compatible ProjectKorra plugin in the Java server’s plugins directory, start the server, and read the startup log for dependency, version or configuration errors. Confirm that ProjectKorra creates its configuration and that its documented commands and permissions are available.
- Test Java gameplay before adding Bedrock access. Join with a Java client, assign a test player the required permission, select a discipline and exercise representative abilities. This establishes that the core plugin works independently of Geyser.
- Install Geyser for your server platform. Add the Geyser plugin or the appropriate Geyser deployment, then follow its current configuration instructions for the Bedrock listener and network port. Keep the Java server reachable to Java clients while you verify the Bedrock route.
- Add Floodgate only if your account policy needs it. Install the matching Floodgate component alongside Geyser and complete its documented authentication setup. Decide whether you will permit linked accounts, Bedrock-only accounts or both, and document that policy for players.
- Connect with a Bedrock test account. Check login, spawn location, chat, inventory, movement and ability activation. Test at least one ability from each discipline you intend to offer, because a successful login does not prove every interaction renders or controls correctly on Bedrock.
- Add community extensions individually. Install one add-on, restart, test permissions and abilities, and inspect logs before installing the next. If a failure appears, you can then identify the most recent change.
- Promote the tested configuration. Copy the known-good versions and configuration to production, retain the backup and write down a rollback procedure before inviting the wider community.
Bedrock-specific checks before launch
Java and Bedrock clients do not present every control and interface identically. Bending abilities that depend on precise key combinations, unusual inventory interactions or Java-specific visual cues deserve extra testing with a real Bedrock client rather than a Java player using a protocol bridge.
- Control mapping: verify how ability selection and activation feel on touch controls, a controller and a keyboard-and-mouse Bedrock setup if your audience uses all three.
- Forms and menus: Floodgate documents Bedrock forms; check that any menu-driven workflow is understandable and usable at the actual Bedrock screen resolution.
- Feedback: test titles, action-bar messages, particles, sounds and cooldown indicators. A mechanic can function server-side while giving a Bedrock player insufficient feedback.
- Identity and permissions: confirm how Floodgate-authenticated names map to your permission system and how account linking affects an existing player’s progress.
- Performance: test busy fights and several simultaneous ability users. A quiet solo test cannot reveal the cost of particle-heavy or event-heavy add-ons.
Administration and configuration priorities
Permissions before public access
Create a small test role with only the permissions required to choose a discipline and use its abilities. Verify that a player without those permissions cannot invoke the same commands or actions. Expand access deliberately rather than granting a broad administrator permission to everyone.
World and gameplay boundaries
Decide where bending is allowed: a dedicated arena, selected worlds or the entire server. Test block interaction, damage, mobility and environmental effects near protected builds. If an add-on introduces a new ability, review its permission and configuration entries before enabling it globally.
Best Value
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
Version discipline
Record the exact server, Java runtime, ProjectKorra, Geyser, Floodgate and add-on versions. Update one layer at a time, back up first and retest both a Java account and a Bedrock account after every update. Community add-ons are particularly sensitive to changes in the core plugin or server API.
Player documentation
Publish the disciplines you offer, the commands or menu path used to select them, the supported Bedrock controls and the account requirements. Tell Bedrock players whether Floodgate permits them to join without Java ownership and explain how account linking works if you enable it.
Choosing between a minimal and expanded setup
| Goal | Install | Trade-off |
|---|---|---|
| Test elemental gameplay with the fewest moving parts | Compatible Java server plus ProjectKorra | Java clients only until a bridge is added |
| Let Bedrock players join while retaining the Java plugin ecosystem | Java server, ProjectKorra and Geyser | Requires bridge configuration and Bedrock-specific testing |
| Lower the account barrier for Bedrock players | Java server, ProjectKorra, Geyser and Floodgate | Adds authentication and account-policy decisions |
| Offer more abilities or custom item mechanics | One of the above stacks plus a tested community add-on | More features, but more version and maintenance risk |
For most small communities, the sensible progression is ProjectKorra first, Geyser second, Floodgate if required, and add-ons only after the base experience is stable. That order separates gameplay, connectivity, authentication and extension problems.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Troubleshooting common failures
| Symptom | Likely cause | What to check |
|---|---|---|
| The plugin does not load on startup | The server is native Bedrock, the jar targets another platform, or the Minecraft version is unsupported. | Confirm that the server is Paper/Spigot-compatible and that the ProjectKorra build supports its exact version. |
| Java players can bend, but Bedrock players cannot join | Geyser is missing or its listener/network settings are incorrect. | Check the Geyser installation, configured Bedrock port and firewall or host port exposure. |
| Bedrock players join but cannot authenticate as intended | Floodgate is absent or its authentication setup does not match the server policy. | Review the current Floodgate and Geyser configuration and test with a fresh Bedrock account. |
| An add-on breaks after an update | The community add-on is not compatible with the new server or ProjectKorra build. | Remove the add-on from staging, restore the last known-good versions and check the add-on author’s release information. |
| An ability works in Java testing but is confusing on Bedrock | Control, menu or feedback differences are obscuring the mechanic. | Test the exact Bedrock device, document the control path and provide clearer player feedback where configuration allows. |
| A player has unexpected access | Permission inheritance or account-linking behavior is broader than intended. | Inspect the player’s effective permissions and test linked and unlinked identities separately. |
Questions to answer before choosing an add-on
- Does the release explicitly support the Minecraft and Java server versions you run?
- Was it updated recently enough for your maintenance policy?
- Is it maintained by the ProjectKorra team or by an independent community author?
- Does it document permissions, configuration keys, reload behavior and dependencies?
- Can Bedrock players understand and activate its abilities with your supported controls?
- Can you remove it cleanly and restore the previous world and configuration from backup?
If you cannot answer those questions, keep the core stack and postpone the add-on. A smaller, predictable bending experience is preferable to an impressive ability list that fails after the next server update.
Bottom-line recommendation
Use ProjectKorra as the bending core on a compatible Paper or Spigot server. Add Geyser to let Bedrock clients connect, and add Floodgate when Bedrock players need to join without paid Java Edition ownership. Treat JedCore, ProjectAddons and Bending Items as optional community extensions, not automatic parts of ProjectKorra, and validate each against your exact server version and Bedrock control scheme.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
