diff --git a/README.md b/README.md
index 4f79a0d..5c44f8f 100644
--- a/README.md
+++ b/README.md
@@ -20,8 +20,6 @@ This repository provides a step by step guide for Linux administrators to host A
   * [Applying server updates](#applying-server-updates)
   * [Daily restarts](#daily-restarts)
   * [Executing RCON commands](#executing-rcon-commands)
-  * [Managing Mods](#managing-mods)
-    * [Prerequisites](#prerequisites)
 * [Setting up a second server](#setting-up-a-second-server)
 * [Addressing "Connection Timeout" issues](#addressing-connection-timeout-issues)
   * [RUMOR (not 100% confirmed): Server too far away/in a different timezone](#rumor-not-100-confirmed-server-too-far-awayin-a-different-timezone)
@@ -354,31 +352,6 @@ docker exec -t asa-server-1 asa-ctrl rcon --exec 'saveworld'
 
 **NOTE:** As opposed to ingame cheat commands, you must not put `admincheat` or `cheat` in front of the command.
 
-### Managing Mods
-
-The mod management tool delivered by this container is currently considered a beta. If you are experiencing any issues following these steps, please open a GitHub issue. The tool is present starting from version `1.2.0` of this container
-image.
-
-#### Prerequisites
-
-Make sure that the ASA server is stopped and that the container is launched in [debug mode](#debug-mode) before you proceed!
-
-#### Installing Mods
-
-##### 1. Downloading Mods
-
-Mods can be downloaded from [CurseForge](https://www.curseforge.com/ark-survival-ascended). Once you downloaded the mods you want to install, upload them to your VPS cloud server, so that they can be moved to your container eventually.
-
-##### 2. Installation
-
-Mods are provided as a zip archive and should not be extracted by yourself, as the mod management tool provided by this container image will take care of that for you.
-
-Copy the downloaded archives to your containers `mods-to-be-installed` directory.
-
-```
-docker cp /vps/path/to/my/mod.zip asa-server-1:/home/gameserver/mods-to-be-installed
-```
-
 ## Setting up a second server
 
 Setting up a second server is quite easy and you can easily add more if you want (given that your hardware is capable of running multiple instances). There's already a definition for a second server in the `docker-compose.yml` file,
diff --git a/root/usr/share/asa-ctrl/cli/utils.rb b/root/usr/share/asa-ctrl/cli/utils.rb
index e8cef31..7b3454d 100644
--- a/root/usr/share/asa-ctrl/cli/utils.rb
+++ b/root/usr/share/asa-ctrl/cli/utils.rb
@@ -12,7 +12,7 @@ def self.passed_command(args)
     end
 
     def self.print_usage
-      puts "Usage: asa-ctrl [rcon|mods] (--help)"
+      puts "Usage: asa-ctrl [rcon] (--help)"
     end
 
     def self.exit_with_error!(message, code)
diff --git a/root/usr/share/asa-ctrl/main.rb b/root/usr/share/asa-ctrl/main.rb
index 91be1b0..58a8999 100755
--- a/root/usr/share/asa-ctrl/main.rb
+++ b/root/usr/share/asa-ctrl/main.rb
@@ -28,15 +28,6 @@
     AsaCtrl::Cli::RconInterface.new(opts)
   end
 
-  args.on 'mods', 'Interface to manage mods' do
-    opts = Slop.parse(ARGV[1..-1]) do |opt|
-      opt.integer '--enable', 'Mod ID/CurseForge Project ID of the mod'
-      opt.bool AsaCtrl::Cli::HELP_ARGUMENT, AsaCtrl::Cli::HELP_DESCRIPTION
-    end
-
-    AsaCtrl::Cli::ModsInterface.new(opts)
-  end
-
   args.on AsaCtrl::Cli::HELP_ARGUMENT, AsaCtrl::Cli::HELP_DESCRIPTION do
     # handled once slop exits
   end