#Experimental Async Packets

The experimental path is enabled with:

renderer:
  async-rendering:
    enabled: true
    target-fps: 30
    maximum-fps: 60
    adaptive-rate: true
    queue-warning-millis: 250

PacketEvents is embedded and relocated inside Blockcade. Do not install another copy just for this feature.

#What it does

Blockcade keeps a one-frame mailbox for every enhanced renderer. A newer component replaces an older queued component, preventing an ever-growing backlog. Serialization and packet delivery run on the renderer worker; Bukkit world and entity access stays on the server thread.

#What FPS means

The dispatcher checks for a new prepared frame at the configured rate. Game simulation still runs on Paper's maximum 20 TPS. Setting 60 can reduce delivery delay for a frame created after input, but it does not create 60 unique simulation states.

Values above 60 are rejected because the current text renderer has no extra frames to send and would only increase CPU and network overhead.

#When to enable it

Test with your exact Paper build, proxy and player count first. The option is experimental and disabled by default. If initialization is unavailable, Blockcade logs a warning and uses synchronous Bukkit rendering.

Changing this section requires a full restart.