Breachingcharge Fix

Breachingcharge Compatibility Fix This addon provides targeted compatibility fixes for Breachingcharge on DayZ 1.30. It updates the script paths, adapts inventory weight handling and restores the original mod's calls to the current vanilla combination-lock functions. The charge keeps its configured base weight while its quantity is used for the detonation countdown. Keep the original Breachingcharge mod and CF installed. Load this fix after them on both the server and connecting clients. What is included? Updates the world and mission script paths to use forward slashes. Adapts charge weight handling to DayZ 1.30, keeping the countdown quantity from increasing inventory weight. Connects the original calls for unlocking and removing vanilla combination locks to the current game functions. Installation for players Click Subscribe on this Workshop page, then subscribe to Breachingcharge and CF. All three are required. Wait until Steam has finished downloading the mods. Start DayZ through its launcher. Choose a server that uses this fix and load its required mods when prompted. Keep CF, Breachingcharge and this fix enabled, along with the server's other required mods. Join the server. After a mod update, let Steam finish downloading and restart DayZ before reconnecting. Installation for server owners Stop your server. Install the three required mods: CF, the original Breachingcharge mod and this fix. Use your hosting panel's Workshop installer, or copy each complete mod folder into your server directory, next to DayZServer_x64.exe. Keep the fix in its own folder and leave the original Breachingcharge files unchanged. Enable them in the regular mod list. In your hosting panel or startup script, use this order: CF, Breachingcharge, this fix. Keep the server's other mods in the list. Every connecting player also needs this fix, so adding it only to -serverMod is not enough. Check signature keys. If your server checks mod signatures, use signed builds and copy their matching public .bikey files into the server's keys folder. This fix also needs a valid signature and matching server key; an unsigned development build will not pass this check. Start the server and connect. Make sure the server and players have the same versions of the three mods enabled. Example startup argument: "-mod=@CF;@Breachingcharge;@HDSN_BreachingCharge_PathFix" The folder names in this example must match the folders on your server. If you already have a -mod argument, add the missing entries to that list, separated by semicolons. This belongs in the server launch command or your host's mod settings, not in serverDZ.cfg. RaidSchedule compatibility This fix also works with RaidSchedule and has been tested with RaidSchedule - New and Improved. RaidSchedule is optional. If you use it, keep your existing RaidSchedule setup, raid-time settings and its required compatibility addons installed. Follow RaidSchedule's own installation instructions for those components. For server owners and modders Requires Breachingcharge and CF. Install this fix on the server and every connecting client through the regular -mod list. Load order: CF, Breachingcharge, this compatibility fix. Existing charge classnames, countdown settings and raid configuration remain in use. Check for overlapping changes before combining this addon with other Breachingcharge compatibility patches. Original mod and repacking Original mod: Breachingcharge by Handsome Nipple and Deadcraft. This addon contains its own compatibility configuration and code. The original scripts, models, textures and other assets remain in the original Breachingcharge mod, which must be installed separately. The original authors' usage and repacking rules still apply. Repacking this compatibility fix is allowed. You may include it in your own server mod pack without asking for additional permission. This permission applies only to the configuration and compatibility code provided by this fix. The original Breachingcharge mod and other dependencies remain subject to their authors' own rules. Contact and support Questions or bug reports? Contact me on Discord: don040.