Clyde

Clyde is a graphical user interface (GUI) for apocalyptech's command line based bl3-cli-saveedit app, an app for manipulating Borderlands 3 save files. As a front end, Clyde is really just a convenience tool. It doesn't actually do anything itself – you must have bl3-cli-saveedit in order to modify your save files.

You can obtain bl3-cli-saveedit from Github or pypi.org. Follow the instructions at either place to install it. It's written in Python, so you will also need Python if you don't already have it. If you don't have Python, it seems to be easier to deal with if you install it just under your user (as opposed to for all users), and make sure you find the spot to have it add itself to your path.

In addition to formatting the command line parameters for bl3-cli-saveedit, Clyde automates the task of making backups of save files for you. You can also choose at any time to copy save files to a location of your choosing, for example to a thumb drive or network share.

Here's the standard disclaimer:

This software is provided 'as-is', without any express or implied warranty.

In no event will the author be held liable for any damages arising from

the use of this software.

Here's the thing. You are fiddling with your game save files. You are ultimately responsible for what happens with them. Although Clyde has been thoroughly tested, bizarre things can happen at any time. You should build your own level of trust using the program, making your own backup copies of your save files frequently enough that you won't lose that hard-farmed beautiful weapon you've acquired or erase the fiercest battle of all time against a badass. I know I do.

Prerequisites

Clyde was built with NET framework 4. 8. It's highly likely that you already have it. Download from Microsoft if not.

bl3-cli-saveedit – the package install creates executables for the scripts. Clyde needs the executable versions.

Python – consult bl3-cli-saveedit documentation for version.

Clyde now has an installer. The installer needs elevated privileges in order to create desktop and start menu shortcuts, as well as writing uninstall information.

If you prefer to do a manual install, download the loose files and follow the instructions below in either the Quickstart or Installation sections.

If you're doing an update, all you really need to do is download the loose files (in the zip) and drop them in your Clyde directory, but the installer is capable of performing an update as well.

The installer does not install Python or the bl3-cli-saveedit package; you will still need to install those. I recommend installing Python under just your user as opposed to all users, and make sure you find and tick the checkbox for 'add python to path'.

If the installer is able to find the executable versions of the Python scripts, it will copy them to your Save Edit directory for you.

Quickstart

Install Python and bl3-cli-saveedit.

Create directories for Clyde, backup files, and saveedit files.

Drop the Clyde executable into the Clyde directory.

Copy the saveedit executables from the Python Scripts directory to the savedit directory you created.

Launch Clyde.

Choose Setup tab.

Supply the locations for the backup files, saveedit executables, and game save files.

Add save files and nicknames to Clyde if they weren't detected.

Installation

First you will need to install Python if you don't have it, as well as the bl3-cli-saveedit package. I found it easier to install Python for just my user, as opposed to all users. Make sure you find and tick the checkbox for 'add python to path'.

Clyde is a single executable, can run from anywhere, and needs no special privileges; you can put it under your Program Files folder or in a different location if you prefer. You will also need to create a directory for your backup files. Optionally you can copy the saveedit files from the scripts folder, where they get installed, to a more convenient directory – the reason for this will be explained a little later. When you install the bl3-cli-saveedit package, executable files will be created. If you installed Python version 3. 8 and you installed it for your user only (as opposed to for all users), these executable files will likely be located h