Windrose Plus Troubleshooting Guide

The dashboard will not open

Use the "Open Dashboard" link on the WindRose Plus tab. That link goes through the platform’s HTTPS proxy and is the only route in — the dashboard’s own HTTP port is firewalled to the game host, so typing an address and port into a browser will never work and is not a fault to chase.

Check the server is running. The dashboard is started by the same script that starts the game, so a stopped server has no dashboard.

Check the WindRose Plus tab is not showing "WindrosePlus is marked as enabled but the installation directory was not found on the server". That means the toggle and the disk disagree; switch it off and on again, and contact support if it comes back.

If the link loads a login page, see the section on that below — opened this way the dashboard does not ask for a password, so a login page means the request did not arrive through the platform’s proxy.

If it does not load at all with the server running, look at the Console tab for UE4SS or DLL errors — those mean the mod framework did not load, and the dashboard goes with it. Switching Windrose Plus off and on again reinstalls a fresh copy from GitHub.

Settings are not applying

Read what the panel said when you pressed "Save Changes". "Configuration saved. Changes will take effect immediately." means it is already live. "Configuration saved. Restart the server to apply changes (PAK rebuild required)." means it is not, and will not be until you restart.

The gameplay multipliers and the six INI-backed sections — player stats, co-op scaling, rest effects, swimming, shared combat effects and hearth — always need that restart, because they are compiled into an override PAK the game loads at start. Server query, admin Steam IDs, the POI scanner and the live map do not.

If a PAK-rebuild setting still has not applied after a restart, check the pak-status banner at the top of the dashboard: it says whether the override the game loaded matches the settings you saved.

wp.config and wp.multipliers in the dashboard console show what the mod is actually running with, which is the fastest way to tell a save that did not stick from a restart that did not happen.

The dashboard asks for a password

It should not. Opened with the "Open Dashboard" link, the dashboard is relayed from the game host itself and treats that relay as a caller the platform has already authenticated, so it opens straight onto the console tab on your GameGrid session. A login page means the request did not arrive that way — go back to the WindRose Plus tab and use the link there, rather than an address kept from somewhere else.

If you do have to log in, what it wants is the Windrose Plus RCON password, not your GameGrid password.

Read the current one: WindRose Plus tab, RCON / Admin Console section, press the eye icon beside the RCON Password field. The field shows "Password is set" rather than the value until you do.

To change it, type a new one and press "Save Changes". That change is flagged as needing a server restart, so restart afterwards.

Two refusals come from the dashboard rather than from a wrong password: "Set a password in windrose_plus.json to access the dashboard" means no password is set at all, and "Change the default password in windrose_plus.json" means it is still the value the mod ships with. Both are fixed by setting a password on the Windrose Plus tab.

The map is blank

Run wp.mapgen from the dashboard console, on a fresh server boot, before anything else. The landscape data it needs is only reachable before a mod hot-reload.

Player and creature positions appear even without terrain, because they are collected separately. Terrain but no POI markers is the POI scanner, not the map.

Full detail is in Windrose Plus Live Map (Sea Chart) Guide.

The toggle says one thing and the server does another

Windrose Plus is switched on and off in the database, but the server decides whether to load it from what is on disk. Those two can disagree, and the panel now tells you when they do.

"Marked as enabled but the installation directory was not found" means an install did not finish. Toggle it off and on again.

"Switched off here, but its files are still installed on the server, so the mod and its web dashboard will keep starting when the server boots" means a disable did not finish. Toggle it on and back off to remove the files.

If either warning survives a toggle cycle, open a support ticket — that needs someone to look at the host.

After a Windrose game update

Windrose Plus is a third-party mod and a game update can break it. The symptoms are the ones you would expect: the server crashes on start, or starts without the dashboard, or the commands stop working.

First, the part you do not have to worry about. A Windrose update replaces the game's own folder, and the loader Windrose Plus needs lives inside it. That loader is reinstalled automatically on your next start, before the game process is allowed to run — along with the item delivery system that sits on top of it. If everything went quiet after an update and came back on the next restart, that is what happened, and it is meant to.

GameGrid checks GitHub for new Windrose Plus releases every 30 minutes on its own schedule and pushes a new one to servers that have it enabled. That is not tied to your server restarting — restarting does not trigger a check.

There is no compatibility warning on the Windrose Plus tab. If your server will not start after a game update, switch Windrose Plus off from the tab and start the server to confirm that is the cause. A Windrose server runs perfectly well without it; you lose the dashboard, the map and the extra settings until a compatible release lands.

The releases themselves are at github.com/HumanGenome/WindrosePlus, which is where a fix will be announced. Switch Windrose Plus back on once it is out.

If the server still crashes with Windrose Plus off, the mod was not the cause — see Windrose Server Won't Start.

Shop purchases are not arriving

Work down this list. The first three are far more common than the last.

1. Is the player on the server? A Windrose purchase lands on the ground at their feet, so there has to be a pair of feet. A purchase made while offline is queued and delivered on their next session — that is normal and needs nothing from you.

2. Is Windrose Plus on? It is what publishes the player list the delivery aims at. If the Economy tab says the add-on is off, that is the answer.

3. Had the server just started? For the first few seconds after a join, or the first few after the server comes up, there is nothing in the world to deliver to yet. Those purchases queue and land by themselves.

4. Did Windrose just update? A game update can pause deliveries briefly while we adjust to the new build. Purchases are refused rather than misdelivered, we are alerted automatically, and the fix reaches your server within about half an hour with nothing restarted. There is nothing to install and no ticket to open — check Economy → Transactions afterwards and Retry anything showing as Failed.

One state is deliberately left alone. A purchase the server took but never reported back on is not retried and not refunded automatically, and is flagged for you instead — the item may already be lying at the player's feet, so retrying would give them two and refunding would give them both the item and their coins. Look at it and decide.

The full picture is in Windrose Economy and Shop.