Help
Installing and compatibility
How to put a setup, build, config or plugin on your server, what it runs on, and what your licence allows.
Installing a server setup
A setup is a whole server in one zip. Most owners use a game panel such as Pterodactyl, so every step below says what to click there and what to do on a VPS.
- 1 Download the zip. Every purchase shows up under Account → Purchases with a download button for the latest version and every older one.
- 2 Read the README inside it first. It names the licence keys, database settings and version notes that setup needs. Fill those in before the first start, not after an error.
- 3 Upload it to an empty server. On a panel, open the File Manager, upload the zip to the server's root folder and choose Unarchive on it. On a VPS, upload it over SFTP to the server folder and unzip it there. Use a fresh server, so nothing old is mixed in.
-
4
Pick the right Java. Java 21 for Minecraft 1.21.x, Java 25 for 26.x. On a panel this is the Java image in the Startup page; on a VPS it is the
javayou launch with. - 5 Pick the server jar. Paper unless the product page says otherwise. The startup file must be the jar the README names.
-
6
Start the server and watch the console. The first start takes longer than the next ones. If it asks you to accept the Minecraft EULA, set
eula=trueineula.txtand start again. - 7 Stuck? Post your order id and the last lines of the console in the support channel on our Discord.
Installing a build or schematic
Schematics are pasted into a world with WorldEdit or FastAsyncWorldEdit (FAWE). Install one of them first.
- 1 Install WorldEdit or FAWE on your server. FAWE is the better choice for anything large.
-
2
Put the
.schemfile in the schematics folder:plugins/WorldEdit/schematics, orplugins/FastAsyncWorldEdit/schematicsfor FAWE. -
3
Load it in the game with
//schem load <name>, using the file name without the extension. -
4
Stand where it should go and paste it with
//paste -a. The-askips air, so the build does not cut a hole in the terrain around it. -
5
Wrong spot? Run
//undostraight away, move, and paste again.
Large builds: use FAWE, and generate the chunks where the build will go before you paste (a pregeneration plugin such as Chunky does this), so the paste is not waiting on world generation.
World downloads: if a product is a whole world, stop the server, drop the world folder into the server root and set level-name in server.properties to the folder's name. Then start the server.
Installing a plugin config
A config pack is the files for a plugin, not the plugin. You need the plugin it was made for, and the Dependencies tab on the product page names it.
- 1 Install the plugin the pack is for, in the version the product page lists, and start the server once so it creates its own folder.
- 2 Stop the server.
-
3
Back up the plugin's folder under
plugins/by copying it somewhere else. This is how you go back if you do not like the result. - 4 Replace the files in that folder with the ones from our download, keeping the same folder layout.
- 5 Start the server and run the plugin's own reload command if it has one. A full restart is the safest way to be sure every file was read.
Installing a plugin
Plugins are a single jar. Check the Dependencies tab on the product page first, since some need another plugin to work.
- 1 Install what it depends on and stop the server.
-
2
Drop the jar in
plugins/. -
3
Restart the server. Do not use
/reload: it can leave plugins half loaded and cause errors that a restart does not have. - 4 Check the console for the plugin enabling without errors.
-
5
Edit
config.ymlin the plugin's folder, then restart again or use the plugin's reload command.
Compatibility
What our products are made to run on.
- Server software: Paper is the one we recommend and build for. Purpur works. Spigot is for older products, and Folia only where a product page says it works there.
- Minecraft versions: 1.21.x to 26.x unless the product page says otherwise.
- Java: 21 for 1.21.x, 25 for 26.x.
- Per product: every product page lists its own versions on the Versions tab and its own requirements on the Dependencies tab. They are the final word for that product.
Licence
A purchase buys one licence for your own use: one network, one client or one project, depending on the product. Access does not expire unless the product page says the licence does. Reselling, redistributing, leaking or publishing the files ends the licence. The terms have the exact wording, and they are what applies.
Read the terms of saleRefunds
All sales are final, with one exception for products our team has abandoned. A product that does not work as its page describes gets fixed instead: report it on Discord with your order id. The terms explain both in full.
Read the terms of saleFAQ
Short answers to the things people ask before and after buying.
Straight away. Every purchase shows up under Account → Purchases with a download button for the latest version and every older version.
Yes, for as long as we maintain the product. New versions go up on the same product page and your purchase covers them. The changelog is on each product.
Yes. Reviews marked BuiltByBit were imported from the original listings there with their original dates and link back to the source. The rest were left on this store.
Discord is the place. Join our server and post in the support channel. If you need to share your order email, open a ticket instead of posting it publicly.
Same zArrowTan, same products. This store just lets us sell directly with instant delivery and without marketplace limits.
Some of our products were made with multiple contributors, and a few of them do not allow the product to be listed outside the original marketplace. Those stay off this store, but you can still find and buy them on BuiltByBit or PixelEast.
Sometimes, depending on the load. Ask on Discord with a short brief and we will tell you honestly whether we can fit it in.
Java 21 for Minecraft 1.21.x and Java 25 for 26.x. The README inside a setup names the version it was tested with, and the product page lists the Minecraft versions it supports.
Yes, and most owners do. Upload the zip in the File Manager, unarchive it, pick the Java version and the server jar the README names in the Startup page, and start the server. You do not need shell access.
Only if the Dependencies tab on the product page says so. It names every plugin the product needs and says whether each one is free or paid.
A reload can leave plugins half loaded, which causes errors that a clean restart does not have. After adding or replacing a plugin or its files, restart the server.
Many setups have a Test server tab on the product page that starts a free 30 minute server you can join in the game. You need to be signed in with a verified account.
