Choose the task and finish the next step
Workshop subscription, package activation and removal are separate steps. Check what was actually installed, and follow Pocketpair's guidance about remaining mod files when returning to an unmodified game.
What the official announcement confirms
- Back up save data before removing old mods or changing the game version.
- Pocketpair says old files and loaders can still load after a manager marks them disabled; remove or relocate the actual files as its guidance describes.
- Verify Steam game files, confirm an unmodded launch, then reinstall updated mods one at a time.
- A save that depends on added mod content may fail after that content is removed; keep a backup of the world and the corresponding loadout.
Follow the matching installation path
- Back up the save and record the clean game revision before changing a loadout.
- Identify the actual format, platform and client/server side from the author release.
- Install the required framework first, verify its current log, then add one mod and check the intended result.
- If it fails, compare with the clean baseline, keep the draft/test evidence and remove the tracked files deliberately.
Official package facts
Pocketpair documents Windows Steam and Windows dedicated servers for its official loader. It supports Paks, Lua, LogicMods, UE4SS and PalSchema package types. PackageName identifies an enabled package; Version changes trigger deployment, and server rules require IsServer. These facts do not certify an arbitrary mod or another platform.
Evidence boundary
The factual tables preserve the stated source snapshot. Source-specific recommendations and mechanics have not been independently reproduced in the current game. Exact gameplay rule gaps remain in the coverage notes rather than being filled with invented quantities.