How the Easy Elden Ring Boss Logbook Actually Works
It's a simple mod that tracks every boss you kill and logs it in a neat little interface. You open it mid-run, see what you've beaten, what's still available, and it marks off locations on a mini-map. I've used it across multiple playthroughs because manually remembering which demigods you've tackled while juggling builds and weapon switches gets exhausting pretty fast. Download it from Nexus Mods. It's called Easy Elden Ring Boss Logbook and it's made by a user called TONKATSU. Grab the latest version compatible with your game build — Elden Ring patch updates break these things occasionally. The current version supports patch 1.12 as of my last check. Extract the contents into your game folder. The path is straightforward: put the .dll file and the folder structure where your elden_ring.exe lives. If you have Steam, that's typically C:\Program Files (x86)\Steam\steamapps\common\Elden Ring. Do not put the files in the wrong subfolder. I learned that one the hard way when my logbook appeared but tracked absolutely nothing because the files were nested one layer too deep.
Launch the game. There's no separate launcher or config window. You press a key — default is I — and the overlay appears. That's it. The interface shows a list of bosses with icons next to them. Defeated ones get a checkmark. Undiscovered bosses stay grayed out. Defeated but currently inaccessible ones show a small warning symbol. The map tab overlays boss locations onto the standard Roundtable Hold map, which helps you plan routes without opening your actual inventory and getting distracted.
What the Logbook Gets Right
The main value is tracking progress across NG+ cycles. When you start New Game Plus, most of your boss data carries over automatically. You can see at a glance which new bosses exist in the current cycle versus which ones you already killed in previous runs. That saves you from accidentally skipping something or wasting hours searching for a boss you've already beaten elsewhere in the world. The category filters are useful too. You can sort by type — Demigod, Shardbearer, Divine Beast, Spirit Ascension, etc. I use the Demigod filter primarily when speedrunning any% splits because I only need to confirm those fights, not every minor optional boss in the Lands Between.
Get the Full Details
Where It Falls Apart
There are real limitations worth knowing before you commit. The first is auto-detection reliability. About 80-85% of bosses are tracked correctly after you defeat them. The rest require manual confirmation through an in-menu button press. If a boss doesn't register, open the logbook, go to settings, and there's a manual entry option. Select the boss from the list. It's not a huge deal but it's annoying when it happens mid-playthrough and you're trying to maintain momentum. The second issue is with certain NPC summons and spirit ash assists. The logbook doesn't differentiate between solo kills and assists. A boss defeated with a summoned spirit still counts as defeated. This matters if you're doing any kind of challenge runs or solo attempts because the log won't reflect that truth. Third, multiplayer co-op sessions sometimes cause sync issues. If you're in someone else's world and they defeat a boss you haven't seen, your logbook might not update until you manually check the settings panel. I've seen this happen most often with Malenia and Morgott — high-profile bosses that other players tend to hit early. It usually resolves itself within a minute of loading back into your own world, but it's frustrating if you're trying to verify completion status for some reason.
Settings You Should Actually Touch
The default keybind is I for opening the logbook and O for the map overlay. I changed mine because I play on a console controller emulation setup and those keys conflict with my inventory. Going into settings and remapping is straightforward. I recommend moving the logbook open key to something less likely to get triggered accidentally during combat. I use F3 myself. The notification sound option is enabled by default. I turned it off after three playthroughs because every boss kill triggers a ding that gets old fast. You can disable it entirely in settings. There's an auto-save feature for your progress data. Keep it on. I disabled it once out of curiosity and lost two hours of boss tracking data after a crash. It saves to a JSON file in the game directory, so you can back it up manually if you want extra safety.
Common Problems and Fixes
If the logbook doesn't appear at all, check your installation path first. Most people mess this up. Make sure the dll is in the root game directory, not in a Data or StreamingAssets subfolder. Verify the game version matches the mod version on Nexus. If bosses aren't registering after defeat, reload the area. Sometimes the trigger fires but the save event gets interrupted by the game's own checkpoint system. Walking back to the boss arena entrance and back usually forces the update. If the map overlay is blank or showing wrong locations, this is a known issue with certain DLC areas. The base game bosses track fine but Elden Ring's DLC regions sometimes need manual coordinate correction in the mod's config file. Open the EasyBossLogbook folder in your game directory and there's a config.json. You can edit boss coordinates there but it's tedious. Easier to just wait for a patch.
Should You Use It
It's helpful for completionists and people juggling multiple playthroughs simultaneously. It's unnecessary if you're just playing through casually and don't mind tracking your own progress. The mod is lightweight — I've noticed zero performance impact on my system. No FPS drops, no crashes beyond the occasional rare conflict with other HUD mods. If you run into issues, check the Nexus comments section. The modder is responsive but updates are sporadic. Last update was about six weeks ago when I checked. Nothing major broken, just incremental improvements and bug fixes for newer patches.
