FireWasFired

Gives the fire overlay the pink slip (when you have fire resistance active).

173 Downloads

forgeneoforgecursedutility

About this Mod

Summary

When you (the player) are on fire, an overlay is rendered that takes up an enormous portion of the screen, regardless of whether its helpful (whether you have fire resistance). This mod simply disables the fire overlay when you have fire resistance active.

Side

Client-side.

It probably won't crash the server if installed server-side, but it definitely won't do anything.

Configuration

None. Remove the mod to disable.

Updates / Other loaders

Most likely none. There's better options for other versions and other loaders.

It's also like 3 lines of code (not incl. boilerplate) so I'm probably going to forget this exists when I'm done playing on (Neo)Forge @ 1.20.1.

Available Versions

FireWasFired 1.0.0release

MC 1.20.1forge, neoforge

October 18, 2024

How to Install FireWasFired on Your Server

Order Server

Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).

Set forge Loader

In the panel under "Egg", select the forge loader and matching Minecraft version (1.20.1).

Install Mod

Open the mod browser in the dashboard and search for "FireWasFired". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.

Compatibility

Mod Loaders

forgeneoforge

Minecraft Versions

1.20.1

Server-side

✗ Unsupported

Recommended RAM

4 GB(min. 3 GB)

Frequently Asked Questions

FireWasFired server crashes on startup – what to do?

Most common cause: wrong forge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.20.1). You can switch loaders with one click in the panel.

Is FireWasFired compatible with forge and neoforge?

FireWasFired officially supports forge, neoforge for Minecraft 1.20.1. The Mado dashboard automatically detects incompatible loader combinations.

Server lagging with FireWasFired – how to optimize performance?

Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if FireWasFired consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.