diff --git a/BattleModeIcon.ico b/BattleModeIcon.ico
deleted file mode 100644
index debfc47..0000000
Binary files a/BattleModeIcon.ico and /dev/null differ
diff --git a/testConfigs/TestBranches.json b/DEFAULT_BRANCHES.json
similarity index 95%
rename from testConfigs/TestBranches.json
rename to DEFAULT_BRANCHES.json
index d0427d3..c8ad0d3 100644
--- a/testConfigs/TestBranches.json
+++ b/DEFAULT_BRANCHES.json
@@ -15,5 +15,6 @@
       "url": "https://github.com/Legacy-Edition-Minigames/Minigames/tree/aprilfools/2024/battle",
       "desc": "April Fools event from 2024 [1.20.4]"
     }
-  ]
+  ],
+  "config_version": 1
 }
diff --git a/PUBLISH.md b/PUBLISH.md
deleted file mode 100644
index e3aa937..0000000
--- a/PUBLISH.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# Guide-for-Emmie: How to publish a LEB-ToolBox update
-This guide will walk you through the steps required to successfully publish to all LEB users a LEB-ToolBox update.
-
-
-## What is a LEB-ToolBox update?
-A LEB-ToolBox update consist of 4 files: The Source Code (.py), the Windows build (.exe), and the Linux and MacOS (binary)
-
-
-### Things to know:
-LEB-ToolBox update number scheme consists of a FLOAT type number. That is, a number with decimals.
-Updates __must__ be named as follows:
-
-A.BBB
-
-
-_A: main revision_
-
-_B: sub revision_
-
-Unlike other name schemes, you cannot, for example, use the scheme A.B.C, as 1.2.3 isn't a decimal number (you can't just have two points in a decimal number bruh).
-
-
-## GitHub Structure Scheme
-LEB-ToolBox.py  -----  Required to fetch new versions
-
-LEB-ToolBox-vA.B.exe  -----  Windows Builds
-
-LEB-ToolBox-vA.B  -----  Linux Builds
-
-LEB-ToolBox-vA.B-MacOS  -----  MacOS Builds
-
-
-## Hypothetical Environment
-Current version: 1.2  ||  Target version: 1.3
-
-## Step 1: Build your __new__ binaries
-To start, first you need to compile the binaries for your new version.
-
-The values that need to be changed are:
-
-__cnt_program = 1.2__ ----> __cnt_program = 1.3__
-
-__ver_info = "OLD CHANGELOG"__ ----> __ver_info = "NEW CHANGELOG"__
-
-Once it has been patched, build the files.
-
-The names of the files __must__ be:
-
-__LEB-ToolBox-vA.B__ _+ OS specific extension_
-
-_A and B are the version number_
-
-
-## Step 2: Upload files
-Now, you must upload all the binaries and the source code (.py) file.
-__Be warned that the moment you upload the source code (.py) file, the version will be published instantly!__
-If for whatever reason, you don't want to publish the update, change the cnt_program value.
-
-Note that, starting from 1.3, you can skip binaries for some operating systems. A message will popup to the user telling them there isn't a build available at the time.``
-
-
-# You finished!
-You can now test if your update is live by updating an old executable file.
diff --git a/src/main/java/net/kyrptonaught/ToolBox/Menu.java b/src/main/java/net/kyrptonaught/ToolBox/Menu.java
index f28ace0..38db538 100644
--- a/src/main/java/net/kyrptonaught/ToolBox/Menu.java
+++ b/src/main/java/net/kyrptonaught/ToolBox/Menu.java
@@ -83,7 +83,7 @@ public static void menuState(BufferedReader input) {
 
         List<InstalledServerInfo> installedServers = Installer.detectInstalls();
         List<RunningServer> runningServers = ServerRunner.getRunningServers();
-        BranchesConfig branches = ConfigLoader.parseBranches(FileHelper.download("https://raw.githubusercontent.com/Legacy-Edition-Minigames/ToolBox/java/testConfigs/TestBranches.json"));
+        BranchesConfig branches = ConfigLoader.parseBranches(FileHelper.download("https://raw.githubusercontent.com/Legacy-Edition-Minigames/ToolBox/java/DEFAULT_BRANCHES.json"));
 
         HashMap<Integer, Runnable> options = new HashMap<>();
 
diff --git a/testConfigs/AutoHasher.jar b/testConfigs/AutoHasher.jar
deleted file mode 100644
index d5eaa39..0000000
Binary files a/testConfigs/AutoHasher.jar and /dev/null differ