Where Does CrossCode Store Mods?
CrossCode mods load through CCLoader from a mods folder in the game directory. The loader patches the HTML5 client at startup.
Last updated
CrossCode runs on an HTML5 client, so its loader patches the game at startup from a mods folder in the game directory. New game plus tweaks, combat options, and interface improvements fill a dedicated scene. Each mod is a folder the loader reads in order.
The loader console is the debugging home: it lists mounted mods on every start, so silent failures show there first. Keep the mod set small and curated, since HTML5 patching makes conflicts subtler than native code. Save backups before quest mod experiments.
Where CrossCode stores this, by platform
[Steam]\steamapps\common\CrossCode\mods
One folder per mod here loaded by CCLoader at startup. Read the loader console to verify mounts. Back up saves before quest experiments.
Frequently asked questions
No mods load after an update. What happened?
Update CCLoader first, then each mod. Game patches move the client files mods hook, so everything fails together until the loader updates. The loader console lists mounted mods.
Is it safe to remove mods mid playthrough?
Back up the save tree first. Quest and combat mods can strand progress when removed, while interface tweaks uninstall cleanly. Test newcomers on a spare Lea.
Notice an outdated path? Let us know.