Please make sure the modpack runs on Forge 1.17.1 or newer before reading this guide - if the modpack is for Forge 1.16.5 or older the installation process is different! There is a guide for 1.16.5 and older modpacks here:
- Installing A Modpack Not On The Jar List (Forge 1.16.5 and Older)
For Fabric modpack installations please follow the guide here:
- Installing A Fabric Modpack Not On The Jar List
Pre-Installation Server File Preparation
A few strongly recommended steps to follow to prepare the server for the modpack installation are:
1 - Shut the server down on the control panel (mc.beastnode.com)
2 - Download anything you need to keep from the server files (for example world folders) and then delete everything except for the server.properties (if you need it to set a level-type, for example if the modpack you wish to use has Biomes O Plenty or OpenTerrainGenerator or similar - if not then this can also be deleted).
This should be done every time you install/switch to a new setup to limit any potential issues - any files from a different setup can cause major issues that would not be there otherwise (particularly when using worlds across different setups).
You can access, download and wipe files through an FTP client following the guide HERE.
3 - Select the 'Custom Server JAR' option for either Forge 1.17.1 or 1.18+, depending on what you are installing, on the jarlist (right at the top) and the page will refresh to confirm the change..
4 - If you are using a custom world generation mod make sure to enter the code for that mods generation (EG for OpenTerrainGenerator the code is OTG in all caps) in the Files > Config Files > Server Settings' Level Type option and save changes to the file.
5 - If the modpack requires a specific world name (for example if it comes with a premade world folder, or requires a specific world name for a mod it uses - for example "Biome Bundle" being the most common for packs using OpenTerrainGenerator) enter it in the World text field on the main page of your servers control panel and hit Save at the bottom of the page.
While not necessary - if the modpack does not require a specific world name it would be recommended to use the name of the modpack so you have an easy reference for which world folder is for which modpack if you switch between any.
Modpack File Preparation
You will then need to download and prepare the files for the modpack, ready to upload to the server. How you get your modpack server files varies depending on the launcher and/or modpack developer that they are provided by - some provide you with an executable file to download the files as they are needed, some will provide a .zip that contains the files directly.
As there are so many ways for the developers to provide you with the files we cannot cover them all - this guide will only cover what you need to change before uploading them to the server for it to work.
Common examples of where to find server file downloads:
- Technic modpacks will link to their server downloads, if available, on their website pages,
- Feed The Beast and ATLauncher server downloads can be downloaded through the launcher itself.
- Most CurseForge modpacks' server files can be found on that modpacks CurseForge page.
Other modpacks/launchers will provide server downloads through their own launcher or their own websites.
If the modpack you wish to use does not provide a server file download you can install the pack using your client installation of the modpack. In this case follow the guide here on installing Forge itself, and use the mods/config folder from your client installation instead:
- Installing Custom Builds of Forge and/or Custom Mods (Forge 1.17.1 and Newer)
What you need to change in the modpack server files before uploading::
When you have the files from the modpacks server download in a folder on your computer you will need to make one small change to allow it to work with our hosting, which is one small change to the libraries folder. Find the unix_args.txt file in libraries/net/minecraftforge/forge/<version>/ and copy it into the libraries folder itself, so you should have this directly inside the libraries folder:
Your files are now ready to be uploaded!
Simply make sure the server is offline and connect to the server files with an FTP client (see guide linked above). If you haven't already delete everything that is no longer needed in the server files (see above for information on this too) and then when ready simply upload everything from the modpack server files to the servers base directory (if you use FileZilla as per the guide above - and some other FTP clients - you can just select everything in the local folder and drag them onto FileZilla, dropping them in the base directory to upload them there).
When everything has uploaded go to your MultiCraft control panel - making sure any necessary level-type options or world names are correctly set and the Custom Server JAR option for Forge 1.17.1+ is selected on the drop down list - and start your server up.
If everything has been done correctly everything should now load up fine! Note that modded setups can take a long time to load, particularly those with a lot of mods to process.
Note that unlike every other server setup with our hosting, Forge 1.17.1+ does not use the jar folder - it will always be present as MultiCraft will create it on server startup, but you will not need to move anything into it for Forge 1.17.1+.