Just tried using this and it launches the Borderlands Pre-Sequel. Maybe there is something else I need to do? I downloaded the mod manager as well but it still starts up the pre-sequel. So I don't know if that means any of the mods are working at not.
Just a couple of notes for anyone who might want to use this:
1) BL2 still has to be hex-edited in order to use any "traditional" mods of the sort hosted on here. Just downloading mods isn't enough. You'll have to use BLCMM or Hex Multitool to do so, before you can use mods (Hex Multitool is required for the EGS version, as of June 15, 2020 -- BLCMM can still hex-edit the Steam version though). See http://borderlandsmodding.com/running-mods/
2) Mods on both EGS and Steam *need* to be merged into a single file, and the tool to do that is still BLCMM. If you don't use BLCMM to merge all your mods together, bits of mods will end up overwriting each other, and you'll end up with mods that only partially work. So even if you're using Vortex to download BL2 mods, you *still* need to import them into your single patch file using BLCMM, and only ever `exec` the single file from the console. See http://borderlandsmodding.com/running-mods/#managing-mods
2a) To that end, *only* the file you `exec` from the console needs to be present in the BL2 `Binaries` dir. It won't hurt anything to store the mods individually in there too, but they won't actually do any good in there.
3) The default file extension for exporting mods from BLCMM is `.blcm`, not `.txt`, though some mod authors still use `.txt`. You might want to update your extension here to support either of those. (BL2 itself doesn't care at all about the extension that you use in the `exec`.)
While the default file extension for exporting mods from BLCMM is "blcm", the most common file extension in Nexus is "txt". However, I will take a look at adding blcm to the extension or just taking the file extension test off completely, since you have to use BLCMM anyway. I was assuming people knew that. Thank you for your post.
4 comments
--- ./bl2//index.js.bak 2020-10-22 04:06:02.878032952 +0200
+++ ./bl2//index.js 2020-10-22 04:12:41.542807835 +0200
@@ -1,7 +1,9 @@
const path = require('path');
const { fs, log, util } = require('vortex-api');
-const EXEC_PATH = path.join('win32', 'Launcher.exe');
+const EXEC_PATH = process.platform == 'linux'
+ ? 'Borderlands2'
+ : path.join('win32', 'Launcher.exe');
const GAME_ID = 'borderlands2';
// All BL2 mods will be .txt files
1) BL2 still has to be hex-edited in order to use any "traditional" mods of the sort hosted on here. Just downloading mods isn't enough. You'll have to use BLCMM or Hex Multitool to do so, before you can use mods (Hex Multitool is required for the EGS version, as of June 15, 2020 -- BLCMM can still hex-edit the Steam version though). See http://borderlandsmodding.com/running-mods/
2) Mods on both EGS and Steam *need* to be merged into a single file, and the tool to do that is still BLCMM. If you don't use BLCMM to merge all your mods together, bits of mods will end up overwriting each other, and you'll end up with mods that only partially work. So even if you're using Vortex to download BL2 mods, you *still* need to import them into your single patch file using BLCMM, and only ever `exec` the single file from the console. See http://borderlandsmodding.com/running-mods/#managing-mods
2a) To that end, *only* the file you `exec` from the console needs to be present in the BL2 `Binaries` dir. It won't hurt anything to store the mods individually in there too, but they won't actually do any good in there.
3) The default file extension for exporting mods from BLCMM is `.blcm`, not `.txt`, though some mod authors still use `.txt`. You might want to update your extension here to support either of those. (BL2 itself doesn't care at all about the extension that you use in the `exec`.)