1. Choose the right server
Select Palworld Dedicated Server rather than a Minecraft profile. Players need a compatible Palworld client and a platform that supports the chosen server connection. This Windows server uses a native executable and game UDP traffic, not Java or Minecraft plugins. Consult Pocketpair's current requirements before choosing player count or memory. A PC diagnosis is a starting point, not a guarantee of how many people can play.
2. Create it in TomoNode
Open New server, select Palworld and choose a dedicated folder. Review the game UDP port and the separate REST management TCP port. TomoNode's implementation downloads official SteamCMD and installs the dedicated server for Steam App 2394010. Allow time and disk space for downloading the game files. Start the server only after installation completes. If setup fails, keep the error message and check free storage, download access and whether another process already uses the selected port.
3. Test locally before inviting friends
First test a compatible client on the host PC using the configured game port, then test a second LAN device using the host's private IPv4 address. For remote players, forward only the game UDP port to that PC when your router and provider permit it. A Minecraft TCP relay setup does not automatically support Palworld UDP. Check the relay's protocol support and service conditions first. Do not expose the REST management TCP port through a router, tunnel or public VPN. An open game port alone does not prove successful client participation.
4. Add content and change settings safely
Use Palworld settings rather than Minecraft extensions. Keep the server and clients on compatible versions. TomoNode reads state and player information through a local REST connection to 127.0.0.1. That does not guarantee PalServer itself is bound only to loopback; block external access to its management port. Treat PalWorldSettings.ini as sensitive because Palworld may require the admin password there. Before updating, stop safely and preserve the world and configuration. TomoNode is not affiliated with Pocketpair or Valve.
5. Make a backup you can restore
Record which server, version and folder the backup belongs to. For a consistent manual copy, save the world and stop the server first. Keep the world, configuration and required extension files together; a copy on the same disk does not protect against disk failure. For an app backup, wait for completion and verify the entry appears. Before restoring, stop the server and preserve its current state. Select the intended backup and check its date and integrity result. Start the restored server and confirm a known build or inventory in the game before treating recovery as successful. Do not depend on scheduled backups while the scheduling UI remains in development.
6. Find the cause before changing more settings
For startup failures, read the first relevant PalServer.exe error in the startup log. Separate an unfinished SteamCMD download from a server that was installed but fails to start. For download failures, check free disk space, write access to the selected folder and the connection to the official distribution service before retrying; preserve the world and settings instead of reinstalling over them. Confirm the configured game UDP port is not already in use. Test a compatible client on the host PC first, then a second LAN device, then an external connection. If only external access fails, check the UDP forwarding destination, firewall rule, CGNAT or double NAT and the relay's UDP support. Never forward the REST management port or disable the whole firewall. Keep server and client versions compatible. For lag, compare CPU, memory and disk activity at the time of the problem and change one server setting at a time. Send only the app/server versions, steps and a redacted error excerpt to support, not passwords, IP addresses, player details or a full world.