Skip to main content

Servers

Use a standalone server for its own exact Minecraft and loader selection. Use a linked server when a client instance needs a matching server for a test. Creating either server installs it but does not start it. Servers use temporary storage by default; choose persistent storage if you need to keep one.

Create a server​

For a standalone server, select New Server in the host list. Choose a name, Minecraft release, loader, and exact loader build if applicable. For a linked server, select Create Linked Server in the Linked servers card beside the client instance's page. It inherits the client's Minecraft and loader versions.

Choose Store persistently if needed. Automatic port starts at 25565 and picks the next locally available port when necessary; turn it off to enter a port yourself. If a modpack publishes separate server files, choose its archive under Server files (optional). For a standalone server, the dialog fills in the Minecraft release, loader, and build the archive's file names state, and Create Server stays unavailable while the selection disagrees with the archive, for example Vanilla for an archive that carries mods. A linked server keeps its client's versions, and server files that do not fit them are refused when you create it. Select Create Server and wait for the installation to finish.

You can also select Also create a linked server while creating an instance or importing a modpack. New servers start with the server property defaults.

A linked server is rebuilt from the client's retained pack recipe. JARs added manually to the client afterward are not copied automatically. A mod change made through the desktop app's mod dialogs can be carried to the linked servers you select; see Mods. Any Forge or NeoForge server, linked or standalone, can also take catalog mods directly and change or remove its own; see Install mods on a server. Pack files whose server side is undeclared are included by default; the CLI can narrow them with repeated --include-unknown PATH flags or omit them with --skip-unknown. Review the server's Mods tab before starting a test.

Review the Minecraft EULA​

Server starts require explicit Minecraft Server EULA consent. Creating a server, importing a pack, and launching a client do not grant it. Consent is recorded for Ephervex's servers, rather than separately for each server.

Open the server's Properties tab. In the Minecraft Server EULA card, select Review & Accept, read the agreement, and confirm if you agree. The card shows the recorded status.

1 marks the EULA action on the server's Properties page.

Starting a server without consent is refused before anything runs. The notice says The server was not started and offers Review Minecraft EULA, which opens the agreement. Diagnostics also checks for consent.

Change server properties​

Localhost limits the server to this computer. Choose LAN for other devices on the local network, or Custom to bind to a specific IP address. Custom bind addresses must be IP addresses, not hostnames.

warning

Keep Online mode on when exposing a server beyond localhost. Ephervex flags an exposed offline-mode server as unsafe.

Open Properties. The Network card holds Access, Port, and Online mode. Under Server settings, the World, Gameplay, Players, and Performance cards list most other server.properties keys, each with a short description; turn on Show advanced for the Advanced card. A key the file does not hold shows the value the server uses instead. Once the server has written its full file, keys its release does not read are hidden. Keys without a row, such as remote administration settings, keep what the file holds.

An edited row shows Changed, and a value the server would not accept shows why. The bar at the bottom counts unsaved changes. Select Save Changes to save them or Discard Changes to drop them.

You can also save while the server runs under Ephervex. Saving does not restart it: until it restarts, the header, Overview, and each saved row show Restart required. Network settings can be changed only while the server is stopped.

1 marks Access, where you choose who can connect.

1 marks Online mode. The example warns because it is off while LAN access is selected.

note

Values saved while the server runs are written again just before it next starts. An edit made to those keys in server.properties outside Ephervex in the meantime, or by the server itself, is replaced.

Set the server's Java and memory​

A server picks its Java, memory, and JVM arguments the same way an instance does; see Set Java and memory for one instance. Stop the server before changing them.

Open the server's Settings tab, or select the Java pill in the workspace header. Java and memory and the Java runtime card work as they do in an instance's Settings. The same tab holds Independent mod changes.

Run the server and use its console​

Open the server workspace from the host list or its linked client. Select Start. The header shows its address and port, and the Overview shows its runtime state. Open Console to watch output and send a command. Use Stop for a graceful shutdown or Restart to stop and start it again. Force Kill is available if it cannot stop normally. The console starts over with only the new run's output whenever the server starts, including Launch Client & Connect, a paired launch, and Restart. Quitting the desktop app stops every server it started: it requests a graceful stop first and kills a server that does not exit.

Launch a linked client and connect​

On a client's page, find its linked server in the Linked servers card and select Launch Client & Connect. Ephervex starts the server if needed, waits for it to accept connections, then launches the client and connects it. The server remains running after the client exits; stop it separately when the test is done.

Start together is a separate pairing option for a client and server. Use Launch Client & Connect when the client should join the linked server directly.

Mark a favorite or set an icon​

Favorites are listed first in the host list. Select the star beside a server's name, or use Add to favorites and Choose icon... in its card menu. On the command line, use server favorite SERVER_ID, server unfavorite SERVER_ID, and server icon SERVER_ID IMAGE_FILE or --clear. Icons follow the instance icon limits.

Recover a server after an interruption​

If Ephervex or the machine stops unexpectedly, the server may have recorded runtime state that needs review. Check its status before trying to start it again. Ephervex clears that state only when it can prove every recorded process has stopped; it will not take over a possibly live server process.

Open the server's Overview. If it says the server needs attention, select Repair. If repair is refused because a process may still be running, inspect and stop that process before trying again. The server can be started after stale state is cleared.