Minecraft
Minecraft
211 ArticlesRelated Categories
Mods & PluginsServer Errors & TroubleshootingManaging Your ServerReducing LagProxy ServersServer AdviceStill have questions?
How to Install a Custom Modpack on Your Minecraft Server
Introduction Custom modpacks are collections of mods that are handpicked and put together by players. Unlike most public modpacks, these don’t come with a pre-made server pack, which makes them more challenging to set up. Because of this, we recommend that only technically advanced users attempt to install custom modpacks, especially if the pack contains a large number of mods. This process can be very time-consuming when working with hundreds of mods. If you’d rather not go through this process yourself, our team can install the modpack for you with the Server Management Addon. ::ProseNote{title="Important" description="As an alternative to using a custom modpack, you can use our Modpack Installer, which has hundreds of pre-made modpacks available for easy installation. Check our guide on it here." appearance="error"} :: --- Part 1: How to get started 1. Make sure that your custom modpack works in a singleplayer world. If the modpack doesn’t load properly in singleplayer, it won’t work on your server. Make sure to fix any crashes or mod conflicts before moving forward. 2. Check if your server has enough RAM to run the modpack. You can see our RAM recommendations here. You can see our guide on how to upgrade your server here. 3. Verify the modloader version that your modpack is using. You can see which game and modloader version your modpack is using by viewing the Minecraft title screen. For example: . Take note of the exact version for Part 2 of this guide. --- Part 2: Getting your server ready 1. Open your server control panel. 2. Shut down the server completely. It's important for the server to remain offline throughout this process unless you are instructed otherwise. 3. Delete all of the files on the server. If there are any files you wish to keep, you can take a backup first to save them for later. See our guide on this here. Note: Make sure to delete every file. Any important files will either be reuploaded with the modpack or will be regenerated by the server in later steps of this guide. 4. Select the correct modloader version on your server. Select the game and modloader version you noted earlier and apply it as the server type. You can check our guide on this here. - If you are using Forge, the 'Recommended' branch will select the latest available version. The 'Experimental' branch allows you to select older versions. - It is important to match your server's modloader version to the exact version used by your modpack. Choosing a different version can cause your server to crash or prevent you from joining. ::ProseNote{title="Unavailable modloader version" description="If your modloader version is not available in the control panel, you can upload it as a custom JAR instead. You can check our guide on this here." appearance="default"} :: --- Part 3: Installing the modpack files on your server 1. Close your game completely. Make sure that your game is fully closed and is not running in the background. This will prevent errors during the next steps. 2. Locate the modpack folder on your computer. The location of the modpack folder will vary depending on the method that was used to install the modpack. See our guide on how to find your modpack folder here. Note: Your modpack folder should contain all of the modpack files, including the mods folder. Double-check that the mods folder contains files inside of it. The files inside will be files. - If you’ve never launched the modpack, then the "mods" folder may not exist yet. Launch it once in singleplayer so the mods folder is generated, then refresh your file browser. - If the "mods" folder still isn't present, then the needed modpack files likely aren't in the location that you're viewing. 3. Compress the modpack files into a single zip folder. Compressing the files is not required, but we strongly recommend it. This helps prevent file corruption, reduces the chance of upload errors, and makes the upload speed much faster in the next steps. 4. Connect to your server with FileZilla. Using an SFTP client like FileZilla is strongly recommended. It manages large uploads much faster than your browser. Check our guide on how to connect to your server with FileZilla here. 5. Upload the zip to your server using FileZilla. 6. Once it is done uploading, unzip the folder in the control panel. Note: You may need to refresh the file manager for the zip folder to appear after it has been uploaded. In the control panel, click the refresh symbol next to the "SFTP Connect" button. 7. Move all of the files inside the unzipped folder into the base directory. The modpack folders and files must be moved into the base directory in order for them to be recognized by the server. After moving them to the base directory (/), you can confirm they were moved by clicking "Home" in the File Manager. All of the modpack folders and files should be present there. --- Part 4: Disabling any client-side only mods on your server After uploading the modpack files to the server, the next step is to disable any client-side only mods inside the server's folder to prevent crashes. 1. Understanding client-side only mods Client-side only mods change how Minecraft works on your own computer, and any changes they make are only visible to you — not other players. They do not modify the server’s mechanics. This means they only need to be installed on your computer. Installing them on the server often causes it to crash because these mods aren’t built to run server-side. An example of this is the "Zoomify" mod, which lets you zoom your camera using a keybind. Since it only modifies the behavior in your own game, it should stay enabled on your computer, but be disabled on your server. 2. How to disable client-side only mods You can disable a client-side only mod by renaming it in the control panel and adding the text at the end of the file name. This fully disables the mod, while still keeping the file present in case you disabled the wrong mod and need to re-enable it later. You can re-enable the mod by removing the text from the file name. Example: The mod named would be renamed to to disable it. 3. How to identify client-side only mods There is no single way to confirm if a mod is client-side only, but mod authors usually provide a way to identify them using one of the methods listed below: ::ProseNote{title="Dependencies" description="Avoid disabling mods listed as libraries, cores, APIs, or compatibility mods. These are almost always required server-side." appearance="error"} :: Method 1 - Modrinth: If a mod is available on Modrinth, the author will indicate whether it is client-side only or offers server-side support. In the following example: The Fabric API mod has server-side support and can remain enabled on the server. The Sodium mod is listed as client-side only and should be disabled on the server. Method 2 - Mod Description: Authors sometimes specify in the mod description on CurseForge, Modrinth, or other platforms, whether the mod is supported server-side or if it's client-side only. For example, the FreeLook mod author specifies that the mod is client-side only in the description of the CurseForge page. Method 3 - Mod Function: You can often tell if a mod is client-side only by observing what it does. If a mod adds new items, blocks, or mobs to the game, or adds a new biome, then it is server-side. If a mod only changes things you see or experience on your own screen, like visual effects, camera zoom, or interface changes, then it is client-side only. For example, you can use client-side only mods on any multiplayer server, and it won't affect other players. Note: If you have trouble finding where a mod originated from, you can copy the full name of the mod and search it in quotes in your browser. For example, searching (with the quotes) should bring up results that include the file name of the mod, which is often posted by the original author. --- Part 5: Starting the server and resolving any remaining errors After disabling the client-side only mods in part 4 of this guide, you can start your server. If everything was set up correctly, the server will go online, and the modpack will work when you join. You can skip to part 6 of this guide if the modpack is working. However, your server may crash with various errors if issues are still present in the modpack. This section will go over the three most common errors that you may come across. Error 1 - Missing dependencies: Many mods require one or more dependencies in order to work properly. Dependencies are mods that are libraries, cores, APIs, or compatibility mods. If a required dependency is missing, the server will crash. As seen in the example below, the server has crashed because the "Better Combat" mod is missing the following dependencies: Player Animator and Cloth Config. You can resolve this by either installing the dependencies, within the version range specified in the console, or by removing the "Better Combat" mod entirely. You can install the required dependencies by downloading them from the mod page and placing them in the server’s folder just like any other mod. Error 2 - Client-side only mods still left on the server: In the following example, the server crashed because the mods "Oculus" and "VoidFog" failed to load with the following error: This error will specify which mod is causing the crash. Directly below it, you can also see the following error: This confirms that these mods failed to load because they are client-side only mods. To resolve the issue, you can disable these mods on your server. The mods can stay enabled on your computer. ::ProseNote{title="No error" description="While uncommon, some client-side only mods like Rubidium, Embeddium, and others, may not show an error in the console. If you suspect that one is still enabled, review your mod list again." appearance="error"} :: Error 3 - Mod (modname) has failed to load correctly: In the previous example, the message below the error indicates that the mods were client-side only which caused the crash. However, sometimes you will only see the original error ("Mod has failed to load correctly") with no decipherable messages beneath it. In these cases, the reason the mod is failing to load is more difficult to determine. If the server generated a crash report, it might include a more specific reason. General Troubleshooting: - Download and reinstall the mod again to rule out any issues with the file. - Make sure the mod was created for the correct version (the server version). - Try a different version of the mod, preferably the latest version of the mod (which still matches the server version). - Mods can sometimes fail to load due to an issue with the mod itself, which has not yet been resolved by the author. As a last resort, you can remove the mod and find a similar mod to replace it with. Replace the mod on your client as well to prevent a mismatch when joining. Compatibility Issues: Mods can also fail to load because of a compatibility issue — most commonly with another mod. Check for common compatibility issues noted by the mod author, usually on GitHub under known issues, in the mod description, in the author's Discord, or other official sources. For example, in the screenshot below, the "Create" mod is failing to load. This is because the Create mod is incompatible with some of the extra Create add-on mods. Installing the "Create: Add-on Compatibility" mod resolves the issue. ::ProseNote{title="Other errors" description="Note that this article is not an exhaustive list and you may experience other errors not listed here. If you are unable to determine the cause of a crash, please feel free to reach out to our support team for further guidance." appearance="default"} :: --- Part 6: Making additional configurations Once your server is online with your modpack, most mods should work right away without any extra setup. However, a few mods may require additional configuration to function properly, particularly those that need access to external services. For example, some mods may require an API key, token, extra port, or database connection to work correctly. Some examples include: - Simple Voice Chat. - Biomes O’ Plenty (only if using Forge versions 1.12 and below). - GeyserMC. - Mods that require databases. - Mods that require a token like DiscordSRV. Keep in mind that this is not a complete list. A mod may require additional setup if the author has noted it on the mod page, if errors show up in the console specifying that additional setup is required, or if the mod does not work as expected in-game. --- That’s it, you’re all set! If you run into any issues with your custom modpack or have any questions, please contact our support at: https://shockbyte.com/billing/submitticket.php
How to Restore a Backup from the Simple Backups Mod
The Simple Backups mod automatically creates and stores backups of your server in the server files. This guide will go over how to restore these backups. We recommend enabling automatic backups through our control panel because it only takes one-click to restore these backups. If you'd like to enable automatic backups you can find our guide on the topic here. ::ProseNote{title="Important" description="As this process involves deleting files, make sure to create a backup of your server before proceeding with the steps in this guide." appearance="error"} :: --- How to Get Started 1. Access your server's control panel and shut down the server. 2. Navigate to the Config tab and take note of the name in the "Level Name" setting. --- Deleting Your World 1. Navigate to the Files tab. 2. Select the folder matching the name that you saw in the "Level Name" setting. 3. Delete the world folder. --- Retrieving a Backup 1. Open the folder. ::ProseNote{title="Note:" description="If you are on the versions 1.21+ then you may need to open the folder, then the folder inside of it: " appearance="default"} :: 2. Select the backup that you want to restore. 3. Select the Move button. 4. Set the new path to to move the backup to the base directory. --- Unzipping a Backup 1. Select the Up Arrow to move back to the base directory. 2. Select the backup that you just moved. 3. Select "Unzip". --- Restoring a Backup 1. Open the new unzipped folder. 2. Select the world folder inside of it. 3. Select the Move button. 4. Set the new path to to move the world to the base directory. Now you can start the server and your backup should be restored.
How to Re-enable Achievements on Your Bedrock Minecraft World
If you've accidentally disabled achievements on your Bedrock server by enabling cheats, you can re-enable achievements with the use of a world editor like Dovetail. ::ProseNote{title="Important" description="As this process involves modifying your world files, make sure to create a backup of your server before proceeding with the steps in this guide." appearance="error"} :: --- How to Get Started 1. Open your Server Control Panel. 2. Stop your server and wait for it go offline. 3. Navigate to the Config tab and open Server Properties (Bedrock). 4. Locate the Allow Cheats setting, then Disable it, and Save the file. This must be disabled to re-enable achievements. 5. Locate the Level Name setting and take note of the name for the next steps. 6. Navigate to the Files tab and open the folder. 7. Open the folder matching the name you saw in the Level Name setting, then Download the file. Modifying the level.dat File Once the file has been downloaded, it can be edited it to re-enable achievements. 1. Open the Dovetail editor. 2. Select Open and open the file you downloaded. 3. Find the following values and change them from to : cheatsEnabled, commandsEnabled, and hasBeenLoadedInCreative. 4. Select Save to download the updated file and proceed to the next section. Uploading the Modified File Back to the Server Once the values have been updated and the level.dat file has been downloaded, it can be uploaded back to the server. 1. If the modified file is named , rename it to . It will not be recognized by the server if it's named incorrectly. 2. Navigate to the world folder where the file was from originally. 3. Upload the modified file, then select Overwrite to replace the original file. 4. Start your server. --- Creative Players If any players are still in Creative Mode, their gamemode will need to be set back to Survival Mode for them to earn achievements. Thankfully, you don't need to enable cheats to do this. You can run the following command in the Console instead: --- That's it, achievements should be re-enabled for all players on your Bedrock server!
How to Find and Share Any Minecraft Log
When troubleshooting an issue with your Minecraft server, logs can help you diagnose and tackle the problem at hand. Shockbyte staff may also ask for logs during a support inquiry to quickly identify any issues you may be experiencing. --- How to Find and Share Your Server Console Log With our panel, sharing your console log takes just two clicks. 1. Navigate to the Shockbyte Panel and open up your server. 2. Click the overflow menu in the top-right corner of your console. 3. Click the Share Log button. How to Find and Share Your Server's Crash Reports Crash reports contain information including what mods were loaded during the crash and where or when exactly the crash occurred. 1. Go to the Shockbyte Panel and open up your server. 2. Navigate to the Files tab. 3. Locate and open the crash-reports folder. 4. Sort the directory by Last Modified and click on the latest crash report. 5. Copy all of the text and paste it into our Hastebin. 6. At the top right, click Save and copy the generated link in your address bar to share the log. Local Client Logs for Vanilla/Modded Minecraft Versions Minecraft generates client-side logs, which are saved to your computer locally. These logs are similar to console logs in that they display a timeline of events, however, client-side logs only display information relating to your game client, not the server. 1. On your keyboard press + at the same time. This will open a Run dialogue box usually in the bottom left of your screen. 2. Paste into the Run dialogue field and press OK. 3. Open latest.log with any text editing program. 4. Copy all of the text in this document. 5. Paste the text into our Hastebin then click Save. 6. Copy the generated link in your address bar to share the log. --- Finding Logs for CurseForge Modpacks The CurseForge launcher makes installing modpacks much easier than traditional methods. It creates separate Minecraft instance folders, each containing all necessary files, including log files unique to the mod pack you are playing. 1. Open the CurseForge launcher, and click the Minecraft logo. 2. Right-click the modpack you are playing and select Open Folder. 3. Open latest.log with any text editing program. 4. Copy all of the text in this document. 5. Paste the text into our Hastebin then click Save. 6. Copy the generated link in your address bar to share the log. If you need help with troubleshooting your server, just reach out to our support team and share any logs created from the steps above.
How to order a Minecraft Server with Shockbyte
Minecraft servers are a fun way to play Minecraft with your friends and other players all over the world. With Shockbyte, running a Minecraft server has never been this easy! Shockbyte offers server hosting for both Minecraft Java and Bedrock Editions, so you can run a server whether you play on a PC, mobile, tablet, console or any other supported devices. Not only that! We also support all server types available for Minecraft, giving you the freedom to choose any server type and version, and you can change this at any time you want. If you're ready to kick-start your Minecraft server with Shockbyte, simply follow the guide below: --- Ordering Your Minecraft Server You can order a Minecraft server through the Shockbyte website. 1. From the top navigation menu of Shockbyte's website, click Minecraft Server Hosting. 2. On the Minecraft plans page, select a server plan by clicking on Add to Cart directly below your chosen plan. The right server plan for you will depend on the amount of RAM your server needs to support the amount of players you expect to host, the Server Type you want to run, the type and number of mods or plugins you intend to use, etc. If you're not sure how much RAM you will need, you may read our article here: How much RAM do I need for my Minecraft server? The plans listed on the page will show recommended slots, which is the recommended number of players each plan can support. However, these are simply suggested numbers, and you can adjust the number of players you can allow in your server regardless of your plan size. 3. On the order page, select your preferred billing cycle. By default, this is set to monthly. However, you may choose to pay for your server renewal on any of our available cycles explained below: Monthly : Billed one (1) month after the previous one. Quarterly : Billed three (3) months after the previous one. Semi-Annually : Billed six (6) months or half a year after the previous one. Annually : Billed 12 months or a full year after the previous one. 4. Under the Configurable Options section, select your preferred Server Location, and you can include addons to your server package order by selecting your preferred addons. If you do not know which location to choose, you may read our guide here: Which server location should I choose? 5. Once you've reviewed the Order Summary, click Continue to checkout. 6. If you have a discount code, enter it in the bottom section of the Review & Checkout page and click Validate Code to apply the discount and update your total amount due. If you have successfully applied the coupon or do not have one, click the Checkout button. 7. You will be asked to log in or register on the Checkout page. If you have an account, simply click on the Already Registered button. Otherwise, you may sign up by filling out the registration form or through any of the alternate options shown on the page. 8. Once logged in or signed up, scroll to the lower section of the Checkout page to choose your preferred payment method, review and agree to the Terms of Service by ticking the checkbox, complete the captcha, and finally, click Complete Order to checkout and pay for your order. 9. Once you've successfully paid for your order, check your registered email's inbox for the email containing your Minecraft Server Details and Panel Login Information. You may also find a copy of the same email in the client area: Email History --- You can now begin setting up and playing on your Minecraft server! Be sure to check out the knowledgebase for other guides and articles: Minecraft Minecraft Bedrock Edition (MCPE)
How to Convert Worlds from Vanilla to Spigot
This guide is for converting your worlds from Vanilla to Spigot. If you're looking to convert your world from Spigot to Vanilla, take a look at this guide here. If you've recently updated your server from Vanilla to Spigot, you may notice that your Nether and End dimensions have been reset; any changes you made in those dimensions have disappeared. Not to worry, however, your progress hasn't been lost. The reason your Nether and End dimensions have reset is that Spigot stores dimensions in a different way than Vanilla. Spigot, as well as CraftBukkit and Paper, store their other dimensions in two separate folders named and . Vanilla stores these dimensions in and respectively, so you can restore your old dimensions by migrating the old data into the new folders. --- Converting Worlds from Vanilla to Spigot If you change to Spigot and want to transfer your dimensions, you can follow these steps: 1. Login to your server's control panel and Stop the server. 2. Navigate to your Files tab and open the affected dimensions: If you need to restore your Nether world, open If you need to restore your End world, open 3. Download the Region folder from that directory onto your computer. 4. After the download is complete, navigate to the new dimension folder made by Spigot: If you are restoring your Nether world, open If you are restoring your End world, open 5. Upload the region folder you downloaded in step 4 and confirm any overwrite prompts that may appear. 6. Start your server. When you load into the affected dimension, your data should now be present.
How to Convert Worlds from Spigot to Vanilla
This guide is for converting worlds from Spigot to Vanilla. If you're looking to convert your world from Vanilla to Spigot, check out our guide on the process here. If you're using Spigot, PaperSpigot or CraftBukkit and you have switched to Vanilla already, you probably noticed that your Nether and End worlds have reset; any changes you made in those dimensions have disappeared. You don’t need to worry, however, as your progress has not been lost. Vanilla stores the data for those dimensions in a different location on the server. When you first started your Spigot server using the default world name, you might have noticed that two new folders were created, named and . This is how the forks of CraftBukkit (Spigot & Paper) store these two dimensions. However, Vanilla stores them differently as and , respectively. This would be why your progress is not there, as Vanilla Minecraft is not reading the region data from the CraftBukkit-generated dimensions. --- Converting Worlds from Spigot to Vanilla If you change to Vanilla and need to migrate your dimension data, you can follow these steps: 1. Login to your server's control panel and Stop the server. 2. Navigate to your Files tab and open the affected dimensions: If restoring the Nether, open If restoring the End, open 3. Download the Region folder from the respective directory to your computer. 4. After the download is complete, navigate to the new dimension folders: If restoring the Nether, navigate to If restoring the End, navigate to 5. Upload the region folder you downloaded. 6. Start your server. When you load into the affected dimension, your data should now be present.