TRANSPARENT VALIDATION
A generated file is not proof that a Minecraft mod works
Mine Mod AI uses deterministic builders and layered validation because valid JSON can still fail silently in Minecraft. Here is what the system checks, what CI proves, and what it does not claim.
Guard the request
Prompts become a clamped, whitelisted specification. Unsupported requests are refused honestly instead of being renamed and shipped as an unrelated pack.
Build from verified templates
Only validated identifiers, escaped names and bounded parameters enter the pack templates. The same request produces the same inspectable output.
Validate the generated pack
Before delivery, the load gate checks manifests, JSON, function references, script entry points, pack layout, item texture chains and other known load blockers.
Exercise real runtimes in CI
Representative generated packs are loaded by automated Java and Bedrock server checks. This catches runtime failures that file-shape validation alone cannot prove.
Public, inspectable proof
150
curated mod pages with real prompts, downloadable outputs and file-level details
Inspect the generated mods →89
verified maker workflows covering items, mobs, datapacks, add-ons and minigames
Browse the maker workflows →The honest boundary
CI loads representative generated packs; it does not boot a fresh Minecraft server for every visitor request. A pack may also conflict with third-party mods, server configuration or experimental settings outside Mine Mod AI's control. Back up important worlds and test new content before using it on a production server.
If the system cannot map a request to an engine that genuinely supports it, the correct result is guidance—not a junk pack carrying the requested name.