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.

When you need this

Cloud Build resolves most libraries on its own — see Available Dependencies. But a paid plugin, a private one, or something a customer handed you as a file publishes no public jar, so there is nothing for the build to fetch. That is what custom dependencies are for.

Uploaded jars are compile-only

Every build of the project reads the jars you uploaded and compiles against them, but never packs them into your finished jar. The Build tab says so under the upload button: Uploaded JARs are compile-only: the server or plugin must supply them at runtime. So the plugin a jar came from still has to be installed on the server, next to yours.

Where it lives

Open your project in the Code Studio and go to Project Settings → Build (the gear icon). The Custom dependencies block near the bottom holds both ways of adding one, and everything you add there is sent to the AI and to the build server.

Two ways to add one

Add the coordinate — if the library lives in any public repository, add its Maven coordinate (group, artifact, version, scope) and the build resolves it like the rest.
Upload the jar — for anything with no public home, press Upload JAR / ZIP and the build compiles against the file itself. A .zip is unpacked for you, so a bundle of several jars can go up in one go.

Uploading a jar


Accepted	`.jar`, or a `.zip` containing one or more jars
Maximum size	25 MB per jar — larger ones are refused with a message, and inside a zip they are skipped
Stored with	The project, so it travels with it and every later build sees it

Not the same as the upload on the Publish tab

Project Settings → Publish has a different jar upload (100 MB, security-scanned, and recorded as not verified — though no screen shows a visitor that mark). That one only supplies the download on a published project when you have no successful compile — it is never compiled against. If you want the build to use a library, it has to go in the Build tab.

Only upload jars you have the right to use. A paid plugin you bought is yours to build against; one you found elsewhere is not, and re-publishing it breaks the Community & Publishing Rules.

Check Available Dependencies first. Several plugins that feel private — MythicMobs, PlotSquared, MMOItems, Geyser — are already wired up and need no upload at all.

Also in Minecraft Studio

Next in Discord Bots: Overview
Start here: 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.
Start here: The Generator Pages — The public pages search engines send people to — and where their big button really goes.
What you can build: Plugin, Mod, Skript or Datapack? — Which of the four Minecraft things to build — and whether your players have to install anything.
What you can build: Bedrock Players — Yes, on a Java server that lets Bedrock players in through Geyser. A native Bedrock add-on is not something VyroAI builds.

22 of 22 in Minecraft Studio · Last checked 12 September 2026 · Previous: The Dependency Catalog