Skip to main content
Yes, with limitations. Summer Engine includes multiplayer APIs and transports for games you run and deploy yourself. Hosted Summercraft multiplayer is a separate platform capability and is not production-live yet.

​
What Works Today

  • High-level multiplayer API: MultiplayerPeer, MultiplayerSpawner, and MultiplayerSynchronizer all work in Summer Engine. The AI can help you set them up through natural language.
  • ENet and WebSocket transports: Local LAN multiplayer and WebSocket-based online multiplayer are both supported out of the box.
  • RPC and state synchronization: Remote procedure calls (@rpc) and automatic property synchronization work as expected. Ask the AI to set up synchronized variables and it will generate the correct annotations.
  • Dedicated server exports: You can export headless server builds for Linux deployment.

​
What the AI Can Help With

The AI assistant can generate multiplayer boilerplate, set up lobby systems, configure spawners and synchronizers, and debug common networking issues like authority conflicts and desync problems. For example, you can say “make this character controller work in multiplayer” and the AI will add the necessary RPC calls and authority checks.

​
Current Limitations

  • No built-in matchmaking or relay servers: Summer does not yet provide production hosted multiplayer infrastructure. Bring your own server for a game you operate today.
  • Complex netcode patterns: Advanced techniques like client-side prediction, rollback, and lag compensation require manual implementation. The AI can assist but these are inherently complex.
  • Testing: Multiplayer testing requires running multiple instances manually.

​
Summer SDK platform contract

The Summer SDK documents the creator-facing contract for host-authoritative gameplay, synced state, persistence, economy, and submission. The submission and review APIs are live. Player-facing playback, hosted dedicated game servers, automatic matchmaking, and the production runtime sandbox are not live yet. Track the canonical platform capability status before making launch promises.