RandomDay-Guard

Project status — RandomDay testing concluded

The RandomDay test operation is complete, and the public test server will close soon.

During this operation, RandomDay and RandomDayGuard ran together through repeated profile rotations, normal and interrupted server restarts, recovery and rollback checks, extended-mod integration, server-evidence collection, and operator-report review.

This gave us the knowledge we set out to gain: how rotating sandbox profiles behave throughout real dedicated-server lifecycles; how RandomDay interacts with supported extended mods; and how far RandomDayGuard can turn the evidence written by the server into useful, cautious monitoring without presenting gaps or guesses as facts.

Test-server stack used

• []RandomDay private development build v0. 41. 76[/]

  []RandomDayGuard private development build v0. 46. 130[/]

  []Chaotic Spawn Engine / DynamicSpawns 0. 8. 5 Hotfix 1[/]

  []Lethal Lasers 1. 0 UE4SS[/]

  []ANTE Up 0. 26[/]

  []RandomDay Encounter Director — a RandomDay-owned DynamicSpawns extension, not a separately distributed mod[/]

  []UE4SS v3. 0. 1 Beta #0 (Git 01e0a584; Nexus package v3. 0. 1-940-g01e0a584)[/]

  []Abiotic Factor dedicated server 1. 4. 0. 27939[/]

  The currently published packages remain RandomDay v0. 3. 16-alpha and RandomDayGuard v0. 4. 12-alpha.

  Development of both projects is now paused. The existing releases and documentation will remain available, and we may return when we once again feel the pull to continue the work.

  This stack documents what was used during the operation; it is not a minimum-version requirement or a guarantee of compatibility with later game, loader, or mod versions. The final formally recorded cycle used Abiotic Factor 1. 4. 0. 27939.

  ---

  RandomDayGuard

  Readable server, daily, player, case, and Guard-health reports for Abiotic Factor dedicated servers

  Alpha release v0. 4. 12-alpha

  RandomDayGuard turns the records already produced by a dedicated server into focused reports that show what happened, what information was available, and what needs attention.

  Each report has one job. Server health does not repeat player history, the daily review is not sent every few minutes, and quiet player or case routes do not create filler messages.

  What you get

  • []Server status - current availability, restart recovery, downtime, backup continuity, scheduler state, and Guard monitoring health.[/]

    []Daily rollup - one complete review of the calendar day across quiet periods and restarts.[/]

    []Player activity - one named account's supported session and recent-history facts, only when player activity exists.[/]

    []Case review - confirmed observations, relevant history, unknowns, and a recommended review step for a named case.[/]

    []Critical Guard - a failure in Guard itself, its reporting impact, and its recovery.[/]

    What the reports look like

    These examples were produced from the sample data included with the release; the names and account numbers are invented. A real report uses the values collected from that server and says when a fact was unavailable. Server Status: Online After Restart

    Current state: Online Available since: 14:07 Restart completed: 14:06 Downtime: 3 minutes, 12 seconds Restart reason: Scheduled game update Monitoring: Active. Last successful check: 14:09 Historical scan: 312 of 355 files reviewed Backups: Last verified 13:00; next expected 15:00; failures today 0 Action: None. The server recovered normally.

    Daily Review: 19 July 2026

    Server availability: Online for 23 hours, 47 minutes; offline for 13 minutes. Restarts: 2 total - 1 scheduled and 1 unexpected. Backups: 23 successful; 1 missing or failed; latest successful backup 23:00. Player activity: 3 unique players; 7 sessions - 6 completed normally and 1 interrupted. Case activity: 1 new, 2 updated, 1 needing attention, 0 critical. Evidence coverage: 6 of 7 expected source groups were available; the 04:00 backup log was unavailable.