-
Notifications
You must be signed in to change notification settings - Fork 57
serverpack creator re-work #408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,105 @@ | ||
| --- | ||
| id: serverpackcreator | ||
| title: "Serverpack Creator" | ||
| slug: /extras/serverpackcreator | ||
| hide_table_of_contents: true | ||
| sidebar_label: "Serverpack Creator" | ||
| description: How can I make a serverpack to upload to my server? | ||
| keywords: | ||
| - Minecraft | ||
| - Forge | ||
| - Fabric | ||
| - Neoforge | ||
| - Server | ||
| --- | ||
|
|
||
| import Tabs from "@theme/Tabs"; | ||
| import TabItem from "@theme/TabItem"; | ||
|
|
||
| This guide gives you a step by step method on creating your own server pack for a custom modpack, or a modpack that doesn't have an available server pack yet. | ||
|
|
||
| :::warning | ||
| While Server pack Creator can make serverpacks it's not perfect and doesn't have a 100% guarantee in making the serverpack functional. Test to be sure it works. | ||
| ::: | ||
|
|
||
| :::important | ||
|
|
||
| **Requirements!** | ||
|
|
||
| - Java 21+ | ||
| - **[Download Server pack Creator](https://github.com/Griefed/ServerPackCreator/releases)** | ||
|
|
||
| **Terminology** | ||
|
|
||
| - Server Pack Creator -> SPC (to make it easier to type out) | ||
|
|
||
| ::: | ||
|
|
||
| ## Part 1. Serverpack creator. | ||
|
|
||
| ### Follow the steps below for your launcher on how to properly use SPC for each launcher. Ensure you select the correct launcher. | ||
|
|
||
| #### The example modpack is [Beyond Depth](https://www.curseforge.com/minecraft/modpacks/beyond-depth) for curseforge & prism, and [Homestead](https://modrinth.com/modpack/homestead) for modrinth. Both do not have a serverpack available from their respective platforms natively. | ||
|
|
||
| While Beyond depth and Homestead provide their own ways to do their serverspacks, we use these modpacks strictly as **examples** for SPC as they are good examples of popular modpacks and have a good selection of mods. | ||
|
|
||
| <Tabs groupId="Launchers"> | ||
| <TabItem value="curseforge" label="Curseforge"> | ||
| Steps: | ||
|
|
||
| 1. Open SPC and navigate to your modpack folder. To find out the modpack folder, right-click the modpack in the launcher and click "Open Folder". Then read the folder location and navigate to it from SPC. CFImage1 (shows how to read the folder location) | ||
|
|
||
| 2. After entering the modpack folder, SPC should automatically detect the mods (game modifications), configs (configuration files), and other folders that the modpack uses. It will also detect the Minecraft version, mod loader (software that loads mods), and mod loader version. | ||
|
|
||
| 3. If all details are correct, click Create ZIP Archive, then Generate, and wait. | ||
|
|
||
| 4. When prompted about the Serverpacks folder, select no. Instead, press Server packs below the generate command. | ||
|
|
||
| 5. When done, continue to part 2 of the guide below. | ||
|
|
||
| </TabItem> | ||
| <TabItem value="modrinth" label="Modrinth"> | ||
| Steps: | ||
|
|
||
| 1. Open SPC and go to your modpack folder. To find the folder, left-click your modpack icon on the left, select the three dots at the top right, and choose "Open Folder." Note the folder location and navigate to it in SPC. Mrimage1 (shows how to read the folder location) | ||
|
|
||
| 2. Once in the modpack folder, SPC should detect the mods, configs, and other folders that the modpack uses. It also detects the Minecraft version, mod loader, and mod loader version. | ||
|
|
||
| 3. When you confirm everything in step 2 is accurate, To make things easier, check create zip archive, then click generate and wait. | ||
|
|
||
| 4. If successful, you will be prompted to open the Serverpacks folder. Select No. Instead, press Server packs under the generate command. | ||
|
|
||
| 5. Once done, move on to part 2 of the guide below. | ||
|
|
||
| </TabItem> | ||
| <TabItem value="prismlauncher" label="Prism Launcher"> | ||
| Steps: | ||
| 1. Open SPC and navigate to your modpack folder. To find out the modpack folder, left click your modpack once, then press "Folder" button on the right side. Then read the folder location and navigate to it from SPC. PrismImage1 (shows how to read the folder location) | ||
| :::warning | ||
| Prism launcher is fairly different when it comes to modpacks, you need to enter **2** folders before you can generate a server pack. Please be sure to read the guide carefully. | ||
| ::: | ||
| 2.1. First enter the Flame folder and select it for SPC, it should detect the mod loader,the mod loader version, and the minecraft version. | ||
|
|
||
| 2.2. After confirming the details re-open the folder select and enter the Minecraft folder which contains the mods, configs, and other folders. After entering this folder, SPC should detect the mods, configs, and other folders that the modpack uses. | ||
|
|
||
| 3. After you confirm everything in 2a & 2b is correct or accurate, click create ZIP archive, then Generate, and wait. | ||
|
|
||
| 4. If everything goes accordingly you will be prompted to look into the Serverpacks folder, Select no and instead press Server packs under the generate command. | ||
|
|
||
| 5. After all of this is done you can now officially move onto part 2. of the guide. Right underneath. | ||
| </TabItem> | ||
|
|
||
| </Tabs> | ||
| ## Part 2. Installing on panel. | ||
|
|
||
| 1. To prepare for your serverpack, delete all the files currently inside the file manager in the duckpanel. This is to ensure there will be no confusion on where files are when you unarchive the serverpack. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Step 1 tells users to delete everything in the panel file manager before uploading a server pack, which can wipe existing worlds, configs, and other persistent data on non-fresh servers; this is an irreversible data-loss path introduced by this rewrite and it is not required for unpacking a generated server pack. The guidance should be scoped to a new/empty server or require a backup-first flow. Useful? React with 👍 / 👎. |
||
| 2. After creating the serverpack, you can now upload it to the server. To do this, you will need to use SFTP. We have an in-depth guide on how to use SFTP [here](/sftp). | ||
| 3. Once you have uploaded the serverpack, you will need to unarchive it using the file manager on the duckpanel. Right click your zip file and click "Unarchive". You should then see all the files that were in the serverpack appear in the file manager. Such as mods, configs, and other folders. | ||
| 4. After unarchiving the serverpack, you can install the server [jar with this simple method](/jars) | ||
| :::info | ||
| If you are confused on what jar to select, you can check the **variables.txt** file that SPC generates with the serverpack. | ||
| **For example, below is the variables.txt Server type Fabric for Version 1.20.1 with Build 0.18.6.** | ||
|  | ||
| ::: | ||
| 5. Once you have changed the server type to the correct one, you can start the server and enjoy the modpack on your server! | ||
| If you need more help. Join the [discord server](https://bloom.host/discord). | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CurseForge, Modrinth, and Prism steps currently include raw placeholder tokens like
CFImage1instead of actual embedded images/links, so users cannot see the referenced folder-location examples that the instructions depend on. In this state, the guide’s launcher-specific navigation flow is incomplete and likely to cause users to pick the wrong directory.Useful? React with 👍 / 👎.