How shanwer/geyser works
Main Components
a. Core Components:
• Protocol Translation Layer
• Session Management
• Entity Management
• Inventory System
• World/Chunk Management
• Authentication System
b. Platform-specific Components:
• Standalone Bootstrap
• Platform-specific Implementations (Spigot, BungeeCord, Velocity, etc.)
• Extension System
┌─────────────────────────────────────────────┐
• Bedrock Client │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Network Layer │
• (Protocol Handlers, Compression, Packets) │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Translation Layer │
• ┬─────────────┬────────────┤
• Entity │ Inventory │ Block │
• Translation │ Translation │ Translation │
• ┴─────────────┴────────────┘
• ↕
┌─────────────────────────────────────────────┐
• Session Layer │
• (GeyserSession, Cache, State Management) │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Platform Layer │
• (Standalone, Spigot, Bungee, etc.) │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Java Server │
• ┘
Key Components Detail
a. Translation Layer:
• Packet translators for both directions (Bedrock → Java and Java → Bedrock)
• Registry systems for blocks, items, and entities
• Connection handling components
b. Session Management:
• Cache management
• Authentication flow
• Player data handling
c. Platform Integration:
• How different platforms connect
• Extension system
• Configuration management
Additional Elements
Include:
• Extension system integration points
• Resource pack management
• Authentication flows
• Cache management systems
• Event handling system
Notes
Annotations for:
• Version compatibility information
• Key configuration points
• Important limitations
• Extension points