Tempting Hades

So You Want to Work With Tempting Hades

I ran into Tempting Hades a while back when someone on a modding forum linked it and said it could speed up what we were doing. It turned out to be useful, not a scam, and not as complicated as some of the write-ups made it look. But it does have a few quirks that aren't obvious unless you've actually run it more than once. Tempting Hades is a utility/mod for the game Hades that changes how certain mechanics interact, mainly around the way boons, curses, and the Infernal Armory options behave during runs. Some people use it to test builds that would normally be impossible due to RNG limitations. Others use it as a sandbox because, frankly, vanilla Hades makes some build archetypes unviable by design and it gets tedious. The download itself is straightforward. You grab it from the author's GitHub or the modding Discord, place it in your Hades install directory, and it hooks into the game via Harmony. That's the main thing — it uses Harmony patching, so it doesn't touch the original executable directly. If your game is cracked or modified already, that's where things start getting fragile.

How to Install It Without Breaking Your Save

Here's the part most guides skip. Back up your Saves folder first. I learned this the hard way after a corrupted save cost me about three weeks of progress. The folder is usually at C:\Program Files (x86)\Steam\steamapps\common\Hades\saves. Copy it somewhere else and rename it with a date. You'll thank yourself later. Next, make sure you're running the retail version of Hades. Steam or Epic. GOG seems to cause Harmony patching issues on occasion. If you're on GOG, there's a workaround but it involves manual IL patching and honestly isn't worth the trouble unless you have a legitimate reason to use that version. Once you've placed the Tempting Hades DLLs and config files in the game directory, launch the game normally. You should see a small log file appear in the same directory if everything loaded correctly. If you don't see the log, the patches didn't apply. Check that your Harmony version matches what the mod requires — mismatched Harmony is the single most common failure mode I've seen.

Configuring It For What You Actually Want

The config file is JSON-based and honestly well-organized compared to most mod configs. The default settings will let you force specific boon combinations and adjust curse weights. But the interesting stuff is in the advanced section, which is commented out by default. One setting people miss: you can lock in a specific god's boon precedence order. This matters because Hades picks boon sources based on a hidden weight system that changes depending on your Pact of Punishment level and which boons you've recently collected. If you're trying to build a specific archetype — say, a pure Poseidon build with occasional secondary god boons — you'll want to set divinePreferenceOrder to match your target sequence. Otherwise the game will keep giving you unexpected sources and breaking your build path. Another thing that isn't documented anywhere useful: the curse override settings. You can force specific boons even when they're theoretically blocked by your chosen curse. I ran into this when testing a build that required both Ares and Persephone boons but had a curse that normally prevents that combination. The workaround was enabling the override flag and setting the exception rules manually in the config. Took me about an hour of trial and error because the error messages are not helpful.

Common Problems and What to Do About Them

Crashes on run start. This is usually caused by a conflict with another Harmony-based mod. If you're running multiple mods, disable them one at a time until the crash stops. I once spent two days tracking down a crash that turned out to be caused by a completely unrelated cosmetics mod that also patched the same method. Harmony doesn't handle overlapping patches gracefully. Game runs but changes don't apply. Check your log file. If you see red error lines, read them carefully — they usually tell you exactly which patch failed and why. Most failures are version mismatches. Hades gets updated occasionally and the internal method signatures change, which breaks the patches until the author releases an update. Save corruption. Again, the backup I mentioned earlier will save you. But to minimize risk: don't use Tempting Hades on a save where you're close to completing something important like a completed Codex entry or a specific completion challenge. The modifications change game state in ways that aren't fully reversible. Test on a fresh save first.

Tempting Hades Advanced Techniques

Once you've gotten past the basics, there are a few things that make this tool genuinely powerful. The first is the ability to simulate entire runs with different boon distributions. You can set up a configuration where every run starts with the same curse and you force different boon orderings each time. This is useful for statistically evaluating which builds are actually viable under pressure rather than just theoretically possible. The second advanced technique involves using the tool alongside the game's debug mode. There's a developer console you can enable that exposes a lot of internal state. When combined with Tempting Hades' ability to manipulate boon weights in real time during a run, you can do things like pause mid-run, check the actual boon probabilities, adjust them, and then continue. This is genuinely useful for understanding how the game's systems actually work rather than just how they appear to work. I did this once while trying to figure out why my Ares boons kept getting replaced by Hades boons on higher Pact levels. The debug output showed me that the game's internal scaling was weighting Hades more heavily at certain threshold values, and Tempting Hades let me confirm exactly where those thresholds were. Without that visibility, I would have just assumed it was random variance.

The downside to all of this is that the tool isn't maintained as actively as it used to be. The author posts updates when Hades gets major patches, but there's a lag. If you're running the latest version of the game, check the mod's issue tracker before installing to see if anyone has reported compatibility problems. I've seen at least two cases where a Hades update broke a core patch and the fix took several weeks to arrive. Also worth noting: Tempting Hades only works in single-player. It modifies client-side game logic and doesn't interact with anything server-side, which is mostly a non-issue since Hades is single-player anyway. But if you're somehow trying to use it in a multiplayer context through some unofficial mod, it won't work and will probably crash the game harder than normal. Overall, it's a solid tool for what it does. It won't make the game easier in a traditional sense, but it gives you enough control to test things that would otherwise take dozens of runs to evaluate. Just back up your saves, keep an eye on the version compatibility, and don't expect the config system to be perfectly intuitive on day one. It's functional, not elegant.