ModTek vs xOBSE

ModTek is a free mod loader for HBS’s BattleTech PC game. It loads mods at game startup when they use the mod.json format, allowing modders to package self-contained changes without overwriting game files. It resolves dependencies and controls load order without requiring edits to VersionManifest.csv. The project says newer versions include DLC support not present in BattleTech’s built-in 1.7 loader. It supports BattleTech installations from Steam and GOG on Windows, Linux, and macOS. Installation uses a downloadable ZIP extracted into the game’s installation folder; the instructions warn that the game should be outside Program Files because Windows UAC protection can interfere. Version 3 and later use UnityDoorstop to load ModTek without modifying game files. The repository documents JSON and DLL mods, advanced JSON merging, manifest manipulation, and HarmonyX support. The project is licensed under LGPL-2.1. Linux instructions describe a system-wide ASLR change as an obsolete, insecure workaround and provide an environment-variable fix instead.

xOBSE is a community-maintained fork of the Oblivion Script Extender, a tool that expands scripting capabilities for modders of The Elder Scrolls IV: Oblivion. The project is free and open source, with releases and source code available through its public GitHub repository. The latest listed release is xOBSE 22.13. Steam and GOG versions are supported, with GOG preferred; Direct2Drive is not supported. The README identifies English official patch v1.2.0.416 as supported and warns that localized versions with different executables or patches may not work. For Steam Proton on Linux, instructions call for renaming obse_loader.exe to OblivionLauncher.exe and launching through Steam. xOBSE does not change the game executable files on disk. It aims to preserve compatibility with existing mods and plugins, though beta releases can introduce errors. Mod Organizer 2 users need additional setup instructions. The repository also includes an example plugin project; plugin developers defining commands need an opcode range allocated by the maintainers.