How mohanavel15/amethyst works
Project type and purpose
• Amethyst is a standalone Minecraft server implementation (targeting protocol version 1.8.x) written in Go.
• Its purpose is to accept Minecraft client connections, negotiate handshake/login, manage play-state sessions (chat, tab list, player position), and optionally handle status queries.
File structure
• Top-level:
• main.go: entrypoint
• go.mod, go.sum, LICENSE, README.md
• Packages:
• server/: core server components (connection management, context, encryption, authenticator, mux, player management)
• handlers/: per-state request handlers (echo/status, handshake, login, play)
• protocol/: packet definitions, state machine, serialization/deserialization, error types, “peeker” (frame reading)
• crypto/: CFB8 cipher, SHA1 for authentication
• zlib/: compression support
• Tests alongside most packages indicate unit-tested boundaries.
README
• Confirms it’s a fork of Plasma, implements Server Status, Join Game, Chat, Tab List, missing “spawn other players.”
Detail
• Every major package as a component
• State transitions (HANDSHAKING → LOGIN → PLAY)
• How Context/Player models are shared between handlers
• Call out external dependencies (e.g., Mojang Auth) even if not yet implemented
• Do not shy away from listing sub-packages (e.g., protocol/packets/status)