A template for building PaperMC/Spigot Minecraft server plugins!
- Draft release on version tag push
- Increment project version with a PR on version tag push
- Build artifacts on pull requests
- Build snapshots on pushes to main
- Weekly artifact builds to ensure your code is up-to-date
- Discord notifcations for main branch build results
- Probot: Stale
- Mark issues stale after 30 days
- Dependabot
- Update GitHub Actions workflows
- Update Gradle dependencies
- Bug report template
- Feature request template
- Shadowed PaperLib build
- Checkstyle Google standard style check
- SpotBugs code analysis
- JUnit testing
- Sample plugin.yml with auto-fill fields
- Simple Gradle build config
- Empty config.yml (just to make life *that* much easier)
- Simple .gitignore for common Gradle files
In order to use this template for yourself, there are a few things that you will need to change.
In order to use Discord notifications, you will need to create two GitHub secrets. DISCORD_WEBHOOK_ID
should be set to the id of your Discord webhook. DISCORD_WEBHOOK_TOKEN
will be the token for the webhook.
You can find these values by copying the Discord Webhook URL:
https://discord.com/api/webhooks/<DISCORD_WEBHOOK_ID>/<DISCORD_WEBHOOK_TOKEN>
For more information, see Discord Message Notify.
I've broken the rest of the changes up by their files to make things a bit easier to find.
Update the line below with the name of your plugin.
rootProject.name = 'ExamplePlugin'
Make sure to update the group
to your package's name in the following section.
group = "com.crimsonwarpedcraft.exampleplugin"
Add any required repositories for your dependencies in the following section.
repositories {
maven {
name 'papermc'
url 'https://papermc.io/repo/repository/maven-public/'
content {
includeModule("io.papermc.paper", "paper-api")
includeModule("io.papermc", "paperlib")
includeModule("net.md-5", "bungeecord-chat")
}
}
mavenCentral()
}
Also, update your dependencies as needed (of course).
dependencies {
compileOnly 'io.papermc.paper:paper-api:1.18.1-R0.1-SNAPSHOT'
compileOnly 'com.github.spotbugs:spotbugs-annotations:4.5.2'
implementation 'io.papermc:paperlib:1.0.7'
spotbugsPlugins 'com.h3xstream.findsecbugs:findsecbugs-plugin:1.11.0'
testCompileOnly 'com.github.spotbugs:spotbugs-annotations:4.5.2'
testImplementation 'io.papermc.paper:paper-api:1.18.1-R0.1-SNAPSHOT'
testImplementation 'org.junit.jupiter:junit-jupiter-api:5.8.2'
testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.8.2'
}
In the following section, you will need to replace "ExamplePlugin.jar" in asset_path
and asset_name
with the name of your plugin (see settings.gradle).
- name: Upload Release Asset
uses: actions/upload-release-asset@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
upload_url: ${{ steps.create_release.outputs.upload_url }}
asset_path: ${{ github.workspace }}/build/libs/ExamplePlugin.jar
asset_name: ExamplePlugin.jar
asset_content_type: application/java-archive
First, update the following with your information.
author: AUTHOR
description: DESCRIPTION
Next, the commands
and permissions
sections below should be updated as needed.
commands:
ex:
description: Base command for EXAMPLE
usage: "For a list of commands, type /ex help"
aliases: example
permissions:
example.test:
description: DESCRIPTION
default: true
example.*:
description: Grants all other permissions
default: false
children:
example.test: true
You will need to replace all instances of leviem1
, such as the one below, with your GitHub
username.
reviewers:
- "leviem1"
You will need to replace leviem1
, with your GitHub username.
* @leviem1
Update this file with whatever applies to you.
github: leviem1
Below are the steps you should follow to create a release.
- Create a tag on
main
using semantic versioning (e.g. v0.1.0) - Push the tag and get some coffee while the workflows run
- Add a description to the release draft once it's been automatically created and publish
- (External contributors only) Create a fork of the repository
- Pull any changes from
main
to make sure you're up-to-date - Create a branch from
main
- Give your branch a name that describes your change (e.g. add-scoreboard)
- Focus on one change per branch
- Keep your commits small (<300 LOC), and write descriptive commit messages
- When you're ready, create a pull request to
main
with a descriptive title, and listing any changes made in its description- Link any issues that your pull request is related to as well
Create scoreboard for total points
ADDED - Scoreboard displayed in-game at game end
CHANGED - Updated `StorageManager` class to persist scoreboard data
After the pull request has been reviewed, approved, and passes all automated checks, it will be merged into main.
Thanks to Gradle, building locally is easy no matter what platform you're on. Simply run the following command:
./gradlew build
This build step will also run all checks and tests, making sure your code is clean.
JARs can be found in build/libs/
.
I think that's all... phew!