Tutorial: Installation

Part 1: Console Access

Enabling the Console

The console can be enabled in the willowinput.ini in:

• documents/my games/'X'/willowgame/config/ for Windows.
• library/application support/'X'/willowgame/config/ for Mac.
• share/aspyr-media/'X'/willowgame/config/ for Linux.

The 'X' must be replaced by either borderlands 2 or borderlands the pre-sequel, depending on which game you want to work on.

Once you find the file, use a text editor to access its contents.

• Use Edit>Find or Ctrl+F or Cmd+F and find [Engine.Console].
• Under this, you will see ConsoleKey= and TypeKey=.

You can set these keys to any key of your choosing, however it's best to do ConsoleKey=Tilde and TypeKey=Backslash, since these keys are generally not used for anything else.

On the QWERTY (Standard) Keyboard Tilde is the key left of 1 and above TAB, Backlash is the key above Enter, below 'Return' and right of }].

Once you've set the keys, while in-game pressing the ConsoleKey will open the console with a log at the top of the screen, and pressing the TypeKey will open the console with just a command line at the bottom of the screen.

Uses and Limitations

At this point, the console can be used in a very limited way. Here are some of the commands that can be used:

• Shot
• TiledShot
• Stat FPS
• ToggleHud
• Quit

If you try to use a command that doesn't exist, or a command you don't have access to, it will simply type into the game chat instead of running them.

However, to patch the game we need access to Set command and some other extra permissions.

Part 2: Patching Game

From this moment on, BORDERLANDSGAME will be used to mean the directory your game files
(either borderlands 2 or borderlandspresequel)

To access BORDERLANDSGAME:

1. Go to your Steam Library
2. Right-Click on the game
3. Click Properties at the bottom of the list
4. Go to the Local Files tab
5. Click Browse Local Files

Patching Methods

All of these methods involve changing the non-writable memory of the game's executable so that the console is unrestricted. They all use different methods to change specific values, some can work while the game is running temporarily, others work by editing the executable itself.

Hex Editing

This method uses a hex editor to permanently edit the executable so that the console is fully unlocked.
Should work for all platforms, you may need a different hex editor if on non-windows.

1. Go to BORDERLANDSGAME/Binaries/Win32.
2. BACK UP Borderlands2.exe or BorderlandsPreSequel.exe.
3. Install a Hex Editor.
4. Open Borderlands2.exe or BorderlandsPreSequel.exe in the Hex Editor.
5. Click the dropdown menu Edit and go to Find and Replace
   (Or use Ctrl+H or Cmd+H)
6. Set it to Hex Values.
7. Replace 83 C4 0C 85 C0 75 1A 6A with 83 C4 0C 85 FF 75 1A 6A.
8. Replace 73 00 61 00 79 00 with 00 00 00 00 00 00.
9. Save changes.

For Windows

The Patcher

This method uses the Patcher
Which will automatically hex edit the executable and set your ConsoleKey (as already done in Part 1)
Run the Patcher executable and follow any prompts, there should be help information given.

Cheat Engine (Non-Permanent)

If you are on Windows, you can still enable all of the blocked commands using Cheat Engine Scripts.

1. Open UnlockConsole.CT in Cheat Engine
2. Once either Borderlands 2 or Borderlands: The Pre-Sequel is running.
3. Click the monitor icon in the top left in Cheat Engine
4. Select Borderlands2.exe or BorderlandsPreSequel.exe in the process list
5. Click Open
6. Check Disable Console Say and Unlock Set Utility.
7. Close Cheat Engine

This must be repeated every time you use mods, so it is non-permanent.

Downloads for Cheat Engine can be found Here
A download without installer is available for Cheat Engine 6.6

For Mac & Linux

Follow this Method

Part 3: File Execution

Exec Command

Place any mods you want to use inside the BORDERLANDSGAME/binaries.

Launch the game and once you are at the main menu (past any loading screens) run Exec *.
Where * is the filename of each file you installed to BORDERLANDSGAME/binaries.

The extension must also be included (usually .txt, sometimes there is no extension)
You will need to do this every time you launch the game.

Organising Files

Since you must run an exec command on every file, it is a good idea to organise the files in a way that allows the formation of a master file; A file that will execute every other file so you only need to execute one.

This master file can be created by:

• Pasting the contents of each file onto the end of one
  (you now don't need any of the other files)
  OR
• Writing a file that contains (for each on a separate line) Exec * for each file
  (Doesn't handle files with names containing spaces or graves)
  OR
• Using UCP Filter Tool to customise your patch install and install mods through a unified graphical user interface.
  (Not entirely integrated for Presequel, Requires Java Runtime Environment)
  OR
• Using ExecLoader.bat to construct Autorun
  (Must be stored in a subfolder of Binaries, only for Windows)

UCP Filter Tool

To use UCP Filter Tool:
Watch this Demonstration by the tool's creator LightChaosman

1. Download and place FilterTool.jar and Patch.txt in BORDERLANDSGAME/binaries
2. Open FilterTool.jar with Java Runtime Environment
3. Check/uncheck features according to your preferences
4. Add mods through Developer tools>Add single mod, this will open a folder browser, select a mod.
   OR
   Add mods through Developer tools>Import mods folder, a mods folder will be created in Binaries, put mods in this folder then use the button again.
5. If you wish, use File>Change default patch to change the master file.
6. Press File>Save patch and the master file will be updated.

ExecLoader

To use ExecLoader.bat:

1. Download the file
2. Create a new folder inside BORDERLANDSGAME/Binaries
3. Put ExecLoader.bat inside it
4. Run ExecLoader.bat
   This will create Buffer and Data folders.
5. Place the files you want to install inside Data
6. Run ExecLoader.bat
   This will create Autorun as well as renamed copies of the files in Data in Binaries