Please disclose if any significant portion of your mod was created using AI tools by adding the 'AI Generated' category. Failing to do so may result in the mod being removed from Thunderstore.
Niflheim NoHeatWave
Turns the Ashlands heat shimmer down by any amount, including off. Client side with no server sync, so unlike BreatheEasy it will not get you kicked from a server that does not have it.
| Last updated | 23 minutes ago |
| Total downloads | 1 |
| Total rating | 0 |
| Categories | |
| Dependency string | NifusionDotDev-Niflheim_NoHeatWave-1.1.0 |
| Dependants | 0 other packages depend on this package |
README
NoHeatWave
Turns the Ashlands heat shimmer down, by any amount you like, including all the way off.
One setting, HeatWaveStrength, from 0.0 to 1.0:
| Value | What you see |
|---|---|
0.0 |
No shimmer at all. The default. |
0.25 |
A hint of it. Enough to read as heat, not enough to fight. |
0.5 |
Half. |
1.0 |
Vanilla, untouched. |
It takes effect the moment you change it. No restart, no reload, no re-entering the biome.
Why this exists instead of just using BreatheEasy
BreatheEasy removes the heat distortion too, along with a lot of other things, but it marks itself as required for everyone. If you install it and the server does not have it, the server refuses your connection.
This mod registers no network behaviour of any kind. There is no NetworkCompatibility
attribute, no ServerSync, no RPC, no config pushed down from the host. Nothing identifies it to
the server, so there is nothing for the server to object to. Install it on your client, join any
server, including one you do not administer, and nothing changes except what your own screen
draws.
That is the entire point of the mod. If you can already run BreatheEasy, you do not need this.
It is a visual change only
The heat shimmer is a full-screen post-process pass. Scaling it changes nothing about damage, temperature, stamina, status effects, or anything else the game simulates. You are not getting an advantage, you are getting a readable screen.
The Ashlands still kills you exactly as fast.
Config
BepInEx/config/niflheim.noheatwave.cfg
| Setting | Default | Range | Meaning |
|---|---|---|---|
HeatWaveStrength |
0.0 |
0.0 - 1.0 |
How much shimmer to keep. |
Editable in-game with Configuration Manager if you have it, otherwise edit the file.
How it works
Valheim draws the shimmer in HeatDistortImageEffect.OnRenderImage, which pushes three fields
into a shader material and blits the result over your frame. The mod takes those three fields,
multiplies them by your setting on the way in, and puts them back on the way out.
At 0.0 the pass is skipped outright and the frame is copied straight through instead. That
matters: the effect's material tints the image through its own colour, so zeroing the three
numbers is not the same as not running it at all. Only skipping it gives you a clean frame.
The restore is a Harmony finalizer rather than a postfix, so the original values go back even if the render throws. If they did not, the scaling would compound every frame and the effect would fade to nothing within about a second, which looks like a fix and is actually a bug.
Install
Needs BepInEx. No other dependencies, and deliberately so.
Drop NoHeatWave.dll in BepInEx/plugins/, or install through a mod manager.
Multiplayer
Client side. Install it or do not, per player, on any server. Other players see their own Ashlands exactly as they configured it.
Status
Works. The 0.0 path has had the most use by far, since that is what it was written for; the
partial values in between are newer.
Credits
Part of Niflheim, a set of single-issue Valheim modlets by NifusionDotDev. Each one does one thing and is installed on its own; none of them depend on the others.
Written by a human doing his best to enjoy his hobby. Reviewed and documented with AI help, which is why the README is longer than the mod is.