Windrose Admin Commands Reference
Every Windrose Plus console command, grouped by what it is for, including the ones that report success and change nothing, and which of them can be put on a schedule.
Where these run
These are Windrose Plus commands, not Windrose commands. A Windrose dedicated server has no admin command system of its own — without Windrose Plus there is nothing to type them into. See How to Become Admin on Your Windrose Server.
They run in the console tab of the Windrose Plus dashboard, which you open with the "Open Dashboard" link on the WindRose Plus tab. There is no password to type: the link carries your GameGrid session, and only an account with access to this server can open it.
Running a command needs more than opening it. An account that can only view the server sees the console and its log but cannot send anything; running a command needs the permission that lets you change the server’s settings.
The console has autocomplete and a command reference panel you can expand. wp.help lists the commands grouped by category, wp.help all adds the debug ones, and wp.help <command> gives the usage for one.
The list below is the current release. New commands arrive with Windrose Plus updates, so wp.help on your own server is always the authoritative list.
Server state
wp.status — server status and the active multipliers.
wp.version — the Windrose Plus version.
wp.uptime — how long the server has been up.
wp.multipliers — the multipliers currently applied.
wp.config — the current Windrose Plus configuration. The RCON password is masked.
wp.time and wp.weather — measured against a live server, these return a raw object pointer rather than the time or the weather. There is no reading to be had from either, which is why neither is offered in the Command Manager.
wp.reload — reload the Windrose Plus configuration.
Players
wp.players — everyone online, each with the actor ID that other commands take.
wp.playerinfo [player] — one player in detail.
wp.pos [player] — a player’s position. wp.tp — teleport.
wp.health [player] and wp.stamina [player] — current values.
wp.playtime [player] — time played.
wp.givestats <player> <stat_count> [talent_count] — reports that it granted stat and talent points, and writes an audit note saying so. Measured against a live server, the player’s stats and talent points are unchanged. Treat it as a note to yourself, not as a way to grant points.
wp.gm, wp.speed, wp.jump and wp.gravity — the movement and mode toggles.
wp.connections — current connections.
Moderation — what these really do
wp.kick, wp.ban, wp.unban and wp.listbans exist and accept their arguments. All four were measured against a live server, and what they do is not what their names promise.
wp.kick removes nobody. The native component it depends on is not installed or enabled by the current Windrose Plus release, so the request is queued and nothing consumes it. Worse, it reports success for any name you type, including a name that has never connected — so the success line proves nothing. Confirm with wp.players: if the player is still listed, nothing happened.
wp.ban and wp.unban report success the same way, for players who do not exist as readily as for players who do. What they genuinely do is maintain Windrose Plus’s own ban list: a ban added with wp.ban comes back from wp.listbans, and wp.unban takes it out again. That list round-trips correctly.
What the list does not do is keep anybody out. Nothing checks it when a player connects, so it is a record you are keeping for yourself rather than access control. A banned player can rejoin.
There is no way to remove a player from a Windrose server from the console. Your real access control is the server password and the invite code on the Settings tab: change the password and restart to lock everyone out, then hand the new one to the people you want.
None of the four is offered in the Command Manager, and that is deliberate. A scheduled command that reports success and changes nothing is worse than no command at all — it puts a green tick in your execution history for work that never happened.
World and map
wp.mapgen — generate the Sea Chart’s terrain heightmap from the world’s landscape actors. It reports what it found, for example "Heightmap exported: 4 landscapes, 16384 vertices". Run it on a fresh server boot before any mod hot-reload; UE4SS caching stops the landscape being found afterwards.
wp.mapexport — the lower-level export, writing raw heightfield data for the tile generator. wp.mapgen is the one to use.
wp.creatures and wp.entities — what is spawned in the world and where.
wp.discover — world discovery data.
Diagnostics
wp.memory — the server process’s memory use. wp.perf — performance counters. wp.health — the mod’s own health check.
wp.doctor — a self-check of the Windrose Plus installation.
wp.modreload — reload Lua mods.
wp.inspect, wp.peek, wp.props, wp.fields, wp.methods, wp.probe_player, wp.settings and wp.nativeprobe are debug and research commands, hidden from wp.help unless you ask for wp.help all. wp.nativeprobe enables an experimental native component and should only be used on a test server.
For CPU and memory over time, the Resource Usage card on your server’s Overview tab is better than wp.memory: it shows the game process’s own CPU, memory, network and thread counts, refreshed every 10 seconds. The Windrose Plus dashboard has no performance graphs.
Running these on a schedule
Any of these commands can be put on a repeating schedule from the Command Manager tab on the Event Manager page — hourly status lines, entity and performance snapshots every few hours, a weekly support snapshot, or a movement event pointed at everyone online at once.
The thing to know before planning anything: Windrose has no broadcast, say or chat command of any kind. No schedule can warn a Windrose server that it is about to restart, because there is nothing to warn it with. That message has to go out in Discord or in the server description.
What scheduling Windrose is genuinely good at is keeping a record, and that — along with the 25 schedulable commands, the Send to every online player behaviour on names with spaces, and the commands that should never be put on a repeat — is covered in Windrose Command Manager.
What is not done here
Gameplay values — multipliers, player stats, co-op scaling, combat effects — are changed on the WindRose Plus tab in the panel, not from the console. The panel validates them and tells you whether a restart is needed.
Server settings — name, password, player limit, world, region, invite code — are on the Settings tab.
Admin recognition is the Admin Steam IDs list on the WindRose Plus tab, not a console command.