A WTFBUILDS project · In development

Minecraft Arcade Infrastructure, Reimagined.

A high-performance Minecraft Java Edition 1.8.9 arcade server engine, written in Rust. Purpose-built to power BedWars and competitive minigames with maximum efficiency and minimal hosting cost.

Runtime concept visualization

Tick

0

Tick rate

20.0

Entities

184

Stylized simulation of a 20 TPS game loop — design target, not a live benchmark. Public numbers ship with the benchmark suite.

Protocol 47Minecraft 1.8.9Rust nativeIsolated match runtime
BedWarsSkyWarsDuelsProtocol 4720 TPS targetRust nativeMulti-match runtimeLow-latency PvPZero JVMWTFBUILDS

01 // Why MELON

Engineered for the arcade workload.

Traditional server architectures carry unnecessary overhead when hosting large numbers of independent matches. MELON strips it away.

Performance

Efficient game simulation and packet processing on the hot path — every tick counts.

Resource Efficiency

Minimal CPU and memory overhead per player and per match, by design.

Massive Concurrency

Many isolated matches running in parallel — without interference between them.

Low Latency

Sub-tick responsiveness for movement, combat, and knockback where it matters most.

Scalability

Maximum concurrent players and matches per machine — grow without growing bills.

Built for Arcade

Purpose-built for the workloads of BedWars, SkyWars, Duels, and beyond.

02 // Game Modes

BedWars first. Arcade infrastructure next.

BedWars stresses every part of the engine, making it the perfect proving ground. SkyWars and Duels follow on the same shared foundation.

Primary target

BedWars

The most infrastructure-hungry mode in competitive Minecraft — and the first optimization target for the MELON runtime. Every system below is exercised at full intensity, all match long.

  • Constant block place & break churn
  • Projectile, fireball, and entity physics
  • Latency-critical PvP combat and knockback
  • Full arena resets between matches
Stylized BedWars arena artwork — red and blue teams bridging across floating islands

SkyWars

Planned

Loot-driven island combat on the shared MELON runtime.

Duels

Planned

1v1 and 2v2 arena combat with tournament-grade latency.

03 // The Difference

Traditional stacks vs. the MELON approach.

CapabilityTraditional Java stacksMELON
Design focusGeneral-purpose platform, decades of compatibility surface
Arcade-only engine with a narrow protocol target
RuntimeJVM instance per server
Native Rust runtime
Per-match footprintHeavy per-instance memory overhead
Minimal by design
Match isolationShared worlds or a process per map
Isolated matches in one runtime
Scaling modelAdd more machines
More matches per machine
BenchmarksRarely published
Public, reproducible harnesses

shipped directiondesign target — engine in active development

04 // System Design

One runtime. Every match.

A modular, multi-crate engine: packets flow through the protocol pipeline into a deterministic game loop that hosts isolated matches in parallel.

01

Minecraft 1.8.9 Clients

Java Edition

02

Network Layer

TCP transport

03

Protocol 47 Codec

Packet pipeline

04

Game Runtime

Deterministic tick loop

05

Match Manager

Allocation & lifecycle

shared foundation

World & Entities

Blocks, chunks, simulation

Combat Core

Hit detection & knockback

Resource Scheduler

Density per machine

Modular workspace

Each subsystem is a standalone crate — protocol, transport, simulation, and game logic stay decoupled and independently testable.

No unsafe defaultsAsync I/O coreTick schedulersCrate isolation
planned workspace
melon/
├── crates/
│   ├── protocol/      # Protocol 47 codec
│   ├── networking/    # TCP & packet pipeline
│   ├── runtime/       # Game loops & scheduling
│   ├── world/         # Blocks & chunk state
│   ├── entities/      # Player & entity sim
│   ├── combat/        # PvP & knockback
│   ├── matchmaking/   # Match lifecycle
│   └── game-modes/    # BedWars, SkyWars, Duels
├── benchmarks/        # Reproducible harnesses
├── docs/              # Design documents
└── tests/             # Protocol & integration

05 // Roadmap

From foundation to arcade network.

Four phases, each shipping something runnable. Follow progress directly in the repository.

01

Foundation

In designPhase 1
  • Project foundation & core architecture
  • Minecraft 1.8.9 protocol implementation
  • Client handshake and login
02

Engine Core

PlannedPhase 2
  • Player movement & synchronization
  • World and chunk management
  • Multi-match runtime
03

Game Layer

PlannedPhase 3
  • BedWars engine
  • Combat, inventory & item systems
  • Matchmaking and lobby flow
04

Scale & Launch

PlannedPhase 4
  • Performance benchmarking suite
  • Production deployment
  • SkyWars & Duels support
  • Arcade orchestration infrastructure

06 // Join the harvest

Witness the future of arcade infrastructure.

MELON is in active development. Star the repository, watch the roadmap land crate by crate, and help build the arcade era.