3.6 KiB
3.6 KiB
Networking Overview
Pumpkin is built with a high-performance, asynchronous networking stack capable of servicing both Minecraft: Java Edition and Minecraft: Bedrock Edition clients simultaneously.
All protocol definitions, serialization traits, and wire-level codecs are isolated in the pumpkin-protocol crate, while client connection management, session state machines, and gameplay packet dispatching are managed in pumpkin/src/net.
Supported Editions
Pumpkin separates network implementations by edition due to their fundamentally distinct transport layers, packet encodings, and state models:
| Feature | Minecraft: Java Edition | Minecraft: Bedrock Edition |
|---|---|---|
| Transport Layer | TCP socket streams | UDP via RakNet & NetherNet |
| Framing | VarInt length-prefixed frames | Batched packets encapsulated in 0xfe headers |
| Encryption | AES-128 / CFB8 stream cipher | Cryptographic session handshake |
| Compression | Per-packet ZLib (above configurable threshold) | Per-batch Deflate / ZLib compression |
| State Model | Explicit states: Handshake, Status, Login, Config, Play | Packet-driven state progression |
| Protocol Crate | pumpkin-protocol::java |
pumpkin-protocol::bedrock |
| Server Net Module | pumpkin::net::java |
pumpkin::net::bedrock |
Networking Architecture
The networking pipeline routes incoming connections through specialized transport and codec layers before delegating to the unified server game loop:
- Transport Listeners: Independent listeners bind to their respective ports—Tokio TCP for Java Edition (
:25565) and UDP/RakNet/NetherNet for Bedrock Edition (:19132). - Session Abstraction: Each accepted connection spawns an isolated session task (
JavaClientorBedrockClient) managing wire framing and encryption. - Codec Deserialization: Wire bytes are deserialized into typed packet structs via
pumpkin-protocol::java(ClientPacket/ServerPacket) andpumpkin-protocol::bedrock(PacketWrite/PacketRead). - Unified Gameplay Dispatch: Decoded packets are dispatched into the unified game loop, updating player entity states and streaming world chunks.
Navigating the Networking Docs
Explore the documentation for each edition:
- Entity Metadata & Synced Data: Synchronization of visual entity states (DataWatchers in Java, Actor Data in Bedrock).
- Java Edition:
- Architecture & Lifecycle: State machine,
JavaClientvs.Player, and multi-version negotiation. - How to Add a Packet: Guide to defining, serializing, and dispatching Java Edition packets.
- Authentication: Mojang Yggdrasil validation, GameProfiles, and proxy forwarding.
- Architecture & Lifecycle: State machine,
- Bedrock Edition:
- Architecture & Transports: RakNet and NetherNet integration, batching, and session handling.
- How to Add a Packet: Guide to defining and handling Bedrock Edition packets.
- Authentication & NetherNet: JWT certificate chain verification, WebRTC DataChannels, P-384 keys, and signaling.
- RCON: Implementation of Valve's Remote Console protocol for administrative management.