Share Your Mod With Your Players

A server-side plugin never leaves your server. A Both mod has to get onto every player's computer, and "I'll DM everyone a JAR" stops working at about five players. Three ways to hand it out, from simplest to most polished.

#Send the file

Download the JAR from the project and send it. Works for a friends' server. Include three things with it, every time:

• The platform (Fabric, NeoForge, Forge)
• The exact Minecraft version
• Whether they also need Fabric API or a base mod like Cobblemon

Point them at Install a mod on your computer so you're not answering "where's the mods folder" six times.

#Publish a community page

Every project can be published to the Player Games community library. That gives your mod a public page with a description, screenshots, the platform and version, and a download button. You send a link instead of a file, and when you push a new build the link stays the same.

From the project, open the publish controls, give the listing a name and summary, and publish. You can set it to:

• Visible: listed in the library, searchable, anyone can find it
• Unlisted: only people with the link can see it
• Hidden: taken down, the link stops working

Publishing to the community library needs a previous credit purchase on your account. That keeps the library from filling up with untested first attempts.

#Publish to Modrinth

If your players use a Modrinth-aware launcher, or you want the mod to be found by people who've never heard of your server, publish it to Modrinth from Creator Hub.

1. Get a personal access token from your Modrinth account.
2. In your Player Games profile settings, open the Modrinth tab and paste the token. It's encrypted before it's stored.
3. On the project, click Publish to Modrinth. Creator Hub creates the Modrinth project with the loader, game version, and license set.
4. After each new build, click Sync new version and the new JAR goes up as a new version.

Modrinth has its own rules about what can be listed. A mod that only works with your server's other plugins is better as an unlisted community page.

#Keep versions straight

Every time you change the mod, players on the old build will have a different mod than players on the new one. On a Both mod that means they can't join.

• Tell players the version number and the date when you update.
• Sync the new version to Modrinth or push the new build to the community page before you update the server.
• Keep the previous JAR so you can roll the server back if the new build has a problem.

#Who owns it

The mod is yours. Download the source any time. If you distribute it, Minecraft's EULA and the loader's rules still apply, same as any other mod.