• Overview
• Systems
• Development
• Discord

• Main site

the end of the world

Chernarus kept decaying after civilisation fell. Buildings rot, roads disappear beneath wrecks and overgrowth, and the places people once depended on hold the remains of failed escapes. FINALDAYZ builds survival around what was left behind.

| the world responds

Weather, sound and environmental effects respond to your surroundings. Rain drums on nearby wrecks, wind reaches through broken windows, and fog changes how far you can see. Moving from open ground into a ruined building changes what you hear and experience.

| a shared state

Connected systems draw on common information about weather, location and conditions. The server controls gameplay, loot and physical hazards, while each client streams visual detail and effects within its performance budget. Together, they give Chernarus a consistent sense of place.

systems index

• WEATHER
• BUILDINGS
• LOOT & SCENES
• ROADS & WRECKS
• SOUNDSCAPE

• INVENTORY
• INFECTED
• UNDERGROUND
• FRAMEWORK
• PLAYER ARRIVAL

system detail

The Environmental State Director owns the server’s weather. Each state defines targets for cloud, rain, fog, wind and storms, along with transition timings and atmosphere settings. Weighted choices introduce variation within an authored progression, while persistence carries the current state across restarts.The World Director coordinates lighting and colour, feeding the daytime and night-time observer so other systems can respond to the conditions. Together, these layers help weather, visibility, lighting and ambient wildlife feel connected. A change in the world can influence several effects through shared information.

system detail

Building templates describe objects relative to a known structure. The runtime transforms those local positions into placements at matching buildings across Chernarus. This allows carefully authored interiors to be reused while maintaining consistent alignment with floors, openings and furniture.When a client activates a procedural building, it sends a READY message containing the building class and catalogue index. The server validates that reference and activates the relevant scene managers. UNLOAD releases temporary scene ownership, while consumed-slot records prevent taken items from immediately returning.

system detail

FINALDAYZ uses authored scenes to give supplies a setting and a history. Panic Sites build hospital and store environments, while the Loot Director places survivor-death scenes using the Building Catalogue. Other systems create breakdowns, selected convoy scenes and a restart-selected aircraft crash site.Gameplay items remain under server authority. Decorative objects can be handled locally where appropriate, allowing greater visual density around the real supplies. The audit’s Loot Director configuration used an inspection setting with unusually dense placement, so those recorded quantities do not define the intended release balance.

system detail

The wreck registry combines authored additions, existing map wrecks and records contributed by other scene systems. Physical wrecks remain authoritative, while their surrounding visual dressing is streamed by each client. Position and template data are delivered in paced batches.Road Detritus uses player location, road-surface checks, movement and deterministic cells to select nearby detail. Looking ahead along travel helps prepare the road in front of the player. The audited physical road-stone companion is dormant, so the active Road Detritus system is described here as visual surface detail.

system detail

The World Soundscape Map divides Chernarus into 150-metre cells with cached environmental classifications. The server combines the player’s current profile with weather information and sends that context to the client. Audio systems can then make consistent decisions without repeatedly scanning the whole surrounding world.Nearby wreck anchors support rain-on-metal loops, while building and exposure information guide indoor rain and wind layers. Nature sounds respond to location, rain, wind and time. Lightning is paired with thunder delayed by distance, and Apocalypse Radio uses a server epoch to coordinate playback across clients.

system detail

Player Monitor spreads its work across small updates, refreshing different information at different rates. It supplies common movement, vehicle and inventory snapshots to its consumers. This keeps checks inexpensive and helps inventory systems agree on the player’s current state.Container Leaks applies staged quantity loss and dampens affected cargo or its container. Ruined Clothing Drops begins with client detection, then asks the server to validate the condition before selecting and ejecting cargo. Movement, swimming and vehicle state influence the drop chance, giving damaged storage practical consequences.

system detail

Urban Undead uses authored urban sites and generated underground encounter records. Proximity activates a site budget, allowing encounters to respond to player presence. Once cleared, a site enters a twenty-minute cooldown before its budget can return through the rearming process.The encounter also communicates with client performance systems. A warning RPC temporarily holds back optional streaming activation before infected spawn in batches. This coordinates gameplay and visual workloads, reducing the chance that several demanding systems activate together.

system detail

The underground complexes occupy an elevated spatial layer, with airlocks moving players between the surface and the appropriate network. Pre-boot tooling prepares the persistent layout and trigger data. The server then loads the geometry, access points, loot scenes and associated registries.Clients receive compact maps for dressing and audio, allowing local detail to follow the generated sections. Fog, flickering lights, surface overlays and props build atmosphere around server-owned geometry. The same network data also supplies encounter positions, keeping gameplay and presentation tied to one layout.

system detail

Startup is staged across call queues, with shared catalogues and caches prepared before their consumers. Building systems reuse canonical positions, while wreck-producing scenes contribute their anchors before snapshots are delivered. Large data sets are sent through paced clear-and-batch messages.Client streaming uses spatial cells, distance, facing, size tiers and hysteresis to manage activation and removal. The performance manager supplies multipliers for detail and work budgets, and receives active-object costs from major visual systems. This allows local presentation to scale while gameplay objects remain under server authority.

system detail

Fresh character creation follows a controlled server sequence. The character is marked as a new arrival, prepared at a holding position, given the selected loadout and moved into the authored wake-up location or boat sequence. Matching client messages provide the visual and audio presentation.Returning-player wake-up uses a separate path and skips characters still within the fresh-spawn window. It presents a brief transition without relocating the survivor or forcing real unconsciousness. A creation throttle also delays heavier post-login work, helping distribute the load around arrival.

development roadmap

from test shard to final release

The goal is a coherant, immersive, and detailed world with controlled performance and reliable gameplay.

discord

be a part of what comes next

Join the FINALDAYZ community to follow development, share your experiences and help shape the world through feedback. Pull up a seat. There’s more to come.

• discord

dev updates / community discussions / player feedback