A Mod That Actually Fixes a Design Problem From the Game
The base game gives you a bestiary of bosses, but it is incomplete and ugly by modern standards. You can see which bosses you have defeated, but the icons are tiny and the layout does not update dynamically unless you open the menu and check every single page. People noticed this early. Then someone with time and basic Unity knowledge decided to fix it. I ended up using Journal For Elden Ring Boss Cute after about forty hours on a standard New Game Plus run. The original tracking system was making it impossible to tell which optional bosses I had actually missed. The mod fills that gap and restyles the whole thing with softer colors and larger character portraits that are easier to parse at a glance.
Journal For Elden Ring Boss Cute setup and download
You will find it on Nexus Mods under the Elden Ring section. The current version is stable enough for regular use, but it does require ModEngine 2 and the proper config file in place before it will load. I learned this the hard way during my second install attempt, when the game crashed on the main menu for about ten minutes before I realized the config entry was missing from the engine settings. The download link lives on Nexus Mods. Grab the latest release, extract it into your root game directory alongside the existing ModEngine folder, and make sure your Config.toml has the right path references. It should take roughly three to five minutes if you already have ModEngine set up.
How it works under the hood
The mod hooks into the same boss data structures the base game uses. Rather than rewriting the entire menu system, it overrides the UI rendering layer and replaces the icon assets with hand-drawn versions that look softer and more stylized. The tracking logic remains untouched, which means your progress carries over from the vanilla save if you transition into the mod later. That carryover behavior is the most important detail nobody mentions upfront. The mod does not rewrite defeat flags. It simply reads them. If you have already killed Malenia on a previous save file, the journal will show her portrait as defeated the moment you load that save with the mod active. There is a quirk with the Grafted Scion fight in the Starting Area. The vanilla game marks that boss as defeated through a different trigger path than most other encounters. The first version of the mod I used did not sync that particular flag correctly, leaving the portrait stuck in the uncompleted state even though the damage numbers appeared on screen. The fix was to reload the checkpoint before engaging and trigger the kill again. It sounds unnecessary, but it worked.
Get the Full Details
What you gain and what you lose
The visual upgrade is significant. The new icons take up more screen space, the names are wrapped properly without overlapping, and the boss names use a font that is actually readable instead of the default game typeface. If you frequently pause to check which legendary bosses remain, this saves meaningful time during a long playthrough. The tradeoff is performance. Replacing those assets adds about eight to twelve extra megabytes of texture memory on top of the base game load. On a console build or a PC rig with less than eight gigabytes of VRAM, you will notice frame dips in areas where multiple bosses appear on screen simultaneously, like the Roundtable Hold menu or the boss summary screen after a fight ends. It is manageable on a 12GB card or better, but not invisible on lower tiers. Another thing to accept is that this is strictly a visual tracker. The mod does not add any quest markers, waypoints, or map pins for missed bosses. If you are looking for something that also points you toward where the boss is located, you need a separate tool for that. This one only tells you whether a boss is marked as defeated or not.
There is also the compatibility question. If you are running other UI overhaul mods at the same time, you may run into texture swap conflicts. I had a clash with a color palette mod that adjusted menu transparency, and the two fought over the same render pass until I disabled the transparency adjustment. The journal still loaded, but the background went fully opaque. Not ideal for readability, but stable.
Installation checklist that actually matters
Make sure ModEngine 2 is up to date. An outdated loader version will cause silent failures where the mod appears installed but never activates. Verify that the game executable matches the one the mod expects. If you are on an older patch like 1.06 while the mod assumes 1.15 or newer, the hooks will miss their targets and the journal will fall back to the vanilla version without any warning message. I also recommend keeping a clean save file before your first launch with the mod enabled. It does not corrupt saves on its own, but if you change your mind and remove it mid-save, the boss flags will still be there and the vanilla menu might display the updated icons depending on how the game caches them. That mismatch is annoying to debug after the fact.
Is it worth the effort
If you care about completion and you get frustrated by the sparse vanilla tracker, yes. The mod is lightweight compared to full reskins, it does not alter gameplay balance, and the dev has been reasonably responsive to bug reports over the past year. The main limitation is that it will never be a full replacement for a dedicated quest-helper tool. It is a display improvement layered on top of the existing system. The best approach is to treat it as a cosmetic upgrade with practical value rather than a comprehensive tracker overhaul. Install it alongside whatever other quality of life mods you prefer, keep your expectations realistic about performance, and move on with the rest of your playthrough.
