Skip to content

Networking

CAT uses server authority for Assembly structure and separates structural synchronization from projected physics synchronization.

Authority model

  • The server initializes and changes assemblies.
  • Clients submit commands and control input through player-owned Interactor Components.
  • The Assembly Component replicates authoritative structural snapshots.
  • Physics synchronization follows the active or passive sync policy.

Structural state

The Assembly Component is the network owner of Assembly State. Clients install replicated snapshots and rebuild their local runtime representation after the required Part Model assets are available.

Physics state

Active controlled objects and passive objects can use different synchronization strategies. Passive snapshot playback supports smoothing and tier-based policies.

For project-wide remote physics and snapshot policy options, see Network Settings.

  1. Standalone initialization.
  2. Listen server with one client.
  3. Client-issued grab and command submission.
  4. Repeated attach and detach operations.
  5. Join in progress after an assembly already exists.
  6. Control Session start, prediction, and stop.

Do not initialize from a client

Blueprint Authority Only functions must execute on the server. Use the Assembly Interactor Component for client requests.