
Player data & inventories · Java & Bedrock · Beginner
How to Clear Deadly Potion Effects, Fire, and Reset Health in Player NBT
Logging out a split second before dying from lava, poison, or starvation creates a frustrating death loop where you perish the instant you rejoin your world. Because Minecraft saves your exact physical state and status timers upon disconnection, you can rescue your character before logging back in by modifying these saved values. Using our browser-based NBT Editor, you can safely reset your health, extinguish flames, and wipe deadly potion effects directly inside your local world files without uploading anything to a server.
What you need
- A complete backup copy of your Minecraft world folder before making any edits.
- Access to your Minecraft world save folder or a .zip archive of the world.
- Our browser-based NBT Editor tool.
- Your player's UUID (if editing a multiplayer Java Edition world).
Step by step
1Back Up Your World and Open the NBT Editor
Before touching any game files, duplicate your entire world folder and store the copy somewhere safe in case a tag is accidentally deleted. Once your backup is secure, open our NBT Editor tool in your browser, where all file processing happens locally on your device. Click 'Open world folder or .zip' and select your Minecraft world directory. For singleplayer Java worlds, your character data is stored directly inside `level.dat` (under the `Player` compound tag), whereas multiplayer worlds and recent versions also store individual files inside the `playerdata` folder named after your UUID (such as `playerdata/<uuid>.dat`).
Tip: If you are playing Bedrock Edition, singleplayer data is stored under the `~local_player` key inside the LevelDB database; if our tool lists player files, look for the local player entry.
2Restore Your Health to Maximum
Expand the root tree of your player data file (`level.dat` -> `Data` -> `Player`, or the root of your `<uuid>.dat` file) and locate the `Health` Float tag. In Minecraft, each full heart equals 2 health points, meaning a standard full health bar is `20.0`. Double-click the `Health` value and change it from its critically low number back to `20.0`. This ensures that even if you take a single tick of environmental damage upon loading in, you will have enough hit points to survive.
Tip: If you wear armor or use mods that increase max health, setting it to `20.0` is still completely safe and will simply fill your base ten hearts.
3Extinguish Fire and Refill Air
Scroll through the player tags to find the `Fire` Short tag, which tracks how many game ticks you will remain burning. When you are on fire, this number is positive (20 ticks equals 1 second of burning); when you are not burning, it normally rests at `-20`. Change the `Fire` tag value to `-20` (or `0`) to instantly extinguish the flames so you do not burn to death on login. While you are here, check the `Air` Short tag and set it to `300` so you do not immediately drown if you logged out underwater.
4Refill Hunger and Saturation
Having full health will not save you for long if you are starving or unable to regenerate hearts rapidly. Locate the `foodLevel` Int tag and change its value to `20`, which represents ten full hunger drumsticks. Next, find the `foodSaturationLevel` Float tag and set it to `20.0`, and set `foodExhaustionLevel` to `0.0`. High saturation is the hidden mechanic that powers rapid health regeneration in Java Edition, giving you an immediate healing buffer the moment you spawn in.
5Clear Deadly Potion Effects
Look for the List tag that stores your current status ailments: in modern Java Edition (1.20.2 and newer), this tag is named `active_effects`, while in older Java versions and Bedrock Edition it is named `ActiveEffects`. If you expand this list, you will see compound entries containing an `id` (like `minecraft:wither` or `minecraft:poison`) and a `duration`. To cure yourself completely, select the entire `active_effects` (or `ActiveEffects`) List tag and either delete it or delete all the individual compound entries inside it so the list shows 0 items. When the game loads an empty or missing effect list, you spawn completely free of poison, wither, or instant damage.
Tip: If you want to grant yourself a survival buffer instead of just clearing effects, you can leave a beneficial effect like `minecraft:fire_resistance` or `minecraft:resistance` inside the list.
6Save and Replace Your World Files
After verifying your changes to `Health`, `Fire`, `foodLevel`, and `active_effects`, click the Save or Download button in our NBT Editor to export the modified file. Move the newly downloaded `level.dat` or `<uuid>.dat` file back into your Minecraft world folder, overwriting the original file. Remember that in singleplayer Java Edition, `level.dat` overrides the `playerdata` folder on load, so if you edited a `<uuid>.dat` file in singleplayer, make sure you apply the exact same edits to the `Player` section inside `level.dat` as well.
How it works
Minecraft stores all entity and player states using the Named Binary Tag (NBT) format. Every time you pause and save in singleplayer or disconnect from a server, the game serializes your character's exact live memory into a compressed `.dat` file. Because timers like fire duration, potion durations, and suffocation are saved as raw tick counts (where 20 ticks equal 1 real-world second), logging out pauses the countdown at the exact millisecond you left.
In singleplayer Java Edition, the game writes a copy of the host player's NBT data directly inside `level.dat` under the `Data.Player` compound tag, in addition to writing a file inside the `playerdata/` directory. When you open a singleplayer world, Minecraft reads `level.dat` first and uses that data for the host player, completely overwriting whatever is in your individual `playerdata/<uuid>.dat` file. Knowing this hierarchy is essential so your edits are not mysteriously undone when the world loads.
Strict data types govern how NBT tags work. For example, `Health` and `foodSaturationLevel` are IEEE-754 floating-point numbers (`Float`), whereas `Fire` and `Air` are 16-bit integers (`Short`), and `foodLevel` is a 32-bit integer (`Int`). Our NBT Editor preserves these strict data types automatically when you edit a value, ensuring the game engine does not reject or corrupt the player profile upon loading.
Common mistakes
- Editing only the `playerdata/<uuid>.dat` file in a singleplayer Java world while leaving `level.dat` untouched, which causes `level.dat` to overwrite your changes when you load the world.
- Editing the world files while the world is currently open and paused in Minecraft; the game will overwrite your disk changes the moment you unpause or quit.
- Setting `Health` to `0` or a negative number by accident, which forces the game to trigger the death screen immediately upon login.
- Looking for `ActiveEffects` in Java Edition 1.20.2+ where the tag was renamed to lowercase `active_effects` (or vice versa in older versions).
FAQ
What if I logged out directly inside a pool of lava?
Resetting your health and fire ticks gives you a few extra seconds, but you will immediately catch fire again upon logging in. To survive lava, you can also expand the `Pos` list tag (which holds your X, Y, Z coordinates) in our NBT Editor and increase the middle number (the Y coordinate) by 10 or 20 blocks to teleport yourself above the lava pool, or edit your `playerGameType` tag to `1` (Creative mode) temporarily.
Why do I see both level.dat and level.dat_old in my folder?
Minecraft automatically keeps `level.dat_old` as a fallback backup from the previous save tick. You only need to edit and replace `level.dat`, though keeping your own separate folder backup is always recommended.
How do I know which UUID file in the playerdata folder is mine?
If you are the only person who plays on the world, there will only be one `.dat` file in `playerdata`. On a server with multiple files, check the file modification timestamps on your computer right after you log out—the most recently modified `.dat` file belongs to you.
By using our browser-based NBT Editor to reset `Health` to 20, `Fire` to -20, `foodLevel` to 20, and clearing the `active_effects` list in your player data files, you can easily rescue your Minecraft character from an unavoidable login death.