Because BLCMM's internal hex-editor is often what triggers the "invalid" error, the most effective solution is to using external tools. 1. Use the Borderlands Hex Multitool
If BLCMM accepts your path but throws an invalid error specifically when trying to apply the text-mod hex edits, you need an external tool to decouple the tasks. Keep BLCMM closed for a moment.
BLCMM requires files to be in ANSI or UTF-8 format. If you edited the mod, it might have been saved in a format BLCMM dislikes. Open the .txt mod file in Notepad++. Click on the "Encoding" tab. Select "Convert to UTF-8". Save and try opening in BLCMM again. 4. Use "Import" Instead of "Open" blcmm invalid file selected
BLCMM needs to target the actual game engine, not the launcher. Borderlands 2 Borderlands2.exe located in ...\Binaries\Win32\ The Pre-Sequel: BorderlandsPreSequel.exe in its respective 4. Verify Java Installation
Follow these troubleshooting steps in order to resolve the issue. 1. Extract the Mod Files (Stop Opening Zips!) Most modders distribute their mods in .zip or .rar files. BLCMM cannot read compressed archives. Because BLCMM's internal hex-editor is often what triggers
Go to File -> Open -> Select the mod, go to Setup -> Set File Path .
If you are trying to mod Borderlands 2 or Borderlands: The Pre-Sequel , you have likely encountered the Borderlands Mod Manager (BLCMM). It is the gold standard tool for managing hex edits and executing .txt or .blcm mod files. Keep BLCMM closed for a moment
: BLCMM often looks for the word "steam" in the file path to validate it. If your game is installed elsewhere (e.g., a non-Steam folder or the Epic Games Store), creating a folder named steam inside your game directory and moving the game files into it can often trick the manager into accepting the path.
To prevent the "invalid file selected" error from occurring in the first place, adopt these best practices when handling mod files:
: Available on the OpenBLCMM GitHub page or Nexus Mods .