Abandoned Bunkers
How to track open and next-to-open abandoned bunkers, configure in-game and Discord notifications, and read snapshot freshness correctly.
On this page
The Abandoned Bunkers module regularly reads the status of abandoned bunkers from a safe copy of the SCUM save database and displays which bunkers are open and which will be opened next. It can maintain one current Discord message and notify players directly in-game when a bunker is opened.
The administrator does not need to recalculate game timers or manually edit Discord every few minutes. However, the module displays the observed state; for old or erroneous data, the freshness must be visible.
Where to find it
SCUM → Abandoned Bunkers contains everything on one page:
- module status and last data collection,
- open bunker settings and the next check,
- Discord template and rows of open/upcoming bunkers,
- one-time game message and optional recurring reminder,
- up-to-date list of bunkers and recent data collections.
You open the webhook with the common button in the header. webhook URL is not saved in bunker settings.
How to read bunker status
- Open: the bunker is open according to the latest fresh snapshot. Shows closing time and remaining time.
- Waiting: the system recognizes the future opening and displays the deadline and countdown.
- Inactive: the bunker is currently not open and does not have a sufficiently known next date.
A zero or unclear game timer is not considered an open bunker. The module anchors the stable timer to the absolute time so that the same countdown does not start over with each ten-minute collection.
What you can set
- Module Enabled: determines whether NODERAgent should collect bunker data.
- Active length: how long an open bunker is considered active.
- Settle delay: a short wait after transition for the state to stabilize.
- Number of next openings: how many waiting bunkers will be displayed.
- Discord: main template, separate row for open bunker and separate row for next opening.
- In-game message: SendChat or Announce, named color and multi-line template.
- Repeated reminder: a separate template and an interval of 5 to 1440 minutes while the bunker remains open.
SendChat sends each non-blank line separately and uses the selected color. Announce creates a single one-line global announcement and does not use the SendChat color. In both cases, this is a message for all online players, not a private channel.
Recommended setup procedure
- Select a server and turn on bunker data collection. The standard check interval is fixed at 10 minutes; the system can schedule an earlier check around opening or closing.
- Wait for successful data collection and check the number of lines, open and waiting bunkers.
- Turn on Discord and edit the main text. Choose variables from the picker next to the field; the sector name is more suitable for players than the internal bunker ID.
- Set a one-time game message when opening. The message is sent only on a known transition from unopened to open state, not on the first loading of an already open bunker.
- If you want reminders, choose a long enough interval. With a 24-hour opening, 60-120 minutes is usually more readable than every few minutes.
- Save and track the next real transition. Compare the time in administration, the in-game message, and Discord.
Available Player Variables
Game messages support for example {sector}, {opened_time}, {closes_time}, {remaining_time} and {server_name}. Discord rows additionally offer the time of the next opening and the remaining time. Use the exact tokens from the modal; a typo cannot be replaced.
Example from the Main server
Collection from 1 September 2026 at 16:55 local server time.
| Area | Main example |
|---|---|
| Module Status | Data collection, Discord and in-game notifications enabled. Last collection "ok", Discord "sent". |
| Freshness | 15 bunker lines; next check scheduled in 10 minutes. |
| Current status | 1 open bunker in sector D1, 2 waiting (A1 and A3), 12 inactive. |
| Active length | 24 hours, settle delay 60 seconds, show up to 6 more openings. |
| One-time message | "Abandoned bunker in {sector} has just opened. It will close in {remaining_time}." |
| Reminder | On every 120 minutes: "Abandoned bunker in {sector} is open for {remaining_time}." |
This example is a historical overview. Always verify the currently open sector in the admin or in the fresh Discord message.
Frequent problems
- The status is not updating: check if the module is on, the last collection and its error. The page does not have a manual refresh button; the agent and backend manage their own schedule.
- Discord shows the last known state after the error: this is intentional, but must also indicate a failed collection. Old content should not appear fresh.
- There was no message when opening: the first collection could have found the bunker already open. The notification is sent only when the transition is observed.
- The reminder didn't come exactly to the minute: the schedule is tied to collection intervals and time windows; missed old windows are not replayed.
- Color changed the audience: it didn't. Color is only the appearance of global SendChat; does not specify recipients.