1.0.5

One fix, but a big one if it affected you: Alex's Caves Continued now works with Citadel installed.

Playing with Citadel no longer crashes the game

If you had Citadel in your mods folder — on its own, or because something else needs it, such as Rats or Alex's Mobs — the game died during startup, before it ever reached the menu. Installed together, the two mods were unplayable.

The reason is a piece of history. Alex's Caves originally needed Citadel to run, and the continuation carries its own private copy of the parts it uses so you no longer have to install Citadel separately. That copy has always been kept under our own name, so it cannot collide with the real Citadel — except in one place we had missed. Both copies teach the game the same handful of new abilities, under the same names, and the game cannot hold two things with the same name in the same place. It refused to start rather than pick one.

Everything our copy adds is now named distinctly, so the two can sit side by side. Nothing about how the mod plays has changed.

…and a second problem that was hiding behind the first one

Once the startup crash was out of the way, a second clash appeared: our copy and the real Citadel were both writing to the same slot in your save file, and each kept finding the other's data there. On a running world this went wrong many times a second. It never had a chance to show up before, because the game had never got far enough to load a world with both mods installed.

That slot is now ours alone, and Citadel keeps its own. Existing worlds are fine — nothing needs to be reset, and no world data is lost.

What we tested

The exact combination from the crash report — Alex's Caves Continued, Citadel and Rats together on Forge — now starts up, loads a world and plays with no errors at all. Both the startup crash and the save-file clash are gone.

If you play with any other mod that uses Citadel, this release is the one you want.