Fall damage is one of the most common things server owners want to switch off. Whether you are running a creative build server where players are constantly working at height, a parkour map where dying to a missed jump kills the fun, or a survival realm where you simply want a more forgiving experience, knowing exactly how to disable fall damage saves a lot of frustration. The good news is that on any modern Minecraft Java server it takes a single command. The slightly more involved news is that the method depends on your version, whether you want it server-wide or per-player, and whether you are on Java or Bedrock. This guide walks through every approach in depth.
The quick answer: the fallDamage gamerule
If your server is running Minecraft Java Edition 1.15 or newer, you disable fall damage with a single game rule. Run this command in-game (as an operator) or in the server console:
/gamerule fallDamage falseThat is it. From the moment the command runs, players on your server take no damage from falling, regardless of the distance. To turn it back on, set the same rule to true. You can also check the current value at any time by running the command without a value:
/gamerule fallDamage
/gamerule fallDamage trueWhen you run a game rule command from the server console rather than in-game, you do not include the leading slash — just type gamerule fallDamage false. The change is saved with the world and persists across restarts, so you only need to set it once. The fallDamage game rule was introduced in Java Edition 1.15 (snapshot 19w36a) and defaults to true on every world.
Version matters: camelCase vs snake_case game rule names
Mojang renamed every game rule to snake_case in Java Edition 1.21.11 (released December 9, 2025). On that version and newer, the rule is written fall_damage rather than fallDamage. The behaviour and the default value are identical — only the spelling changed.
# Java 1.15 through 1.21.10
/gamerule fallDamage false
# Java 1.21.11 and newer (calendar versions like 26.x)
/gamerule fall_damage falseThe old camelCase names still work on 1.21.10 and earlier, and a huge number of existing servers, hosting panels, and tutorials still reference them — so do not panic if you see fallDamage everywhere. If you are unsure which version you are on, just try one; if the server reports an unknown game rule, switch to the other spelling. Mojang also moved to calendar-based version numbers in 2026 (for example 26.1.2), with the 1.21.x line being the last of the classic numbering before the switch.
| Minecraft version | Game rule name | Command |
|---|---|---|
| 1.15 – 1.21.10 | fallDamage | /gamerule fallDamage false |
| 1.21.11+ / 26.x | fall_damage | /gamerule fall_damage false |
| Pre-1.15 | No vanilla rule | Requires a plugin (see below) |
| Bedrock Edition | No equivalent | Requires a behavior pack / add-on |
Who can run the command? Operator permissions explained
Changing a game rule is a cheat-level action. On a vanilla, Spigot, or Paper server you need to be an operator at permission level 2 or higher to run /gamerule in-game. The /gamerule command sits in the same tier as /difficulty, command blocks, and target selectors. The server console always operates at the equivalent of level 4, so you can always set game rules from the console even if no one is opped.
If you have not opped yourself yet, you will need to do that first. The /op command grants the level defined by the op-permission-level key in server.properties, which defaults to 4 (full owner access). For a complete walkthrough of opping yourself, including editing ops.json directly to assign a custom level, see our guide on adding an op admin via ops.json.
Disabling fall damage before Minecraft 1.15
If you are running an older server — perhaps a legacy modpack or a long-lived world pinned to an early version — the fallDamage game rule simply does not exist. There is no vanilla way to turn off fall damage on Minecraft versions earlier than 1.15. Your only route is a plugin, which means your server must be running a plugin-capable fork such as Paper, Spigot, or Bukkit rather than the plain Mojang server.jar.
The general approach is to install a damage-control plugin (an EssentialsX-style or region plugin) that can cancel fall damage events. The exact command and configuration vary by plugin and version, so rather than quoting a command that may not match your setup, the reliable path is: install the plugin, open its config file, and look for a fall-damage or damage-cause toggle, then reload the plugin. Always check the plugin’s current documentation for the precise syntax on your version. If you have the option, the cleanest long-term fix is simply to update the server to 1.15 or newer and use the native game rule — it is faster, has zero performance cost, and never breaks on a plugin update.
Per-player fall damage immunity
The fallDamage game rule is global — it affects every player on the world at once. There is no vanilla game rule that disables fall damage for a single named player while keeping it on for everyone else. If you need true per-player control, you have a few options:
- Permission-based plugins: Plugins such as EssentialsX (and many region/protection plugins) expose per-player or per-group toggles via permission nodes. You grant a node to a specific player or rank and only they become immune. Check the plugin’s wiki for the exact node name on your version before relying on it.
- Game mode: Players in Creative or Spectator mode never take fall damage. If the goal is to let a builder work at height safely, switching that one player with
/gamemode creativeis the simplest no-plugin solution. - Effects: Slow Falling and Resistance can be applied per-player with
/effect give. Slow Falling in particular eliminates fall damage entirely for its duration, and you can refresh it or apply it for a very long duration as a lightweight per-player workaround.
# Apply Slow Falling to one player for ~1,000,000 ticks (long duration)
/effect give Notch minecraft:slow_falling 1000000 0 trueFor most servers, the global game rule is the right tool. Reach for per-player methods only when you specifically want different rules for different people.
Disabling fall damage on Bedrock Edition
Bedrock Edition is a different beast. The Bedrock Dedicated Server (BDS) is Mojang-only software with no plugin API — instead of plugins, it uses behavior packs and add-ons. Critically, the game rule sets between Java and Bedrock are not identical, and Bedrock does not have a fallDamage game rule equivalent the way Java does. You cannot simply run the Java command on a Bedrock realm or BDS instance and expect it to work.
On Bedrock, the practical routes to remove fall damage are:
- Behavior pack / add-on: A behavior pack can override entity damage behaviour or apply effects, achieving the same result as the Java game rule. This is the closest thing to a “native” solution on Bedrock.
- Slow Falling effect: The
/effectcommand exists on Bedrock too, and Slow Falling cancels fall damage while active — usable per-player or via repeating command blocks for everyone.
Worth knowing about the broader Java/Bedrock split: Bedrock servers listen on UDP port 19132 (and 19133 for IPv6) rather than Java’s TCP 25565; Bedrock uses an allow-list with allowlist.json instead of Java’s white-list and whitelist.json; and Bedrock uses a visitor / member / operator permission model keyed by XUID in permissions.json rather than Java’s numeric op levels 1–4. The two editions are not server-compatible, so always confirm a feature exists on your edition before relying on it.
| Feature | Java Edition | Bedrock Edition |
|---|---|---|
| Default port | TCP 25565 | UDP 19132 (IPv6 19133) |
| Server software | server.jar / Paper / Spigot | Bedrock Dedicated Server (BDS) |
| Extensions | Plugins (on Paper/Spigot) | Behavior packs / add-ons |
| Fall damage toggle | /gamerule fallDamage false | No game rule — behavior pack or effect |
| Allow list file | whitelist.json | allowlist.json |
Setting it on XGamingServer
On a managed Java server the workflow is straightforward. Connect to your server’s in-game console or open the console in your control panel, make sure you are opped at level 2 or above, and run /gamerule fallDamage false (or fall_damage on 1.21.11+). The setting is saved to the world immediately and survives restarts. If you would rather host somewhere that makes running these commands painless — with an instant console, one-click version switching, and full file access for plugins — take a look at our Minecraft server plans. For step-by-step panel screenshots covering console access, op management, and game rules, our Minecraft documentation walks through the control panel in detail.
Related server tweaks worth knowing
Fall damage is usually one of several survival rules people relax when setting up a casual or creative-leaning server. Game rules follow the same pattern, so once you have the syntax down you can apply it everywhere. A few common companions to disabling fall damage:
/gamerule keepInventory true— players keep their items and experience on death./gamerule doDaylightCycle false— freeze the time of day. See how to stop the day cycle./gamerule mobGriefing false— stop mobs (including creepers) from breaking blocks. If you only want to stop creepers while keeping TNT working, that needs WorldGuard — see disabling creeper explosions and TNT./gamerule doWardenSpawning false— yes, there is a real vanilla rule for this (added in 1.19, renamedspawn_wardensin 1.21.11). See how to stop warden spawning.
Remember the same camelCase-to-snake_case rename in 1.21.11 applies to all of these — for example keepInventory became keep_inventory and doDaylightCycle became advance_time.
Frequently asked questions
What is the command to turn off fall damage in Minecraft?
On Java Edition 1.15 and newer, run /gamerule fallDamage false in-game as an operator (level 2+) or type gamerule fallDamage false in the server console. On Java 1.21.11 and newer the rule is spelled fall_damage, so use /gamerule fall_damage false. The setting saves with the world and stays in effect after restarts.
Why doesn’t /gamerule fallDamage work on my server?
There are three usual causes. First, your version may be too old — the rule did not exist before 1.15, so a pre-1.15 server will report it as unknown and you will need a plugin instead. Second, you may be on 1.21.11 or newer, where the rule was renamed to fall_damage — try that spelling. Third, you may lack permission: you need to be opped at level 2 or higher, or run the command from the console. Double-check the version and the spelling before assuming something is broken.
Can I disable fall damage for just one player?
Not with a vanilla game rule — fallDamage is global and affects everyone. For true per-player control you need a permission-based plugin like EssentialsX, where you grant a fall-damage immunity node to a specific player or rank. Without plugins, the simplest workarounds are putting that player in Creative or Spectator mode (neither takes fall damage) or applying the Slow Falling effect to them with /effect give , which cancels fall damage for its duration.
How do I turn off fall damage on a Bedrock or Realms server?
Bedrock Edition has no fallDamage game rule equivalent, and the Bedrock Dedicated Server has no plugin API. The two practical options are a behavior pack/add-on that overrides damage behaviour, or applying the Slow Falling effect (per-player or via repeating command blocks) since /effect works on Bedrock. The Java command will not work on Bedrock — the editions have different game rule sets and are not server-compatible.
Does disabling fall damage affect mobs too?
The fallDamage game rule applies to players. Mob fall damage is handled separately — for example, in a WorldGuard region you would use that plugin’s own fall-damage flag rather than the vanilla game rule. If you specifically need to control mob fall damage (for instance, in a mob farm), confirm the exact flag or setting in your protection plugin’s current documentation before relying on it, as behaviour can differ by version.
Will turning off fall damage cause lag or performance issues?
No. The vanilla game rule has essentially zero performance cost — it is just a boolean flag the server checks when calculating damage, so it is far lighter than running a plugin to do the same job. This is one more reason that, if your only obstacle is an old pre-1.15 version, updating to use the native game rule is preferable to installing a damage-control plugin.
Wrapping up
For the vast majority of servers, disabling fall damage is a one-line job: /gamerule fallDamage false on Java 1.15 through 1.21.10, or /gamerule fall_damage false on 1.21.11 and newer. Drop to a plugin only if you are stuck on a pre-1.15 version or need genuine per-player control, and remember that Bedrock requires a behavior pack or the Slow Falling effect rather than a game rule. Set it once, op level 2 or higher, and your players can leap from any height in peace. While you are in the console, it is a good time to dial in the rest of your survival rules too — keep-inventory, day cycle, mob griefing, and warden spawning all follow exactly the same pattern.
Free Minecraft Tools
Speed up your server with our free Minecraft tools:
Ready to play?
Run your own Minecraft server with XGamingServer
Spin up an always-on Minecraft server your friends can join in minutes — no port-forwarding, no tech headaches.
