Core Keeper temporarily disables mod save sharing in security patch 1.3.0.7

Core Keeper’s PC update 1.3.0.7 temporarily turns off the save-sharing feature used by mods. Pugstorm released the November 2 security patch after identifying a vulnerability in Brotli, the library used to compress save data, while stating that it had no indication of attacks targeting Core Keeper players.

The developer’s notice describes a precautionary feature suspension. Restoring it depends on a fix in the Unity engine, and the announcement supplies no return date. It does not instruct players to delete existing worlds or identify a confirmed theft of accounts or saves.

Save sharing is one part of the mod system

The single listed change is specifically marked for PC and concerns sharing save files through mods. The notice does not announce the end of mod support, removal of ordinary cooperative play or deletion of locally stored progress. A mod depending on that sharing capability may consequently behave differently even though other parts of the game continue to work.

The distinction has a practical history. Core Keeper’s official mod.io guidelines allow community maps to be distributed as world files when they provide useful content. They also say the service should not be used merely as personal backup storage. Sharing a playable world with others and preserving a private copy of progress are therefore different activities.

The older guidelines establish the intended use of world sharing; they are not confirmation that the temporarily disabled feature has been restored. The dated security notice is the relevant update to its availability.

Check the installation route when a mod stops working

The current installation documentation distinguishes Workshop subscriptions, mod.io subscriptions and manually installed packages. Subscribed mods update while the game is closed, whereas manually installed mods require manual updates. Some packages also depend on other mods listed in their descriptions.

That gives players a concrete way to separate two questions: whether their installed modification is current, and whether it relies on the game feature that has deliberately been switched off. Updating an outdated package can address its own compatibility problems; it cannot by itself establish that the engine-dependent sharing feature has returned.

The mod guidelines direct compatibility and maintenance questions about user-created content to its author. A useful report should identify the game version, the affected mod and the action that fails. “The world will not download through this mod” is more specific than treating every problem after the patch as corrupted progress.