RandomDay-Mod

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.

  ---

  RandomDay

  A complete Abiotic Factor ruleset prepared for the next restart

  Alpha release v0. 3. 16-alpha

  RandomDay gives each server run a distinct sandbox profile without changing the rules under players who are already connected.

  The current session keeps the SandboxSettings.ini it loaded at startup. RandomDay validates and prepares a complete family/day profile for the next restart. When the server starts again, that prepared profile becomes active and RandomDay queues the following day.

  What you get

  • []17 playstyle families with 17 days each: 289 documented profile combinations.[/]

    []Separate active and prepared states, so you can see what is running now and what the next restart should load.[/]

    []Complete sandbox profiles rather than partial live edits.[/]

    []Backup, validation, readback, and recovery around the primary sandbox replacement.[/]

    []Compact notices for the current profile and the profile prepared next.[/]

    []Optional adapters for separately installed supported mods. RandomDay does not bundle their code.[/]

    []A manual singleplayer/LAN mode that stays inside the RandomDay folder until you choose a world and copy the generated file yourself.[/]

    Active and prepared are different

    Active profile means the complete sandbox rules loaded by the running session. Prepared profile means a complete profile that passed validation and was written for the next restart. A prepared profile is not active until a later startup reads its marker. On the first installation, one start prepares Day 1 and a later restart activates it. That two-start sequence is expected.

    How the rotation works

    • []Abiotic Factor starts with the sandbox file already on disk.[/]

      []UE4SS loads RandomDay.[/]

      []RandomDay reads the active marker and chooses the next family/day profile.[/]

      []It builds and validates the complete next sandbox file.[/]

      []The file is reported as prepared only after production readback succeeds.[/]

      []The following restart activates it and RandomDay prepares the next day.[/]

      The standard set includes Action, Survival, Stealth, H