Minecraft
Minecraft
208 ArticlesRelated Categories
Mods & PluginsServer Errors & TroubleshootingManaging Your ServerReducing LagProxy ServersServer AdviceStill have questions?
How to Migrate your Minecraft Server From Java 21 to Java 25
Introduction Migrating your Minecraft server to a newer Java version ensures compatibility with the latest plugins and mods. The following steps will guide you through migrating your server from Java 21 to Java 25 while keeping your data safe. --- Step 1: Shut down your server. Step 2: From the tab of your control panel select "Edit Server Type". Step 3: Select "Custom Jar" from the options listed and click "Next Step" Step 4: Select "Java 25" from the dropdown and click "Next Step" and then "Save Changes" Step 5: Go to your server's tab and rename your server's JAR file to "custom.jar" Step 6: With all your files securely in place, start your server. Your server will now load using Java 25, yay!
How to Remove Items from a Player's Inventory or Ender Chest on Your Java Minecraft Server
You may want to remove specific items or all items in a player's inventory or ender chest for several reasons, such as if they obtained corrupt items, duplicate items, or other disallowed items on your server. ::ProseNote{title="Resetting Player Data" description="Are you looking to reset all of a player's data instead? This includes their inventory, experience, position in the world, achievements, and other progress. Check out our guide on the topic here." appearance="discovery"} :: --- Getting Started There are different methods to delete items from a player’s inventory or ender chest, depending on whether the player is online, the server type, whether it's vanilla, supports mods, or supports plugins. This guide will explain the best method to use in each situation. ::ProseNote{title="Important" description="Make sure to create a backup of your server before proceeding with the steps in this guide. Once items are deleted, they cannot be recovered without a backup." appearance="error"} :: --- Removing the Inventory Items from an Online Player If a player is online, the Minecraft command can be run to clear either all of the items in their inventory or specific items in their inventory. This does not apply to ender chests. For a full list of the available arguments that can be used with the command, check out the Minecraft Wiki Page here: Clear Command Arguments | Command | Effect | |---------|--------| | /clear | Clears all items and armor in their inventory. | | /clear | Clears all of the specified item in their inventory. | | /clear | Clears the specified amount of the item in the player's inventory. | --- Removing the Inventory or Ender Chest Items from a Player Alternative methods are required to remove items from offline player inventories and player ender chests because the command does not work in these situations. Two methods can be used: Installing mods or plugins, or manually editing the user's player data file. Mods and Plugins Mods or plugins can be installed on the supported server types to manage an offline player's inventory, or an enderchest. See our list of popular mods and plugins with this feature below. Steps to remove items from a player will vary between mods and plugins. Refer to the documentation or support from the mod or plugin author for further guidance. ::ProseNote{title="Unavailable Modification" description="If you cannot find a mod or plugin for your server type or game version on this list, you can search for alternative options on Modrinth, CurseForge, or SpigotMC, or skip to the next section." appearance="default"} :: Mods | Mod | Modloader | Versions | Inventory | Enderchest |-|-|-|-|-| | InvView | Fabric | 1.16.2 - 1.21+ | X | X | | InvView | Forge/NeoForge | 1.16.5 - 1.21+ | X | X | Plugins | Plugin | Versions | Inventory | Enderchest | |-|-|-|-| | Invsee++ | 1.8 - 1.21+ | X | X | | OpenInv | 1.0 - 1.21+ | X | X | | EssentialsX | 1.8 - 1.21+ | X | X | --- Manually Editing a Player Data file This section will require the use of a world editor like NBTExplorer. These steps can be followed on any server type, including Vanilla Minecraft servers. ::ProseNote{title="Player" description="The affected player must remain offline throughout this process for the steps to work correctly." appearance="error"} :: Downloading the Player Data file 1. Obtain the player's UUID from NameMC and save it for later. 2. Open your Server Control Panel. 3. Navigate to the Config tab and open Server Properties (Java). 4. Locate the Level Name setting and take note of the name for the next step. 5. Navigate to the Files tab and open the world folder matching the name you saw in the Level Name setting. 6. Inside the world folder, open the folder. 7. Select the file that contains the player's UUID that you previously identified in Step 1, then Download it. Do not download the file with at the end of the file name. This file is not currently in use and has a gray icon. Navigating the Player Data File with NBTExplorer 1. Launch NBTExplorer and open the player data file that you downloaded. 2. Use the button next to each entry to view its data. 3. Open the main player data section, then open the next desired section. The Inventory section will be used in the following example. - Inventory - Inventory item data. - Equipment - Armor and offhand item data. - EnderItems - Ender chest item data. 4. Inside the Inventory section, folders named will represent occupied inventory slots. The other sections follow a similar format. Continue using the button to expand each folder and view its contents. Each entry inside the folders will consist of the following: - (Amount of the item) - (Minecraft ID of the item) - (Inventory slot the item is located in) You can use MCUtils to see the location of a specific slot in an inventory or ender chest. Editing and Removing Items Using NBTExplorer, you can perform advanced changes such as adjusting item quantities, replacing existing items with different ones, moving items between slots, and more. While the next examples will only focus on removing items from a player’s inventory, the same steps can be used to remove items from an ender chest. Option 1 - Deleting All Inventory Items 1. Select the Inventory section and click the red to delete all inventory items. 2. Select the Equipment section and click the red to delete all of the player's armor, and their offhand item. 3. Save the updated player data file. 4. Upload the file back to the folder, and Overwrite the existing file. All of the player’s inventory items should now be removed when they next join the server. Option 2: Deleting a Specific Inventory Item In the next example, we will remove a Mob Spawner from slot 25 in the player's inventory. 1. Locate the item by looking through each folder in the Inventory section. 2. Select the folder containing the item data and click the red to delete it. This will delete all item data in that slot, removing the item entirely, whether it’s a single item or multiple of the same item. 3. Save the updated player data file. 4. Upload the file back to the folder, and Overwrite the existing file. The specified item should now be removed from the player's inventory when they next join the server. The images below show the example player's inventory before and after following this method. --- To learn more about Minecraft server hosting, you can browse our library of Knowledgebase articles here.
How to Reset Chunks with AmuletMC on Your Minecraft Server
Sometimes you might need to reset individual chunks on your Minecraft server. There are several world editors you can use for this. If your game version is below 1.12, you will need to use MCASelector instead of AmuletMC. We have a guide on how to use it here. AmuletMC is another popular world editor because it is more versatile. It supports both Bedrock (versions 1.7 and above) and Java Edition (versions 1.12 and above). Also, it allows you to edit your server chunks in both a 2D interface and a 3D interface, unlike MCASelector. ::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"} :: --- Installing AmuletMC 1. Navigate to the AmuletMC website. 2. Download the version of AmuletMC that matches your computer's operating system. Currently, the installation steps vary between versions due to an issue with Linux and macOS. Please refer to AmuletMC's documentation or Discord for further guidance on installation. Opening your world file on AmuletMC The steps listed in this guide work for both Java Edition and Bedrock Edition worlds, but in this guide, we will be using a Java Edition world as the example. 1. Download your Minecraft world. 2. Extract the world folder that was downloaded. 3. Open AmuletMC and select "Open World", then "Open Other World". 4. Select your folder in the prompt to open it. Keep in mind that only Spigot-based server types will store the Nether and End dimensions in separate folders named "worldnether" and "worldend". Other server types will store the Nether and End dimensions in the "world" folder with the rest of the world data. ::ProseNote{title="End Dimension" description="Resetting the wrong chunks in the End dimension may break it completely. If you're attempting to reset chunks in the End dimension, please review our other guide on the topic here." appearance="error"} :: Resetting the Chunks on your World 1. Once your world has been opened in AmuletMC, select "3D Editor" on the left-hand side. 2. Once loaded, select the "3D" button at the top to change your world view to 2D. This is not required but is strongly recommended as it's easier to navigate the 2D editor when resetting chunks. 3. Select the "Chunks" button at the bottom of AmuletMC to change the selection mode to chunks instead of individual blocks. 4. Find the chunks that you want to reset. You can navigate the 2D editor by editing the coordinates in the box at the top of AmuletMC, by pressing the WASD keys to move around the world, and by using the scroll wheel on your mouse to zoom in or out. 5. Select the chunks that you want to reset, then select the "Delete Chunks" button, and select "Yes" to confirm. 6. After the chunks are reset, open the "File" tab at the top-left of AmuletMC and select Save. --- Uploading the world back to your server 1. Reupload the edited world folder back to your server. 2. Start your Server. Once started, it will regenerate the chunks that were reset. --- If you run into any issues or have any questions, please contact our support team at: https://shockbyte.com/billing/submitticket.php
How to Fix the Error "ZIP END Header Not Found"
Some Minecraft servers may crash with the following error: . While it most commonly affects modded Forge servers, it can also occur with other server types. This guide will cover the possible solutions for this issue. ::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"} :: --- Regenerating the Server file This error can happen when the server's .jar file becomes either fully or partially corrupted. You can regenerate the file to resolve the issue. 1. Open your Server Control Panel. 2. Shut Down your server. Make sure that your server is completely offline. If it is not offline, then it will not regenerate the .jar file correctly. 3. Navigate to the Files tab. 4. Locate and delete the server's file. For vanilla Minecraft servers, the .jar file will be named . For all other server types, the server's .jar file will include the server type in the name. For example, a Paper 1.21.5 server would use: Some server types, like Forge or Fabric, may have an additional .jar file present, just with "installer" added in the file name. This can also be deleted. 5. Start the Server. Once you start the server, it will regenerate the .jar file automatically. If the crashes were caused by a corrupt server .jar file, it should be fixed now. ::ProseNote{title="Custom .jar files" description="If you originally uploaded a custom .jar file to the server, it will not be regenerated automatically. You will need to reupload it manually. See our guide on this here." appearance="default"} :: --- Incompatible mods This error can happen when one or more mods are incompatible with each other or with the server type's version, which is most common on Forge servers. To check for this, try launching the modpack in singleplayer. If any mods are incompatible, the game will usually crash. --- Corrupt Mod files This error can happen when one or more of the server's mods become fully or partially corrupted. You can reinstall the affected mods to resolve the issue. This section will go over how to identify and then reinstall corrupt mods. How to identify corrupt mod files 1. Fully corrupted Mod files If a mod file becomes fully corrupted, the file will be in size. You can go through your server's folder to locate any affected mods. 2. Partially corrupted mod files While our control panel includes protections that help prevent partial uploads, it is still possible for mod files to become partially corrupted during upload or later on in the server's lifespan. In this case, the file size of the affected mods will be smaller than the original file size. If your server generated a crash report, it may list the faulty mods. You can also compare the file size of the mods on your server to the mod files on your computer, but there’s currently no other reliable way to confirm if a mod has become partially corrupted. ::ProseNote{title="Important" description="If you suspect that your mods may be partially corrupted, but are unable to identify them, we recommend reinstalling all of them with the same method you used to install the modpack." appearance="default"} :: How to reinstall individual mods 1. Shut Down your server. 2. Take note of the exact version of the mod and then delete the mod file. 3. Navigate to the original mod page and redownload the exact same version of the mod that was originally installed on the server. 4. Upload the file that you downloaded back into the server's folder. 5. Start the server. --- If you have any questions or the crash is still occurring, please contact our support team for further guidance at: https://shockbyte.com/billing/submitticket.php
Changing Modpack Versions on 3rd Party Launchers
This guide will show you how to change which Modpack Version you are using on 3rd Party Launchers such as CurseForge, Technic, FTB and ATLauncher. Whether you need to downgrade your client version to match the most recent modpack version available on our Modpack installer, or would simply like to play on an older version of your favourite modpack. This guide is here to help. --- CurseForge 1. Launch CurseForge. 2. Hover your cursor over the installed modpack you would like to switch the version of. 3. Select the ‘Change Version’ arrow beside your ‘Play’ button. 4. Tick and then click on the dropdown to choose the version you wish to use. 5. Click Continue. Curseforge will automatically begin installing the selected version of the modpack to your client. --- Technic 1. Launch Technic. 2. Click on the Modpacks tab. 3. Select the modpack you wish to switch the version of. 4. Select in the top right. 5. Tick the ‘A Specific Version’ circle and use the dropdown to select the version you’d like to use. 6. Select . This will begin installing the selected version of the modpack on your client. --- FTB 1. Launch FTB. 2. Click on the tab. 3. Click on the modpack you wish to switch the version of and select . 4. Click the dropdown at the top and select the version you wish to use. Then click the or button. 5. The FTB app will automatically begin installing the selected version. --- ATLauncher 1. Launch ATLauncher. 2. Click on the tab. 3. Find the modpack you wish to switch the version of and click . 4. Scroll through the Version to Install dropdown and select the version you’d like to use. 5. Click on the ‘Reinstall’ button. This will begin installing the selected version of the modpack to your client. --- If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php
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.