Continuous-Time State
The “4D” in Timeless 4D Engine means that time is part of the state model.
A multiplayer world does not only need to know what is true now. It often needs to know what was true when an action happened.
Continuous-time state gives Arcanex a way to reason about shared reality across space and time, especially when latency, validation, permissions, replay, and long-term world history matter.
Why Time Matters In Multiplayer
Online games do not operate in a perfect present moment.
Players see the world through clients that are always slightly behind the server. Messages can arrive at different times. Two players can act based on different views of the same world.
In a simple game, many of these problems can be handled with special-case networking code.
In a persistent world, time becomes a foundation problem.
The engine needs to know not only what is true, but when it was true.
A player may take an action based on what their client saw a fraction of a second earlier.
The server may need to validate that action against the state that existed at that moment, not only against the newest state.
That matters for interaction, permissions, ownership, visibility, combat, trading, building, moderation, replay, and world history.
State At A Point In Time
Traditional systems often focus on current state: what exists now, where it is, who owns it, and what values it currently has.
That is useful, but it is not enough for a large multiplayer world.
Arcanex needs to reason about state across time.
A persistent world needs a timeline, not only a current view.
Continuous-time state means that systems can ask what was true at a specific point in time.
This does not mean every rendered frame is stored.
It means the engine can use time-aware state and authoritative history to reason about the world at relevant moments.
That makes latency handling, validation, replay, debugging, and auditability part of the engine model instead of separate systems bolted on later.
Latency And Ordering
Networks do not give multiplayer worlds a perfect shared present.
Clients and services can temporarily disagree about what happened first or what state was visible when a player acted.
A traditional state-centric system often needs special-case logic around those cases.
Arcanex treats timing differences as part of normal multiplayer reality.
Continuous-time state gives the engine a principled way to reason about actions against the relevant moment.
This is especially important in worlds where actions have durable consequences.
A temporary mismatch in a short match can disappear when the match ends. A persistent world has to preserve a coherent history.
Prediction, Reconciliation, And Validation
Client responsiveness is important.
Players need the world to feel immediate, even when the server remains authoritative.
But responsiveness has to coexist with an authoritative world model.
The client can feel immediate. The engine must preserve the shared reality.
Continuous-time state gives the engine a better foundation for validation and reconciliation.
The engine can evaluate actions against the relevant moment in time. Systems can reason about what was allowed, who had permission, and what state was visible when the action happened.
This is useful for latency handling, cheat prevention, permission checks, replay, and debugging.
Why This Matters For Persistent Worlds
Persistent worlds magnify every state problem.
The world continues after the session ends. Player actions can affect ownership, economy, construction, travel, access, reputation, social structure, and history.
Those systems need time-aware validation.
In a persistent world, history is product infrastructure.
A persistent world cannot treat history as a disposable log.
It needs to know what happened, when it happened, and how those events changed the world.
Continuous-time state is one of the foundations that allows the Timeless 4D Engine to support replayable history, durable ownership, permissioned interactions, and long-term world state.
contime
One public technical primitive behind this thinking is contime, an open-source Rust crate developed by Arcanex’s founder.
contime demonstrates a small public piece of time-aware state thinking. It is public, minimal, and work in progress. It is not the full Timeless 4D Engine.
The full engine includes additional private systems around shared state, simulation, generation, permission, perception, replay, and world operation.
The public crate shows the concept. The engine is the larger system around it.
Where To Go Next
Continuous-time state is one part of the engine foundation.
It connects directly to event-first architecture, replayable history, permission and perception, and Rust systems infrastructure.