(Classic Edition) Community Patch - Base

witcher-3 — Mods & Enhancements

This patch serves as a foundational framework that creates a unified, conflict-free base for other mods to build upon, specifically for the Classic Edition (pre-1.30) of The Witcher 3. It introduces new 'hubs' (virtual folders) that modders can reference in their own mods, allowing multiple mods to share common files (like textures or scripts) without overwriting each other. Players install this to ensure that popular mods like 'Friendly HUD' or 'Immersive Cam' work together seamlessly, reducing the need for manual script merging and preventing random crashes from file conflicts.

📦 Full mod page on discovermods

Downloads, ratings, compatibility info, installation guides, and user reviews.

View on discovermods →

Syntax

Utilities

Example

Downloads: 586,938 | Endorsements: 19,748

💡 Notes

By rmemr and wghost81 | v1.0 | 19,748 endorsements

🎯 Tips & Tricks

Install this patch as the very first mod in your load order, before any other mod, to establish the base structure.

In Vortex, set the mod's 'Deploy Priority' to 1 (lowest number). In Mod Organizer 2, place it at the top of the left pane. This ensures all other mods that depend on its hubs (like 'modShared' or 'modBase') can find the necessary files. If you install it later, you'll need to re-deploy all mods to refresh the virtual file system.

Use the included 'Community Patch - Base' console command to verify the hubs are active.

Open the console (~) and type 'CPBase_VerifyHubs'. If you see 'Hub: modShared - OK' and 'Hub: modBase - OK', the patch is working. If not, you have a load order issue and need to reinstall the patch and ensure no other mod is overwriting its 'content/texture.cache' file.

When merging scripts with 'Script Merger', always select 'Community Patch - Base' as the 'BASE' file for any script that appears in multiple mods.

This is because the patch's scripts are designed to be the most minimal and compatible. For example, if you have 'Friendly HUD' and 'Colored Map Markers' both modifying 'mapMenu.ws', set the Community Patch's version as the base, then apply the other mods' changes as patches. This reduces conflicts and keeps the game stable.

🔧 Troubleshooting

Game crashes on startup with 'Error [mod_community_patch_base] content/scripts/def_metadata.ws - Could not open file' when using 'Unification Patch' (for 1.31 content on 1.30).

The Unification Patch is incompatible with Classic Edition. Uninstall it and instead use the 'Classic Edition - Unification Patch' from the same author, which is designed to work with this base. Alternatively, downgrade your game to 1.30 and use the standard patch. Never mix the two.

Script Merger shows a conflict between 'Community Patch - Base' and 'Enhanced Targeting' because both modify 'playerInput.ws'.

Open Script Merger, and for the 'playerInput.ws' file, choose the version from 'Community Patch - Base' as the base. Then, manually add the Enhanced Targeting changes via a custom patch. This is a known issue; the Enhanced Targeting author has a dedicated patch for this on their Nexus page, download 'Enhanced Targeting - CP Base Compatible' and install it after both.

⚠️ Common Mistakes

[object Object]
[object Object]

👍 Pros

19,748 endorsements
586,938 downloads
Category: Utilities

👎 Cons

Requires mod manager installation
May conflict with similar mods

← Back to all witcher-3 Mods & Enhancements