This is a Python script made to automatically download and install Minecraft modpacks from Curseforge, Technicpack, FTB, and a direct download link as the pack was intended by the modpack author. Serverpacks provided for modpacks by their authors come in very different kinds, with many different installers. This is an attempt to unify the installation of all serverpacks (for both Forge and Fabric) as the modpack author intended them to be. Here's the kinds of serverpack installers the script works with. The script is extensively tested and should work with all modpacks on Curseforge.
-
Download the modpacks serverpack (or non-serverpack) from the Curseforge Project ID, Technic modpack slug, FTB modpack ID, or a direct download link (url). See details below.
-
Run any provided installers through a unification attempt that come with the serverpack if needed.
-
Remove garbage files.
After the installer is done, the modpack will be fully installed in a separate folder (named after the modpack itself) and ready to be started.
OS: Windows, Linux
The script works with both Forge and Fabric modpacks.
3. Run "run.py" from your terminal with specified arguments like:
python run.py -provider PROVIDER -modpack-id MODPACK-ID [--modpack-version MODPACK-VERSION] [--pterodactyl] [--clean-scripts] [--update]
Provider sets from where to fetch the modpack. Available modes are curse for Curseforge, technic for Technicpack, ftb for Feed The Beast, modrinth for Modrinth, and direct for a direct download link (url) to a modpack (can be from any site).
If provider is set to curse this should be the modpacks project ID found on the Curseforge website in the top right "About Project" section of your desired modpack.
If provider is set to technic, this should be the modpack slug found for each modpack on the Technicpack website. For example, the url for the Attack of the B-Team modpack is https://www.technicpack.net/modpack/attack-of-the-bteam.552556. The slug is the last part of this url minus the dot and the numbers (i.e attack-of-the-bteam).
If provider is set to ftb, this should be the modpack ID found on the Feed The Beast website. In the first part of the url for each modpack there is a numerical ID. For example, The Direwolf20 1.16 modpack's link is https://feed-the-beast.com/modpack/79_ftb_presents_direwolf20_1_16. This modpacks' ID is therefore 79.
If provider is set to modrinth, this should be the modpack project ID OR the modpack slug found on the Modrinth website. On each modpack page, the project ID is found on the bottom-left under "Technical information". The modpack slug is found in the URL after /modpack. Example: https://modrinth.com/modpack/mechanic-craft/ - the slug here is mechanic-craft.
If provider is set to direct, this should be a direct download link (url), from where to fetch the modpack.
Which version of the modpack to install. Specify a version from the modpacks name. For example, RLCraft names their releases like "v.2.9", "v.2.8.2" etc. (as you can see by going to the "Files" section). Here, you can use "v.2.8.2" to pull that version. You can also use an exact version ID from Curseforge found in the URL of the specific pack version. For Technic, versions are labeled as "builds" instead of versions. For FTB, the version is found as an ID using the modpacks.ch api with the modpack ID. Example: https://api.modpacks.ch/public/modpack/79 for Direwolf20 1.16. For Modrinth, the modpack version is found using the Modrinth API labeled as "id". This option is not available if provider is set to direct. If left unspecified, the installer will fetch the latest recommended version of the modpack.
In conjunction with Curseforges' release type system, if no "recommended" version exists, it will pull the latest "beta" serverpack. If no "beta" version exists it will pull the latest "alpha" serverpack. If the modpack has no provided serverpack at all it will pull the latest non-serverpack in the same order. For technic, all modpacks have a recommended version.
Set to clean (remove) the provided startup scripts (.sh for linux and .bat for Windows) when installing the modpack.
Set to remove the /mods, /.fabric and /libraries folders before installing the modpack. This should be set if updating a modpack and not set if it's a first-time install.
Pterodactyl is intended to use in conjunction with a pterodactyl egg install script (More details on this).
There is currently no standardization in how serverpacks are uploaded on Curseforge.
- Some serverpacks include all required files to run the server by default
- Some require Forge or Fabric to be installed separately with only the mods and libraries folders included
- Some for mods to be downloaded using the ServerStarter script by BloodyMods or the somewhat standardized manifest.json file.
This script is compatible with all different types of installers by identifying and running them as tasks separately if needed. The advantage of using this script over other scripts is that it downloads and installs the serverpack as intended by the modpack author, keeping certain files that they have included which, were the mods installed in any other way, would not have been included.
The modpack author may, for example, have made modifications to the server.properties file or any mod config file. These modifications would not be carried over using another way of installing the modpack.
For technic, contrary to curse, modpacks are standardized to include all files required to start the server.
The script can also run in the optional --pterodactyl mode. Pterodactyl mode is intended to be used in conjunction with popular Game Server Panel software Pterodactyl Panel in an egg install script (in bash). Currently, this mode will move the files directly to the root folder of the installation script instead of the modpack installing in it's own subfolder.
Python 3.7+ (Might work on earlier versions of python as well - not tested.)
python3-pip
Java (11 or later) (for Forge/Fabric installers)