Enshrouded Command Manager: Repeating Events
Enshrouded has no console commands, so the Command Manager gives it the one step that matters: opening a settings window on a schedule, every week, by itself.
What it can do on Enshrouded
The Command Manager runs scheduled steps against your server. On most games those steps are console commands.
Enshrouded's server accepts no commands at all, so instead of an empty command box it gets a platform step โ something GameGrid does on your behalf rather than something the game is told to do. There is exactly one, and it is the useful one:
Open a Settings Window โ apply one of your saved settings presets for a stretch of time, then put your settings back exactly as they were.
That is the Event Manager's job, on a repeating schedule. It is how you get "double XP every Saturday" without creating the event by hand each week. (For a fixed run of up to 8 weeks, the Event Manager's own Repeat option is simpler.)
The Command Manager is the Commands tab of Events in your server's sidebar.
The three things it asks for
| Field | What it means |
|---|---|
| Settings preset | Required. The preset's identifier, not its display name. Up to 64 characters |
| Starts in (minutes) | How long after the step fires the window opens. Optional |
| Window length (minutes) | How long it stays open. Optional |
Both times accept anything from 1 minute up to 10,080, which is seven days, so a weekend-long window is well within range.
Get the identifier first. /preset list in Discord lists your presets with their ids. A display name typed into this field will not match anything.
Setting up a weekly event
1. Create the preset on the Presets tab of Events and run it once by hand to check it does what you expect. A scheduled event that was never tested is a scheduled surprise.
2. Copy the preset's identifier.
3. Open the Commands tab and create a schedule.
4. Add the Open a Settings Window step, paste the identifier, and set the start delay and window length.
5. Set the schedule โ day, time and repeat.
6. Save.
From then on it runs itself. The Event Manager does the actual work, including taking a snapshot of your real settings before anything is written, so the revert puts back exactly what you had rather than a guess at it.
Two restarts, every time
Every Enshrouded settings window restarts the server twice: once when the window opens, once when it closes. The game reads its settings only at startup, so there is no way around it.
That shapes when you schedule things:
- Schedule the step so that both the opening and the closing restart fall at quiet hours.
- A short window costs the same two restarts as a long one. Longer windows are better value: an hour of double XP disrupts play as much as a whole weekend does.
Only one window at a time
This is the rule that catches people, and it is better than the alternative.
A server can have only one settings window booked or running. If a scheduled step fires while another window still holds the server, that step is refused โ it does not open a second window, and it does not queue behind the first.
So two overlapping schedules do not give you two events. They give you one event and a refusal in the history. If you run several events, make sure their windows cannot touch, and leave a gap for the closing restart.
Players are warned in Discord
Enshrouded gives a server no way to put a message on a player's screen, so the warning before each restart goes to your Discord alert channel.
If your schedule can run while people are playing, make sure that channel is set (/config alert-channel) and your players know to watch it.
Schedules that work well
| Schedule | Why it works |
|---|---|
| Double XP, Saturday morning to Sunday night | A whole weekend for two restarts, both at quiet times |
| Peaceful enemies, one weekday evening | A building night that reverts by itself |
| Faster gathering, the week after a wipe | Gets a new world moving, then stops |
| Shroud time doubled, one weekend a month | An exploration weekend โ distinctive without touching difficulty |
Checking it ran
The schedule's history shows each run and its result, paged rather than as one long list. A refused run โ the one-window rule above โ appears there with its reason.
After a window opens, GameGrid reads back the settings the server actually applied and compares them with what was asked for. If they do not match, the event is failed and your settings are put back, which is much better than a weekend quietly running on values nobody chose.
The Console shows the same thing from the server's side: the [GameGrid] lines mark the restart and the settings event. See The Enshrouded Console and Server Log.
From Discord
The bot can manage schedules too โ /command-schedule โ and the Event Manager side with /event and /preset. See The GameGrid Discord Bot on Enshrouded.
Where to go next
- Command Manager Guide โ the parts that are the same on every game
- Command Manager Variables
- Command Manager Troubleshooting
- The Enshrouded Event Manager