Everything you need to build for Minecraft: Spigot/Paper plugins, Fabric/Forge mods, Skript scripts, datapacks and configs — generated from a description and compiled in the cloud.
22 guides in this section of the VyroAI wiki.
Overview — Minecraft Studio explained: server plugins and Fabric or Forge mods that Cloud Build compiles to a .jar, and how Skript, datapacks and configs differ.
The Generator Pages — The public pages search engines send people to — and where their big button really goes.
Plugin, Mod, Skript or Datapack? — Which of the four Minecraft things to build — and whether your players have to install anything.
Bedrock Players — Yes, on a Java server that lets Bedrock players in through Geyser. A native Bedrock add-on is not something VyroAI builds.
Plugin Generator — Describe a Minecraft plugin in plain English and get the Java: commands, listeners, GUIs, permissions and config files, started one of four ways.
Mod Generator — Generate a Fabric or Forge mod from a description: blocks, items, entities and more. How Quick Create picks Fabric or Forge, and why Quilt is greyed out.
Script Editor — Write Minecraft Skript without Java: where the Script Editor lives, how to start a .sk script, and when addons, server TPS or a real plugin matter.
Datapack Studio — Vanilla datapacks — recipes, loot, advancements and placeable builds, with no plugin on the server.
Config Studio — Generate or safely edit YAML, JSON and TOML files: paste a config, describe the change, and get the whole file back with every other key and comment kept.
An Existing Mod or Jar — Bring a mod or plugin you already have: import its source to change it, or build your own project against its jar. What works when you only have the .jar.
Which Servers It Runs On — Nine platforms you can tick, why ticking several is normal, and when you end up with two jars.
Folia Plugins on Paper — Usually yes: Paper has the same schedulers Folia plugins use. The other way round is the catch. How to make your own VyroAI plugin run on Paper and Folia.
Cloud Build — Compile your Minecraft plugins and mods to a .jar file without installing anything.
When the Build Connection Drops — Your browser stopped hearing back from the build server. The build almost certainly finished anyway — the .jar is waiting in Build History.
Installing It on a Server — What to do with the .jar after you download it: which folder, why a full restart, and how to tell it actually loaded.
Hosting a Minecraft Server — No. VyroAI builds plugins, mods, datapacks and scripts, and you run them on your own server or with a server host. It only sells hosting for Discord bots.
Moving to a New Version — Update a plugin or mod you already have for a newer Minecraft release: what to ask for, what the Build tab setting really does, and what happens to Java.
Server Console Errors — Your plugin built fine and broke on your own server. How to read the error, and what the four common ones mean.
Plugin Icons — Let the AI draw an icon for your plugin, bot or mod from Project Settings or straight from the chat, pick a background style, and download it as a PNG.
Available Dependencies — Libraries you can use in generated plugins — resolved automatically at build time.
The Dependency Catalog — A page that says which libraries your build can actually fetch today — and lets you report one that cannot.
Custom Dependencies — Use a paid or private plugin the build cannot fetch: add its Maven coordinate or upload the jar in Project Settings → Build, and the build uses it.