How winds-studio/leaf works
Project Type and Purpose
• This is an open-source, performance-oriented fork of the Minecraft Paper server (“Leaf”), built on top of Gale and incorporating patches from multiple other forks.
• It consists of two main deliverables:
• leaf-api – a compile-only API module that exposes hooks, events, annotations, and configuration abstractions for plugin authors
• leaf-server – the actual patched server implementation (Paperclip JAR) that runs under the Bukkit/Spigot/Paper plugin loader
File Structure
• Top-level build: Gradle wrapper, build.gradle.kts, settings.gradle.kts, scripts for releasing and upstream commits, and a build-data directory for import/version tracking.
• leaf-api: patch files plus a Maven/Gradle-published API artifact.
• leaf-server: paper/gale/minecraft patches, src/main/java with subpackages:
• org.dreeam.leaf (bootstrapping, async subsystem, commands, config modules)
• gg.pufferfish (Sentry integration, utility executors)
• net.caffeinemc (Lithium mod integration)
• org.leavesmc.leaves (protocol handlers: custom payloads, Jade, Syncmatica, replay, bot)
• others for Purpur commands, Linear region format, Matter hashing
• Configuration and build scripts tie all of these together via Paperweight’s “applyAllPatches” and “createMojmapPaperclipJar” tasks.
README for Additional Insights
• Purpose: high-performance fork, async pathfinding/mob spawning/entity tracking, broad plugin compatibility, mod-protocol support (Jade, Syncmatica, AppleSkin, etc.), Sentry error reporting, bStats metrics.
• Build instructions and license details.
Detail Balance
• Every major package and subsystem without overcrowding: use nested containers or layering.
• Fork/patch workflow and the runtime interactions between platform, Leaf code, and external services.
• Keep the focus on how the project is structured for both build-time (patch application) and runtime (async, config, protocol).