Q/GUI
QuantumGUI
A fast, cross-version inventory interface framework.
- Immutable menu templates
- Incremental rendering
- Pagination and safe click handling
Modern Minecraft development libraries
Build better.
Build Quantum.
Create fast, maintainable Minecraft plugins using clean APIs for interfaces, commands, configuration, and scheduling.
Published by Crown · MIT License · v0.1.0-alpha
Composable by design quantum.java
Menu shop = QuantumGUI.menu() .key("credits-shop") .title("<gradient:#8B5CF6:#22D3EE>Credits Shop</gradient>") .rows(6) .policy(MenuPolicy.locked()) .item(22, GuiItem.builder() .material(MaterialKey.of("EMERALD")) .name("<green>Your Credits") .onClick(context -> context.open("credit-packages")) .build()) .build();shop.open(player);Platform-aware architecture
Adapters for the server ecosystems developers already use.
Spigot
Paper
Purpur
Folia
Compatibility matrix status: Coming Soon
The ecosystem
Four focused libraries. One way of building.
Use each product independently, or compose them into a consistent foundation for production plugins.
Q/CMD
QuantumCommandAPI
A strongly typed command framework with arguments, suggestions, permissions, and clean command trees.
- Typed arguments
- Native suggestions
- Permissions and structured errors
Q/CFG
QuantumConfig
A type-safe configuration framework with validation, migrations, comments, and safe reloads.
- Typed models
- Validation and migrations
- Atomic snapshots and safe reloads
Q/SCH
QuantumScheduler
A unified scheduler API for Spigot, Paper, Purpur, and Folia.
- Global and async tasks
- Entity and region tasks
- Ownership, groups, and cancellation
Developer experience
Less framework ceremony. More useful intent.
Quantum keeps performance and safety inside the architecture so everyday plugin code stays readable.
Focused APIs
Small, composable surfaces keep common work obvious and advanced paths available.
Discoverable types
Typed builders, contexts, and results make the next valid operation clear in the IDE.
Safe lifecycle
Ownership and cleanup rules are part of the framework instead of plugin-specific afterthoughts.
Platform boundaries
Keep business logic separate from version checks and platform registration details.
Fast feedback
Testkits, diagnostics, and stable contracts reduce the distance between an idea and a working plugin.
Measured architecture
Incremental work, immutable snapshots, and direct lookups avoid unnecessary runtime churn.
Performance by construction
Do less work on the hot path.
Quantum favors direct lookups, stable snapshots, incremental rendering, and explicit execution contexts. The result is infrastructure that stays quiet while your plugin does useful work.
Read the architecture guides Runtime lifecycledeterministic
- 01
Build immutable intent
- 02
Validate before publication
- 03
Apply only current revisions
- 04
Clean up on lifecycle events
Docs Getting Started
From dependency to first menu.
Use the BOM to align modules, install the platform adapter, and keep the manager for your plugin lifecycle.
repositories { mavenCentral() // Crown Maven repository: Coming Soon}dependencies { implementation(platform("dev.crown.quantum:quantum-bom:0.1.0-alpha")) implementation("dev.crown.quantum:quantum-gui-core") implementation("dev.crown.quantum:quantum-gui-paper")}Examples
Patterns pulled from real plugin work.
Start from a focused example, then adapt it to your own domain and lifecycle.
QuantumGUI
Paginated shop
Inventory UI with dynamic balance rendering and safe click handling.
QuantumCommandAPI
Admin commands
Typed player and menu arguments with native suggestions.
QuantumConfig
Validated settings
Commented models, range validation, and stable reload snapshots.
QuantumScheduler
Profile loading
Async I/O returning safely to the entity scheduler.
Build your next plugin foundation
Build better. Build Quantum.
Start with one focused library, then compose the ecosystem as your plugin grows.