BlockcadeDocumentation ← Portfolio
Docs/Compatibility and performance

#Compatibility and Performance

#Supported platform

  • Paper 1.19.4 or newer
  • Display Entity support
  • Java compatible with the selected Paper release

The release JAR targets Java 17 bytecode and the Paper 1.19.4 API baseline. The project is also compiled against the current Paper 26.2 API during release checks.

Blockcade does not use direct NMS calls. Modern raw movement input is accessed through a version-safe compatibility layer and older supported builds fall back to Bukkit movement events.

#Tick rate and visual FPS

Paper game logic runs at up to 20 TPS. games.yml tick periods divide that rate. Client monitor FPS and packet dispatcher FPS do not raise simulation TPS.

#Session design

  • One shared Bukkit ticker services all sessions.
  • One TextDisplay belongs to each active session.
  • Unchanged frames are not resent.
  • Enhanced rows combine adjacent cells with the same color.
  • Async rendering keeps only the newest queued frame.
  • A failure in one game session is caught and closes only that session.

#Capacity

Use max-active-sessions as a safety limit. Actual capacity depends on server CPU, other plugins, game selection and render mode. Watch MSPT with Paper or spark and lower the limit if the arcade tick warning appears.