Skip to content

Building from source

The source code isn’t published: these steps are for the plugins’ maintainers. To run the plugins, use the ready-built files from the downloads page.

You need JDK 25 and Maven 3.9+ on your PATH. The Fabric companion builds with the Gradle wrapper in its folder, which downloads Gradle and Minecraft the first time.

  • Linux and macOS: ./build-all.sh
  • Windows: build-all.cmd

Both build every plugin and copy the jars into _builds/.

Plugin Command (in its folder) Jar
ShottyCore proxy plugin mvn -B package -pl velocity -am (in ShottyCore/) velocity/target/ShottyCore-Velocity.jar
ShottyCore Paper companion mvn -B package -pl paper -am (in ShottyCore/) paper/target/ShottyCore-Paper.jar
ShottyCore Fabric companion ./gradlew build (in ShottyCore/fabric/) build/libs/ShottyCore-Fabric.jar
ShottyEvents mvn -B package target/ShottyEvents-<version>.jar
ShottyGames mvn -B package target/ShottyGames-<version>.jar
ShottyDeathSwap mvn -B package target/ShottyDeathSwap-<version>.jar
ShottyMace mvn -B package target/ShottyMace-<version>.jar
ShottyBedwars mvn -B package target/ShottyBedwars-<version>.jar

The ShottyCore jars have no version in their file names, so a new build always replaces the old jar on a server.

ShottyBedwars compiles against ScreamingBedWars, which isn’t on a Maven repository: put the ScreamingBedWars 0.2.44 jar at ShottyBedwars/lib/sbw.jar first.

mvn -B test runs a project’s unit tests. ShottyCore’s cover the database migrations, punishment and duration parsing, the chat filter and watched-word matching, the application form rules, store steps and Stripe, parties, nicknames, the anticheat kick rules and more; ShottyDeathSwap’s cover the swap ring, the swap timing and the weighted picks.

The Pelican panel plugins have plain PHP checks: php tests/SupportTest.php (Minecraft Sources) and php tests/UserLogParserTest.php (Zomboid Players).

They aren’t built. Copy the plugin’s folder (minecraft-sources/ or zomboid-players/) into the panel’s plugins/ folder and run php artisan p:plugin:install <id>. See each plugin’s README for its settings.

The documentation website is generated from these Markdown files: the READMEs and the guides in docs/. Change them here, then refresh the site from them.