Windrose Command Manager

Read this first

Windrose has no broadcast, say, or chat command of any kind. Not one is missing from the catalog - the game does not have one. No Windrose schedule can put text in front of a player, ever.

This is the single thing to understand before you plan anything, because almost every scheduling pattern from other games starts with "warn the players first". On Windrose that warning has to go somewhere else: a Discord message, your server description, or your community's own channels.

What Windrose is unusually good at instead is keeping a record. Its command set is rich in things that report state - status, uptime, multipliers, creature and entity counts, performance, memory, network connections.

A schedule that runs one of those hourly turns your execution history into a timeline of how the server actually behaved. When a world starts running badly, the before-and-after is already sitting there.

At a glance

The Command Manager runs Windrose Plus commands for you on a repeating schedule. You pick one from a list, fill in its parameters, choose when it runs, and save.

It is one of two tabs on the Event Manager page. Config Events change settings and restart the server for a while; the Command Manager sends commands and restarts nothing.

Your first schedule

1. Open your server, click Event Manager, then the Command Manager tab.

2. Click + New Schedule.

3. Name it Hourly Status, pick Server Status, choose Hourly.

4. Click Create, then Run Now, then Log.

5. The log row holds the server's own status output. In a week, that history is a timeline.

On Windrose the history *is* the product. Unlike other games, where a schedule mostly changes something, most of the value here is in what the schedule records.

The 25 commands

Server state - the ones worth running on a repeat

Show Configuration prints your settings in full apart from the RCON password. If you schedule it, remember the execution history is readable by anyone with panel access to the server.

World

Diagnostics

Players - read-only

Players - these change the game

The last three persist. If you schedule an event that raises movement speed, schedule the one that puts it back to 1.0 as well - otherwise every player who does not reconnect stays fast indefinitely. And teleporting somebody mid-fight or mid-sail loses them whatever they were doing, with no way to warn them first on this game.

Custom

Custom Command sends whatever you type, unchecked. The debug commands - wp.peek, wp.props, wp.nativeprobe and the wp.gg.* family - read live engine memory and are for support use on a test server, not for a schedule on a world people play on.

Running a command for everyone online

Nine commands take a player: Player Info, Position, Health, Stamina, Playtime, Teleport, Speed, Jump and Gravity. Each shows an Send to every online player checkbox beside the player field.

Tick it and you type nobody's name. When the schedule fires we read the roster with wp.players and send the command once per person. A timed "fast weekend", or an "everyone to the harbour" event, becomes one schedule instead of one per player.

Names, spaces, and quotes

Windrose is the only game we host whose roster has no numeric handle to offer. wp.players returns names and nothing else, so names are what the expansion has to use.

Multi-word names do work - send them unquoted. This is measured behaviour, not a guess:

wp.playerinfo Captain Ada     → finds the player
wp.playerinfo "Captain Ada"   → not found

Windrose Plus treats the quote characters as part of the name it is looking for, so adding them makes it worse, not better.

If your server has players with spaces in their names, prefer the read-only commands on a schedule and run the movement ones by hand.

What happens in each case

Seven commands are deliberately not in the catalog

wp.kick, wp.ban, wp.unban, wp.listbans, wp.givestats, wp.time and wp.weather are all real Windrose Plus commands, and none is offered here. Each was measured against a live server.

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.

Custom Command will still send any of them if you insist, and they will still not do what you want. The full measurement is in Windrose Admin Commands Reference.

Do not schedule Generate Live Map Terrain

Generate Live Map Terrain (wp.mapgen) works only on a fresh boot. UE4SS caching means the landscape cannot be found once the mod has hot-reloaded, so a second run in the same server session does nothing useful.

Run it once by hand after a restart if your live map needs regenerating.

On a repeating schedule it will succeed the first time and then quietly achieve nothing - which is exactly the shape of problem that wastes an afternoon.

Schedules worth building

A slowdown watch, every six hours

When somebody reports the world running badly, you already have the readings from before it started.

A timed movement event

Announce both in Discord. The game itself cannot tell anyone.

Reading the history

Click Log for the last 50 runs, each with the command sent, the output Windrose Plus returned, and a status.

Each status and what to check: Command Manager Troubleshooting.

Everything else a schedule can do

Multi-step sequences, waits, run conditions, overlap policy, catch-up windows, start spread and missed-run alerts work the same on every game.