Engine Profiles & Modes

CVL CORE does not treat “Tiers” as arbitrary commercial paywalls. Instead, the engine operates on an Operational Profiles Architecture, where network serialization, simulation tick rates, wire stride formats, and buffer sizing adapt dynamically to the target simulation genre and entity density requirements.

By decoupling tick rates from network egress and selecting fixed-stride serialization layouts, the engine allows teams to balance millisecond precision against egress bandwidth and hardware concurrency.

🟢Master Operational Profiles Matrix

The planned operational profiles govern baseline server loop pacing and binary wire contracts:

🟢Current Focus

🟡Future Plan : Existing Framework Refactoring

Architectural Parameter	Profile 1: Standalone Shard / MMO Cell	Profile 2: Action Co-Op	Profile 3: Competitive Arena
Profile Key	🟢`PROFILE_MMO_HIGH_DENSITY`	🟡`PROFILE_ACTION_COOP`	🟡`PROFILE_COMPETITIVE_ARENA`
Target Workloads	Open-World Survival (Rust, LIF), Persistent Hubs, MMO Zone Nodes	ARPGs, Dungeon Crawlers, Hero Brawlers, Co-Op Sessions	Flight/Space Combat, Racing, Sports, Fast Projectiles
Server Simulation Loop	30Hz (33.3ms frame budget)	30Hz (33.3ms frame budget)	60Hz (16.6ms frame budget)
Broadcast Divider	`2` (Effective Broadcast: 15Hz / 66.6ms)	`1` (Effective Broadcast: 30Hz / 33.3ms)	`1` (Effective Broadcast: 60Hz / 16.6ms)
Kinematic Precision	7.81mm X/Y, 0.087° Yaw	7.81mm X/Y, 0.087° Yaw	0.976mm X/Y, 0.021° Yaw, Pitch & Roll
Single-Node Capacity	400 – 500 Simultaneous	200 – 250 Simultaneous	64 – 100 Simultaneous
Client Buffer Delay ($T_{\text{render}}$)	100ms – 150ms (~2.0 ticks)	66ms (~2.0 ticks)	33ms (~2.0 ticks)
Full Server Egress Bandwidth	~37.4 MB/s @ 500 EIDs (Full Broadcast)	~18.7 MB/s @ 250 EIDs	~10.7 MB/s @ 100 EIDs

Active Development Operational Profile

🟢Profile 1: Standalone Shard / MMO Cell (`PROFILE_MMO_HIGH_DENSITY`)

Dual-Role Architecture: Functions out of the box as a complete, single-server standalone world (ideal for persistent survival sandboxes like Rust, Life is Feudal, or DayZ) hosting 400–500 un-instanced actors on a single compute node. Crucially, it also acts as the validated atomic cell for future multi-stitched MMO clusters.
Asymmetric Egress Conflation: Evaluates physics and continuous collision sweeps at 30Hz while dispatching outbound movement updates at 15Hz via BROADCAST_DIVIDER = 2, cutting network bandwidth by half without sacrificing authoritative resolution.
Packed 64-Bit Bitmask: Compresses 3D translation and rotational yaw into a tightly packed 10-byte <HQ> binary stride (Opcode 0x01), delivering 7.81mm positional granularity.
Jitter Ring Buffer: Client proxies smooth discrete 15Hz updates through an 8-slot snapshot ring buffer ($T_{\text{render}} \approx 133\text{ms}$), eliminating micro-stutter and network packet bunching.

Planned Future Profiles

🟡Profile 2: Action Co-Op (`PROFILE_ACTION_COOP`)

Synchronous Broadcast Cadence: Physics and networking tick 1:1 at 30Hz, minimizing client interpolation delay for medium-scale co-op games that demand tight responsive reactions.
Low-Latency Render Floor: Halves the client interpolation delay down to 66ms, delivering snappier melee feedback, dodge windows, and combat reactivity.
Balanced Bandwidth Footprint: Maintains the compact 10-byte <HQ> wire stride while scaling smoothly across instances housing 200–250 active entities.

🟡Profile 3: Competitive Arena (`PROFILE_COMPETITIVE_ARENA`)

High-Frequency 60Hz Loop: Paces the authoritative simulation loop at a strict 16.6ms budget to handle rapid projectile ballistics, vehicle collisions, and twitch interactions.
18-Byte Extended Bitmask: Employs a dual 64-bit word format (128-bit bitmask) packing full 3-axis orientation (Yaw, Pitch, Roll) and sub-millimeter Cartesian coordinate resolution (0.976mm steps).
Minimal Client Buffering: Operates at a tight 33ms buffer delay (~2 ticks), providing near-instantaneous visual parity for competitive esports and vehicle simulations.

Scaling Trajectory: From Single-Shard to Stitched MMO

A common question is how PROFILE_MMO_HIGH_DENSITY relates to the 10k–50k distributed MMO roadmap. The diagram below illustrates the relationship between a standalone world and a distributed cluster:

[ Standalone Shard / Survival World ]
  └── Single Node (PROFILE_MMO_HIGH_DENSITY)
        └── 400 - 500 Entities @ 30Hz (Single VPS)
              │
              ▼ [Stitched Multi-Node Architecture]
┌────────────────────────────────────────────────────────┐
│ Node A (Zone 1)  ◄── Modulo-4 Hysteresis ──►  Node B (Zone 2) │
│ (400-500 EIDs)         Epoch Gating           (400-500 EIDs) │
│        ▲                                             ▲       │
│        │                                             │       │
│ Node C (Zone 3)  ◄── Seamless Entity Handoff ──►  Node D (Zone 4) │
│ (400-500 EIDs)                               (400-500 EIDs) │
└────────────────────────────────────────────────────────┘
  Total Single-Shard Seamless World: 10,000 – 50,000+ Concurrent Entities

1. The Building Block Principle

Rather than attempting to run 10,000+ players inside a single bloated monolithic thread—which causes catastrophic tick degradation—CVL CORE solves MMO concurrency through modular cellular partitioning.

Each individual server node runs an ultra-lean PROFILE_MMO_HIGH_DENSITY instance capped at 400–500 entities with a flatline 42 MB RAM ceiling.

2. Multi-Stitched Cluster Topology (Active R&D)

To scale into a full 10,000–50,000+ single-shard MMORPG:

Macro-Zone Transfers: Server nodes are stitched together along coordinate boundaries. Boundary hysteresis (e.g., 32m margins) and modulo-4 circular epoch gating transfer authority between physical server nodes without client disconnects or loading screens.
Proximity-Layer Cell Broadcasting: Clients only receive kinematic streams for entities within their local 9-cell spatial neighborhood.
Zero-Overhead Orchestration: Because each individual node operates with sub-4ms tick loops, the aggregate cluster scales linearly across Linux bare-metal instances.

3. High-Density Telemetry Switchboard (10,000 – 50,000 Entities on Single Node)

For non-game enterprise workloads (autonomous drone swarms, industrial digital twins, and logistics fleets), a single headless CVL CORE node can scale to 10k–50k active entities by disabling client broadcast loops and operating purely as a high-velocity spatial hashing switchboard.