Loading...
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.
People bring two different things, and they lead to two different routes: the source code of a mod or plugin, or only its compiled .jar.
Make a project of your own, then upload the jar in Project Settings → Build, under Custom Dependencies. Every build compiles against it, and the AI is given the classes inside it, so it uses their real names instead of guessing them.
That is the route for an add-on, or for a patch of your own that sits next to the original. The original still has to be installed as well: uploaded jars are compile-only and are never packed into your file.
Dropping a .jar into the file tree reads it as text and breaks it, even though it looks fine there. A jar belongs under Custom Dependencies instead.
Paste the full error from the server or game log into the project chat, including the last Caused by: line. With the source in your project, the AI can change the code that fails. With only somebody else's jar it cannot change that code, so the fix has to live in your own project or come from the jar's author.
Only upload jars you have the right to use, and never publish somebody else's work as your own. See Community & Publishing Rules.
Try it now: Describe your plugin and see the plan, free and with no account. Open the plugin generator
10 of 22 in Minecraft Studio · Last checked 15 September 2026 · Previous: Config Studio