1.3.1
Compatibility
Changes
v1.3.1
This pull request simplifies the repository by removing outdated workflows, updating version properties, and cleaning up dependency files. The most important changes include the deletion of the beta branch workflow, renaming the main branch workflow, updating the paperVersion property, and removing unused library definitions.
Workflow changes:
- Deleted the workflow for publishing packages on the beta branch, including all steps related to GitHub Packages, Hangar, and Modrinth uploads.
- Renamed the workflow from "Beta Branch" to "Main Branch" and updated the trigger branch from
betatomain.
Version updates:
- Updated
paperVersionfrom1.21.4to1.21.8, reflecting the latest platform version.
Dependency cleanup:
- Removed unused dependency definitions for VaultAPI and Paper API, cleaning up the file.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:oRpYCka8:T3DC6iHw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oRpYCka8:T3DC6iHw"
}

