Free Minecraft server hosting by Ametistos.

Start with the Minecraft version your players actually use, then select server software that publishes a compatible build. Vanilla follows the official game. Paper, Spigot, Bukkit and Folia focus on plugin-based servers, while Fabric, Forge and NeoForge support different mod ecosystems. Mohist combines approaches but requires additional compatibility checks. A newer version is not automatically the best choice for an established world: verify plugins, mods, Java requirements and world-format changes before upgrading. Keeping the game version, loader and extensions aligned prevents many startup failures before the first launch.

Minecraft memory requirements depend on more than the number of connected players. World generation, view distance, simulation distance, entities, farms, plugins, mods and the selected server version can all change consumption. Begin with a modest configuration, watch live memory and CPU data while people play, and increase resources only after confirming a real limit. Too little RAM can cause pauses or crashes, but assigning more memory cannot repair an incompatible plugin or a slow world task. Ametistos keeps the configured memory and estimated credit runtime together so performance and cost can be evaluated as one decision.

View distance and simulation distance are two of the most useful performance controls. A large view distance sends more chunks to every player, while simulation distance keeps more chunks active for mobs, crops and redstone. Lowering either value can reduce memory use and server tick work without changing the world files. Also inspect entity farms, constantly loaded chunks and extensions that run frequent tasks. Use the console and logs to identify what changed before increasing RAM. Resource upgrades help when the server is genuinely constrained, but careful settings usually produce a more stable result than treating every lag spike as a hardware problem.

A plugin must support the Minecraft version, the server software and any required dependency plugins. Read the project release notes instead of relying only on the plugin name. Install one major change at a time, restart the server when requested and check the earliest related message in the console. A warning can explain a missing optional feature, while an exception or disabled-plugin message usually needs attention. Never place client-only mods in the plugins folder, and avoid files from unverified mirrors. Before replacing a plugin that stores player or world data, download its configuration and data directory so the previous state can be recovered manually.

Fabric, Forge and NeoForge are separate loaders; a mod built for one is not automatically usable with another. Players normally need the same loader version and compatible client-side mods as the server. Check every project's supported Minecraft release, loader, dependencies and configuration instructions before upload. Add mods in small groups and preserve a known working set so a failure can be isolated. Modded worlds may contain blocks, items and dimensions that disappear or become invalid when a mod is removed. Changing loader or server type can therefore require a full reset, making a local world copy essential before experimenting with a different configuration.

The Files workspace exposes the data that defines the world and server behavior. Stop the server before replacing important world, configuration or extension files so the running process cannot overwrite the upload. File deletion and full server reset are irreversible operations in the panel. A reset removes the existing server state to prepare a clean installation; it is not the same as a restart. Automatic backups are planned after the MVP and are not currently an alpha feature. Download important worlds, player data and configuration before software changes, datapack changes, deletions or resets, and verify that the downloaded archive opens before relying on it.

Use the Access area when another person needs to help manage a server. Invite an existing Ametistos account and grant only the permissions required for that role, such as server controls, settings, files or console access. A builder who only needs to start the world does not necessarily need permission to delete files or execute administrative commands. Review access after a project or event ends and remove accounts that no longer need it. Keep the owner password and authentication token private, confirm the account email and use a strong unique password. Scoped access creates a clearer activity boundary and limits the damage caused by a mistaken action.

When a Minecraft server does not reach online status, read the console from the beginning of the failed start instead of focusing on the final shutdown message. The first relevant exception often identifies an unsupported Java version, invalid configuration, missing dependency, damaged file or incompatible plugin or mod. Compare the current launch with the last working change and temporarily remove only the suspected addition. Repeatedly pressing Start does not repair a deterministic configuration failure. Check memory limits, software and game versions, then use logs for the complete trace. Full reset should remain the final option after important data has been downloaded.

Stop the source server and create a complete local copy before migration. Record the Minecraft version, server software, loader build, seed, plugins, mods and datapacks used by the world. Create a matching destination configuration before uploading data; opening a world with a different version or missing content can permanently transform chunks and player inventories. Confirm the correct world folder name and keep dimension folders in the structure expected by the selected software. Start the migrated server privately, inspect the console and visit important locations before inviting players. Retain the untouched source copy until inventories, dimensions, permissions and gameplay behavior have been verified.

Set a recognizable MOTD, game mode, difficulty, player limit, spawn protection, whitelist and operator list before publishing the address. Test joining with a normal player account so permissions are evaluated without owner privileges. Confirm that the server automatically stops according to the intended empty-player timeout and that collaborators have only their required access. Review estimated playtime after the final RAM choice, because active sessions consume credits according to configured memory. Finally, document the Minecraft version and any required client mods for players. A short launch checklist prevents avoidable connection questions and makes the first shared session easier to support.