Server Update Notifications ​

Intermediate40-60 minutesWindowsUnturned ServerNotepad++

The Unturned™ dedicated server receives updates through the Steam publishing pipeline, but the server itself does not notify its operator when a new version is available. The operator must either poll the Steam backend manually -- checking the Steam News Hub, monitoring the server's console for update-detection messages, or relying on third-party tools -- or subscribe to one of the two automated notification channels that the Smartly Dressed Games team provides: the Discord webhook feed or the RSS feed. Both channels publish the game version number and the Steam build ID for every update, giving the operator the information needed to decide whether to schedule a restart.

This article is the 57 Studios™ reference for the Unturned™ dedicated server update notification system. It covers the Discord notification channel in the official Unturned™ Discord server, the RSS feed hosted on the Smartly Dressed Games website, how to interpret the version number and build ID that each notification includes, and how to integrate the notification feed into a server operator's monitoring workflow. Server operators who configure update notifications eliminate the information gap between an update being published and the operator knowing that the update exists.

Discord message in the dedicated-server-updates channel showing an Unturned update notification with version number and build ID

The screenshot above shows the typical format of a Discord notification message in the dedicated-server-updates channel. The message contains the version number and build ID in a structured embedded field layout that is easy to scan at a glance.

Documentation source: The notification channels documented in this article are drawn from the official Smartly Dressed Games modding documentation.

Who this article is for ​

This article is written for Unturned™ dedicated server operators who want to receive timely notifications about server software updates. Familiarity with Discord and RSS feed readers is assumed. If you have not yet installed a dedicated server, start with Setting Up Your Server Panel and return here after your server is running.

What you will learn ​

  • Where to find update notifications in the official Unturned™ Discord server
  • How to subscribe to the dedicated server updates RSS feed
  • How to interpret the game version number and Steam build ID in each notification
  • How to choose between the Discord channel and the RSS feed for your monitoring setup
  • How to combine update notifications with the server's auto-restart system for fully automated updates
  • How to verify whether your server is running the latest published version

Background: how update notifications work ​

The Unturned™ dedicated server is a separate Steam application (App ID 1110390) from the base game (App ID 304930). When the SDG team publishes an update, the new version is pushed through Steam's publishing pipeline, which updates both the game client and the dedicated server tool. The update triggers a new Steam build ID -- a numeric identifier that increments with every push -- and a new game version number that follows the standard semantic versioning pattern used by Unturned™.

The update notification system has no direct connection to the server process itself. The server does not poll the notification feed; the notification feed is consumed by the operator, who then decides whether to apply the update. The server's own update-monitoring system (the Enable_Update_Shutdown feature in Config.json) checks for changes in Workshop content, not for changes in the server software version. These are two separate systems.

The SDG team provides two channels for receiving update notifications:

  1. A Discord webhook feed in the official Unturned™ Discord server, in the #dedicated-server-updates text channel. Each message includes the game version number and the Steam build ID.
  2. An RSS feed hosted on the Smartly Dressed Games website, at https://smartlydressedgames.com/rss/unturned-steam-dedicated-server-updates.xml. Each feed entry includes the game version number and the Steam build ID.

Both channels are updated simultaneously when a new version is published. There is no delay between the Discord notification and the RSS notification -- both are triggered by the same publishing event.

The flowchart above shows the notification delivery chain. The SDG publishing event triggers both the Discord and RSS channels simultaneously. The server operator receives the notification through whichever channel they are monitoring, evaluates the update, and decides whether to restart the server.

Discord notification channel ​

The primary notification channel is the #dedicated-server-updates text channel in the official Unturned™ Discord server. Anyone who joins the official Unturned™ Discord server can access this channel and receive notifications. The channel is read-only for non-staff members -- only the webhook posts messages, and members cannot send messages to the channel.

Each notification message in the channel includes:

  • The game version number in the standard Unturned™ format (e.g., 3.25.9.2). This is the version number that appears in the game client's title bar and in the server browser.
  • The Steam build ID (e.g., 14327654). This is the numeric identifier that Steam assigns to the build when it is published. The build ID increments with every push, including pushes that do not change the version number (such as hotfixes that only change the dedicated server without changing the client version).

The notification message format is a webhook post with an embedded fields layout. The two fields are clearly labeled, making it simple to scan the channel history for the latest version.

To access the Discord channel:

  1. Join the official Unturned™ Discord server. The invite link is available on the Unturned™ Steam store page or through the SDG website.
  2. Navigate to the #dedicated-server-updates channel in the channel list under the Server Updates category.
  3. Read the most recent message to see the latest version number and build ID.

The channel posts a new message for every publishing event. A single Unturned™ update that goes through multiple publish iterations (e.g., a beta publish followed by a stable publish) will produce multiple messages. The operator should check the timestamp on each message to identify the most recent one.

Discord notification advantages ​

AdvantageDescription
Real-time deliveryDiscord push notifications arrive on mobile and desktop within seconds of the webhook firing
No polling requiredThe notification appears automatically in the channel; the operator does not need to check manually
Historical recordThe channel maintains a scrollable history of past updates with version numbers and build IDs
Community contextOther server operators in the Discord server may discuss the update in adjacent channels, providing additional context
Free and accessibleThe Discord server is free to join and the notification channel is openly accessible to all members

Discord notification disadvantages ​

DisadvantageDescription
Requires Discord accountOperators who do not use Discord must create an account and join the server
Notification overloadOperators in many Discord servers may miss the notification among other messages
No automated processingThe notification cannot be directly consumed by a script or monitoring tool without additional integration

RSS notification feed ​

The RSS notification feed is an alternative to the Discord channel for operators who prefer standards-based feed aggregation or who want to integrate the notification into an automated monitoring pipeline.

The RSS feed URL is:

https://smartlydressedgames.com/rss/unturned-steam-dedicated-server-updates.xml

Each feed entry corresponds to a publishing event. The entry contains:

  • A title that includes the game version number (e.g., "Unturned Dedicated Server 3.25.9.2").
  • A description that includes the Steam build ID alongside the version number.
  • A publication date that records when the update was published.

The RSS feed can be consumed by any RSS reader application, by server monitoring tools that support RSS ingestion, or by custom scripts that parse the XML at a polling interval. The feed does not require authentication and is publicly accessible.

RSS feed advantages ​

AdvantageDescription
Standards-basedRSS is a well-established format supported by hundreds of applications and libraries
Machine-readableThe XML format can be parsed by scripts for automated monitoring and alerting
No account requiredThe feed is publicly accessible without authentication
Cross-platformRSS readers are available for every operating system and mobile platform
Self-hostableOperators can configure their own monitoring tools to poll the feed at a custom interval

RSS feed disadvantages ​

DisadvantageDescription
Requires pollingThe operator must poll the feed at an interval to detect new entries. Push notifications are not available through RSS natively
No community contextThe feed contains only the version number and build ID without any discussion or release notes
Reader dependencyThe operator must have an RSS reader or a script that consumes the feed, adding one more tool to the monitoring stack

Choosing between Discord and RSS ​

The choice between the two notification channels depends on the operator's existing monitoring setup and preferences.

ConsiderationDiscord recommendedRSS recommended
Primary communication toolOperator already uses Discord for server communityOperator does not use Discord or prefers email-style notifications
Monitoring automationOperator monitors notifications manuallyOperator has a monitoring script that processes feed entries
Alerting requirementsOperator wants real-time push notifications on mobileOperator checks for updates on a daily or per-shift schedule
Infrastructure complexityOperator wants zero-configuration setupOperator already maintains RSS-consuming monitoring infrastructure
Historical trackingOperator wants a scrollable history of past updatesOperator maintains their own changelog database
Cost sensitivityDiscord is free and requires only an accountRSS readers are free but may require additional tooling for automated alerting

The 57 Studios™ recommendation is to use both channels. Subscribe to the Discord channel for real-time awareness and the RSS feed for integration with any automated monitoring tools. The cost of maintaining both subscriptions is zero (both are free), and having both provides redundancy in case one channel experiences downtime.

Interpreting version numbers and build IDs ​

Each notification includes two identifiers that together describe the update precisely.

Game version number ​

The version number follows the four-part format MAJOR.MINOR.PATCH.BUILD (e.g., 3.25.9.2). The four components are:

  • MAJOR (3): The major version of Unturned™. This has been 3 for the current generation of the game and changes only during a major engine or architecture overhaul.
  • MINOR (25): The minor version, which increments with significant content updates that add new features, maps, or systems.
  • PATCH (9): The patch version, which increments with bug fixes, balance changes, and smaller feature additions.
  • BUILD (2): The build number within the patch, which increments with hotfixes and emergency updates.

The version number is the primary identifier that the server operator uses to determine whether a restart is needed. If the server is running 3.25.9.1 and the notification reports 3.25.9.2, the operator knows that a minor hotfix has been published and a restart will apply the fix.

Steam build ID ​

The Steam build ID is a numeric identifier that Steam assigns to every publish event. It is a monotonically increasing integer: build ID 14327654 is newer than build ID 14327653. The build ID is the authoritative identifier for the exact binary and asset set that the server will download when it runs SteamCMD with +app_update 1110390.

The build ID is useful for operators who want to verify that the server's current installation matches the latest published version without relying on the version number alone. Some updates change the build ID without changing the version number (for example, a dedicated-server-only hotfix that does not change the game client version). In such cases, the build ID is the only indicator that an update is available.

Verifying the server's current version ​

To determine which version the server is currently running, check the server console output at startup or use the @version command (if available on your server version). The startup log includes the game version number in a line approximately:

Version: 3.25.9.2 (Build ID: 14327654)

Compare this version number and build ID against the latest notification from Discord or the RSS feed. If they match, the server is running the latest published version. If they differ, an update is available and a restart will apply it.

For servers running auto-restart wrapper scripts that include the SteamCMD update step, the update is applied automatically on the next restart regardless of whether the operator checks the version. The operator should verify after the restart that the version number has incremented to the expected value, because a SteamCMD failure during the update step would leave the server on the old version.

Combining update notifications with the auto-restart system ​

The update notification system (Discord and RSS) and the server auto-restart system (Enable_Update_Shutdown in Config.json) are complementary but independent. The notification system tells the operator that an update exists. The auto-restart system watches for Workshop content changes and can trigger a shutdown when a Workshop item updates, but it does not monitor the server software version.

The recommended workflow for keeping the server software up to date:

  1. Subscribe to the Discord channel or RSS feed to receive notifications when a new version is published.
  2. Read the update notification and evaluate whether the update requires immediate application (security fix, critical bug fix) or can wait for the next scheduled restart.
  3. If immediate application is needed, trigger a manual restart through the wrapper script. If the update can wait, let the next scheduled restart apply it through the wrapper script's SteamCMD update step.
  4. After the restart, verify the version number matches the notification.

This workflow gives the operator control over when updates are applied while ensuring that the server is never more than one restart cycle behind the latest version.

The sequence diagram above shows the two possible workflows after receiving an update notification. The operator decides whether to restart immediately or wait for the next scheduled restart. Both paths end with the server running the new version.

Diagnostic table ​

SymptomMost likely causeResolution
Discord channel shows older version number than the RSS feedThe Discord webhook and RSS feed publish at slightly different times; a few minutes of delay is normalWait 5-10 minutes and check Discord again; if the discrepancy persists, the notification may have been manually posted on one channel only
RSS feed does not load or returns an errorThe RSS feed endpoint is temporarily unavailableCheck the SDG website status; the feed is hosted on the Smartly Dressed Games infrastructure and may experience downtime
Server version does not match the latest notification after a restartThe wrapper script's SteamCMD step failed silentlyManually run steamcmd +login anonymous +app_update 1110390 +quit and verify the command completes without errors
No notification received for an update known to existThe operator is checking the wrong Discord channel or the RSS reader cache has not updatedVerify the channel name is #dedicated-server-updates; clear the RSS reader cache and force a refresh
Version number in the server console is blank or shows 0.0.0.0The server binary is corrupted or the version manifest is missingRe-run the SteamCMD update step with the -validate flag to verify file integrity
Discord channel is empty or deletedThe operator joined the wrong Discord server or the channel was restructuredConfirm the official Unturned Discord server invite link is correct and that the channel still exists under the current channel layout

Frequently asked questions ​

How do I know if the Discord notification channel has been moved or renamed? ​

The SDG team typically announces channel structure changes in the #announcements channel of the official Discord server. If the #dedicated-server-updates channel disappears from the channel list, check the #announcements channel for a message about the change. If no announcement exists, the channel may have been temporarily removed during server maintenance and will reappear after the maintenance is complete.

Can I run the dedicated server on the same machine I use for general computing while relying on update notifications? ​

Yes, but the notification system is independent of the server machine. The Discord and RSS channels are consumed by the operator on any device with internet access, not by the server machine itself. An operator who runs a server on a dedicated machine in a data center can check update notifications from a personal laptop or phone without needing to access the server machine.

What is the most reliable way to detect that an update was published without relying on Discord or RSS? ​

The most reliable method is to use the SteamCMD command +app_info 1 1110390 to query the latest available build ID for the Unturned Dedicated Server App ID 1110390. This command returns the current build ID from the Steam backend directly. A script can run this command at a scheduled interval, compare the returned build ID against the server's current running build ID, and alert the operator if they differ. This method is more reliable than Discord or RSS because it queries the authoritative source (Steam) directly.

Can I set up an email alert for server updates? ​

Yes. Several free services provide RSS-to-email bridging, including Blogtrottr, Feedrabbit, and IFTTT. Configure the bridge with the RSS feed URL and the operator's email address. New feed entries are forwarded to the email address as they are published. The 57 Studios™ recommendation is to use a dedicated email filter rule that automatically tags or moves these messages to a designated folder so they are not lost among other email.

How do I differentiate between a dedicated server update and a game client update in the RSS feed? ​

The RSS feed is specifically for the dedicated server tool (App ID 1110390). It does not include game client updates that do not affect the dedicated server. If an update changes only the game client without changing the dedicated server binary, the RSS feed does not get a new entry. The Discord #dedicated-server-updates channel follows the same rule -- only dedicated-server-affecting updates trigger a notification.

What is the difference between the #dedicated-server-updates channel and the #announcements channel in the Unturned Discord server? ​

The #announcements channel in the official Unturned™ Discord server covers all SDG announcements, including game updates, blog posts, community events, and general news. The #dedicated-server-updates channel is specifically for dedicated server publishing events and contains only the version number and build ID for each update, without any commentary or unrelated announcements. Server operators who want minimal noise should monitor only the dedicated-server-updates channel.

Can I receive Discord notifications for the dedicated-server-updates channel without joining the Unturned server? ​

No. The Discord channel is only accessible to members of the official Unturned Discord server. You must join the server to access the channel. There is no public webhook endpoint that broadcasts the notifications independently.

How frequently is the RSS feed updated? ​

The RSS feed is updated every time the SDG team publishes an update to the Unturned™ dedicated server. There is no fixed schedule -- updates are published as needed for bug fixes, content additions, and hotfixes. The feed may be updated multiple times in a day during active development periods or remain unchanged for weeks during stable periods.

Can the RSS feed be consumed by a Discord bot or a custom monitoring tool? ​

Yes. The RSS feed is standard XML and can be consumed by any tool that supports HTTP fetching and XML parsing. A custom monitoring script can poll the feed at a configurable interval (the recommended interval is every 30 minutes to 1 hour), parse the latest entry, compare the build ID against the server's current build ID, and trigger an alert or a restart if a newer build is available.

Does the Discord channel include release notes for each update? ​

No. The Discord channel posts only the version number and build ID in a structured message format. Release notes are published separately on the Steam News Hub and are not included in the notification channel. Operators who want detailed change information should check the Steam News Hub after receiving a notification.

How long after the Discord notification should I wait before restarting the server? ​

There is no mandatory waiting period. The operator can restart the server immediately after receiving the notification, or wait for the next scheduled restart. The only risk of waiting is that a security-critical fix is not applied until the restart. For routine updates that do not patch security vulnerabilities, waiting for the next scheduled restart is safe.

Can I configure the server to automatically restart when a new version is published through the RSS feed? ​

The server does not natively poll the RSS feed. To implement automatic restart-on-update, the operator would need a custom script that polls the RSS feed, compares the build ID against the current server build ID, and triggers a restart if a newer build exists. This is an advanced configuration that requires scripting knowledge and is not needed for most servers because the regular scheduled restart through the wrapper script ensures the server is never more than 24 hours behind the latest version.

Can I receive update notifications by email or SMS? ​

Not directly through the SDG notification system. To receive email or SMS notifications, the operator would need to set up a third-party service that monitors the RSS feed and sends email or SMS alerts on new entries. Several free and commercial services provide RSS-to-email bridging.

How do I verify that the RSS feed URL has not changed? ​

The RSS feed URL is documented in the official SDG documentation and on the Smartly Dressed Games website. If the URL changes, the SDG team will announce the change through the Discord server and the Steam News Hub. The 57 Studios™ recommendation is to periodically verify that the URL is still correct by visiting it in a browser -- a 404 error indicates a changed URL.

What does a Steam build ID of 0 mean? ​

A Steam build ID of 0 in the server console output indicates that the server binary was not published through the standard Steam pipeline or that the version manifest is missing. This can occur when running a debug build, a custom compile of the server code, or a corrupted installation. The official server binary from SteamCMD always has a positive build ID.

Why would I need the build ID when the version number already tells me if an update is available? ​

The build ID is the more granular identifier. A dedicated-server-only hotfix may change the build ID without changing the version number. In such cases, the version number remains the same, and only the build ID indicates that a new binary is available. Operators who want to be certain that their server is running the exact latest binary should compare the build ID, not just the version number.

Worked example: configuring update notifications for a production server fleet ​

This worked example walks through the complete notification setup for an operator who runs three Unturned™ dedicated servers: one US East, one US West, and one Europe West. The operator wants to receive notifications about all server software updates and apply them uniformly across the fleet.

Step 1: join the Discord server and locate the notification channel ​

The operator joins the official Unturned™ Discord server using the invite link from the Steam store page. After accepting the server rules and completing the onboarding flow, the operator navigates to the channel list and locates the #dedicated-server-updates channel under the Server Updates category. The operator right-clicks the channel, selects "Mute Channel" to prevent notification sounds, but keeps "Channel notifications" set to "All" so that new messages appear in the unread list.

Step 2: configure the RSS feed in a monitoring tool ​

The operator maintains a monitoring dashboard using a self-hosted tool that supports RSS ingestion. The operator adds the feed URL https://smartlydressedgames.com/rss/unturned-steam-dedicated-server-updates.xml to the dashboard's RSS widget and configures it to poll every 30 minutes. The widget is configured to display the most recent entry's title and publication date in a prominent position on the dashboard.

Step 3: create a notification relay bot for the server community ​

The operator has a community Discord server for their game servers with approximately 200 members. The operator creates a private channel named #server-updates and configures a webhook that relays messages from the official #dedicated-server-updates channel. This relay ensures that community members can see update notifications without joining the official Unturned™ Discord server. The operator adds a note at the top of the channel explaining that the messages are relayed from the official SDG channel and that community members should check the Steam News Hub for detailed release notes.

Step 4: verify the server versions before the first notification ​

The operator SSHes into each of the three server machines and checks the startup logs for the version number and build ID:

US East: Version 3.25.9.1 (Build ID: 14327650)
US West: Version 3.25.9.1 (Build ID: 14327650)
Europe:  Version 3.25.9.1 (Build ID: 14327650)

All three servers are on the same version. The operator records this baseline in the server operations log.

Step 5: receive and process the first notification ​

A week later, the operator sees a new message in the Discord notification channel:

Unturned Dedicated Server 3.25.9.2
Build ID: 14327654

The operator checks the Steam News Hub for the release notes, confirms that the update includes a fix for a recently reported connectivity issue, and decides to apply the update immediately rather than waiting for the next scheduled restart.

Step 6: restart the servers and verify the version ​

The operator triggers a manual restart of each server through their respective wrapper scripts, staggering the restarts by 10 minutes to avoid all three servers being down simultaneously. After each server comes back online, the operator checks the startup log:

US East: Version 3.25.9.2 (Build ID: 14327654) - CONFIRMED
US West: Version 3.25.9.2 (Build ID: 14327654) - CONFIRMED
Europe:  Version 3.25.9.2 (Build ID: 14327654) - CONFIRMED

All three servers are now on the latest version. The operator updates the operations log with the version change and the restart times.

Step 7: ongoing maintenance ​

The operator's ongoing routine for update notifications consists of checking the Discord channel daily during the morning operational review, verifying each server's version weekly against the latest RSS feed entry, and maintaining the relay bot's webhook configuration when the official Discord server structure changes.

The worked example above shows the complete notification setup for a small server fleet. The total ongoing time commitment is approximately 5 minutes per day for checking notifications and 15 minutes per update cycle for applying updates across the fleet.

Best practices ​

  • Subscribe to both the Discord channel and the RSS feed for redundancy. The Discord channel provides real-time push notifications; the RSS feed provides a machine-readable source for automated monitoring.
  • Check the server's current version and build ID at startup and compare them against the latest notification at least weekly. A server that falls more than one minor version behind may miss compatibility changes.
  • Include the server's current build ID in the server operations log so that the operator can verify the version at a glance.
  • When a notification includes a security fix (noted in the Steam News Hub release notes), restart the server immediately rather than waiting for the next scheduled restart.
  • Configure an automated feed checker if running multiple servers. A single script that polls the RSS feed and compares the build ID against each server's current version saves the operator from checking each server individually.
  • Do not rely solely on the server's update-monitoring system (Enable_Update_Shutdown) to indicate when the server software has changed. The update-monitor checks Workshop content, not server software version.
  • Document the Discord server invite link and the RSS feed URL in the server's operational documentation so that any operator covering the server can access the notification channels.

Common mistakes in notification configuration ​

The following mistakes recur frequently among server operators who set up update notifications. Each entry describes the mistake, why it happens, and how to correct it.

Mistake: relying on the Discord mobile app notification for the dedicated-server-updates channel without checking the channel directly. Discord mobile notifications can be delayed or suppressed by the phone's battery optimization settings. A server operator who relies on the push notification may not see it for hours or may miss it entirely if the phone's notification history is cleared. The correction is to check the channel directly at least once per day in addition to relying on push notifications.

Mistake: subscribing to the RSS feed but never checking it. An RSS feed that is added to a reader that the operator rarely opens provides no practical benefit. The correction is to either set up an RSS-to-email bridge that forwards new entries to an email address the operator checks regularly, or to configure a monitoring dashboard that displays the feed entry in a visible location.

Mistake: assuming that receiving a Discord notification guarantees the server will update automatically. The Discord notification is informational only. It does not trigger any automatic action on the server. The operator must manually trigger or schedule the restart. The correction is to clearly separate the notification step from the update step in the operator's workflow documentation.

Mistake: checking the wrong Discord channel. The official Unturned Discord server has multiple channels with similar names. The #announcements channel posts general news including game updates, but it also posts community event announcements, blog updates, and other content that is not relevant to server operators. The dedicated-server-updates channel is the correct source for pure update notifications. The correction is to verify the channel name matches #dedicated-server-updates before relying on its messages.

Mistake: not verifying the server's build ID after a restart. A SteamCMD update step that fails silently leaves the server on the old version. The server starts normally, players connect, and the operator assumes the update was applied. The correction is to verify the version number and build ID in the startup log after every restart that was intended to apply a server software update.

Advanced considerations ​

Monitoring multiple servers from a single notification subscription ​

An operator who runs multiple Unturned™ dedicated server instances on different machines or in different data centers needs to track the version of each server independently. A single Discord or RSS subscription covers the global update status but does not tell the operator which servers have been restarted and which have not.

The recommended approach for multi-server operators is to combine the RSS feed with a script that polls each server's console output for the current build ID, compares it against the latest build ID from the RSS feed, and produces a report of which servers are up to date and which need a restart. This script can run as a cron job or scheduled task and send a summary to the operator on a daily basis.

Verifying Workshop content updates separately ​

The update notification system covers the server software version. Workshop content updates are tracked separately through the server's own update-monitoring system (the Enable_Update_Shutdown feature). An operator who needs to know about both server software updates and Workshop content updates should configure both systems: the notification channel for server software updates and the auto-restart system for Workshop content updates.

Notification integration with Discord bots ​

Operators who run their own Discord bot for server status can configure the bot to relay messages from the #dedicated-server-updates channel to a private channel in their own Discord server. This is useful for operators who want to keep their server community informed about updates without requiring community members to join the official Unturned™ Discord server. The relay bot must have access to the official server and the permission to read the notification channel.

Appendix A: Update notification channels quick reference ​

ChannelURLAccessFormatRecommended for
Discord#dedicated-server-updates in official DiscordRequires Discord account and server membershipChat message with embedded fieldsReal-time notifications, mobile alerts
RSShttps://smartlydressedgames.com/rss/unturned-steam-dedicated-server-updates.xmlPublic, no authentication requiredXML (RSS 2.0)Automated monitoring, script integration

Appendix B: Version and build ID fields in notification messages ​

FieldExampleSourcePurpose
Game version3.25.9.2SDG publishing pipelineHuman-readable version identifier for the update
Steam build ID14327654Steam publishing systemMachine-readable numeric identifier for the exact binary and asset set

Appendix C: Diagnostic commands for verifying server version ​

Command or locationWhat it showsWhen to use
Server startup console outputVersion: 3.25.9.2 (Build ID: 14327654)Immediately after server start
Discord #dedicated-server-updatesLatest published version and build IDWhen a new update notification is expected
RSS feed XMLPublished version and build ID with timestampWhen polling for automation
SteamCMD +app_info 1 1110390Latest available build ID on SteamWhen verifying SteamCMD will download the expected version

Appendix D: Update notification historical data point comparison ​

The following table shows a representative sample of update notification data points to illustrate the relationship between version numbers, build IDs, and update timing. These values are examples only and will differ for actual updates.

DateVersionBuild IDUpdate typeNotification channels
2026-07-203.25.9.114327650Bug fix patchDiscord + RSS
2026-07-253.25.9.214327654Hotfix for connectivity issueDiscord + RSS
2026-07-283.25.9.314327658Security fixDiscord + RSS
2026-08-053.25.10.014327700Content updateDiscord + RSS
2026-08-063.25.10.114327703Hotfix for content updateDiscord + RSS

The pattern shows that major content updates increment the MINOR version component, while bug fixes and hotfixes increment the PATCH and BUILD components. Build IDs always increase monotonically regardless of which version component changes.

Appendix E: External references ​

Document history ​

VersionDateAuthorNotes
1.02026-07-2657 StudiosInitial publication. Complete reference for Unturned dedicated server update notification channels including Discord and RSS, version number and build ID interpretation, notification workflow integration, and diagnostic guidance.

Notification channel selection decision flow ​

The following decision flowchart helps server operators choose the right notification channel or combination of channels for their operational setup.

The decision flow above covers the three common notification setups: Discord-only for operators who use Discord daily, RSS-only for operators who prefer feed-based monitoring, and dual-channel for operators who want both real-time push notifications and machine-readable automation.

Authoring checklist ​

  • [ ] Server operator has joined the official Unturned Discord server and can access the #dedicated-server-updates channel
  • [ ] RSS feed URL is bookmarked or configured in the operator's RSS reader or monitoring script
  • [ ] Server's current version and build ID are recorded for baseline comparison
  • [ ] Notification workflow is documented: operator knows where to check for updates and how to trigger a restart
  • [ ] Multi-server monitoring strategy is defined if applicable
  • [ ] Discord notification relay is configured if the operator wants to share update notifications with their community
  • [ ] RSS feed polling script is implemented if automated monitoring is desired

Cross-references ​

57 Studios logo with slogan

Beginner-friendly guides for Unturned modding, tools, publishing, server operations, and troubleshooting.

Learn

Getting StartedSteam SetupInstalling Unturned

Explore

ItemsSelf-HostingTroubleshootingHome

Built for Unturned creators, server staff, and 57 Studios™ contributors.

Copyright © 57 Studios™. All rights reserved. 57 Studios™, its branding, guides, and associated original content are protected by applicable copyright and trademark law.