iTX Technologies
GitHub (new tab)中

iTX TechnologiesMinecraft ecosystem

Synapse

A legacy project exploring proxying and load balancing for Minecraft Bedrock Edition.

Legacy project
Source code (opens in a new tab)Project documentation (opens in a new tab)
Concept illustration
Brand
iTX Technologies
Platforms / runtime
See project documentation
Technologies
  • PHP
  • Swoole

About the project

Synapse is a historical project exploring connection proxying and load balancing for Minecraft Bedrock Edition. It focuses on how player connections enter a server network and how the proxy and backend exchange information, with documentation, examples, and source available to explore this work.

Genisys hosts worlds and gameplay, while Synapse focuses on network access. Using both in one server environment requires checking their protocol versions and implementations; no directly compatible version combination is confirmed here.

  1. Proxy and load-balancing focus

    The project targets proxying and load balancing for Bedrock Edition servers.

  2. Protocol exploration

    The roadmap covers Bedrock RakNet and Synapse Proxy Protocol rev9.0.

Understand the protocol goals

The README roadmap leaves the Bedrock RakNet and Synapse Proxy Protocol rev9.0 implementation items unchecked. The revision 9 document contains only a title and a packet-section heading, so it cannot serve as a complete integration specification. Consult the source when studying communication behavior; a complete proxy workflow remains unconfirmed.

What the example demonstrates

The technology notes list PHP 7.2 and Swoole 4.2. The example configures two listening endpoints and periodically updates the advertised server information. Its online player count is randomly generated display data, not a count of actual connections or a performance measurement.

Follow the documentation into the source

Begin with the roadmap, then compare the example, launcher, and protocol-handling source to distinguish interfaces, existing logic, and unfinished work. Reproduction also requires matching the historical runtime, extensions, and client protocol. Old dependency versions are not a guarantee of compatibility today. This page provides documentation and source access, with no download entry.