Why Alloy Exists
The Minecraft modding ecosystem is fractured, bogged down by technical debt, and governed by drama. The existing platforms started as passion projects that grew beyond their architecture. Rather than patch what's broken, we're building what should have existed all along.
Our Philosophy
Alloy is not a fork. It is not built on top of Forge, Fabric, Quilt, or anything else. Every component — the mod loader, the API, the mappings, the modpack format, the launcher — is original work, designed together as a cohesive system.
We believe the next generation of Minecraft modding should be built on modern tooling, automated pipelines, and clean architecture. Modders deserve an ecosystem that respects their time and doesn't fight them at every turn.
This isn't about being different for the sake of it. It's about doing things right — the way they should have been done from the start.
Core Pillars
The principles that guide every decision we make.
No Legacy Baggage
Every decision is made for the current and future state of Minecraft. We don't carry forward years of workarounds and compatibility hacks.
Developer Experience
If a modder has to fight the tools to get work done, the tools are wrong. Alloy is designed around the developer, not the other way around.
Automation First
Mappings updates, build pipelines, version support — everything that can be automated, is. Humans should write mods, not babysit infrastructure.
Community Governed
No single point of failure. No benevolent dictator. Alloy is built by the community, governed transparently, and open to contribution from day one.
Roadmap
Where we are and where we're headed.
- ◆Core mod loader implementation
- ◆Initial modding API design
- ◆Automated mappings pipeline
- ◆Project website and documentation
- ◆Public API release for mod developers
- ◆Gradle plugin and mod templates
- ◆Example mods and tutorials
- ◆Community feedback integration
- ◆Stable 1.0 release
- ◆Launcher with modpack support
- ◆Mod repository / distribution
- ◆Full documentation and guides