Palworld Server Manager
Windows app-
1.14.0 Current version
- The Plugins page used to describe your files, and therefore what should happen.
- Each plugin reports its last start. Loaded, turned off in its own file, invalid or unreadable info file, engine too old, entry point not found, crashed during its own start-up, or missing…
- The case that made the page lie is fixed. A plugin that looked perfect on disk but collapsed while initialising was still shown as healthy. Not any more.
-
1.13.1
- A fix for a confusing regression reported right after 1.13.0.
- Your server window was gone. With "Start this server with PalApi" ticked, no console window opened any more.
- Why it happened. The manager has always asked the program it starts not to open a window.
-
1.13.0
- The Plugins page no longer stops at "is the PalApi engine installed?".
- Every installed plugin is listed. Name, version, folder, and what it requires.
- No empty promises. As long as "Start this server with PalApi" is unticked, or the engine is not installed, no line claims a plugin will load.
-
1.12.0
- Server plugins: install the PalApi engine and let your server actually load them.
- New "Plugins" section for each server. It installs, updates, repairs or removes the PalApi plugin engine in one click, the same way the other server add-ons are handled.
- A checkbox: "Start this server with PalApi". Without it, plugins sit on the disk and never start — this is the trap that silently affected servers with plugins installed.
-
1.11.3
- The app no longer locks up behind a pile of error windows: one is shown at a time, the rest go to the log.
- The cause is gone — the event watcher no longer queries the database when no event is running.
- Rolling back an expired event is retried on the next pass instead of being abandoned when the write fails.