1.3.5
Compatibility
Changes
v1.3.4
This pull request introduces several improvements and refactors to the project, focusing on enhancing the release and publishing workflows, improving code organization, adding a new command for listing gravestones, and making logging more consistent. The changes also include some dependency and version updates.
CI/CD Workflow Improvements:
- Replaces the separate
main.yml,alpha.yml, andbeta.ymlworkflows with a unified.github/workflows/release-and-publish.ymlworkflow that handles building, tagging, and publishing releases for both themainandalphabranches, and adds publishing to GitHub Releases, Hangar, and Modrinth. [1] [2] [3] [4]
Features and Commands:
- Adds a new
ListGravestoneCommandthat allows players to list their gravestones, including inventory UI integration. - Updates command registration in
LyttleGravestone.javato prepare for the new list command, though it is currently commented out pending completion.
Database Enhancements:
- Adds new methods to
GravestoneDatabasefor retrieving all gravestones or gravestones belonging to a specific player, supporting the new list command functionality. [1] [2]
Code Organization and Logging:
- Refactors event listener classes by moving them from the
listenerspackage to a newhandlerspackage and updates related imports and registration comments for clarity. [1] [2] [3] - Replaces direct
System.out.printlnlogging withplugin.getLogger().severefor more consistent and appropriate error reporting throughout the codebase. [1] [2] [3] [4]
Dependency and Version Updates:
- Updates
pluginVersionto1.3.5andpaperVersionto1.21.8ingradle.properties. - Removes the unused
gradle/libs.versions.tomlfile.
These changes streamline the release process, improve maintainability, and add new features for users and administrators.
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:q790UNpr:ZjQlX2hw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q790UNpr:ZjQlX2hw"
}

