1.3.4-ALPHA.24
Compatibility
Changes
v1.3.4
This pull request introduces significant updates to the codebase, including the addition of new functionality, refactoring for better organization, and improvements to logging. Key changes include the addition of a new command for listing gravestones, refactoring listeners to handlers, and enhancing error logging throughout the project.
Functional Enhancements:
- Added
ListGravestoneCommand: Introduced a new command that allows players to list their gravestones. This includes fetching gravestones from the database and displaying them in a custom inventory. - Database Enhancements: Added methods in
GravestoneDatabaseto retrieve all gravestones and gravestones associated with a specific player.
Refactoring:
- Renamed Listeners to Handlers: Updated the package structure by renaming
listenerstohandlersfor better alignment with the code's purpose. This change affects files such asBreakBlock.java,Death.java, andGuiClose.java. - Reorganized Variable Declaration: Rearranged variable declarations in
LyttleGravestone.javato improve readability.
Logging Improvements:
- Enhanced Error Logging: Replaced
System.out.printlnstatements withLogger.severeorLogger.warningfor more consistent and professional error handling across the project. This change affects multiple files, includingRetrieveGraveStoneCommand.java,BreakBlock.java, andGuiClose.java.
Workflow Updates:
- Removed Beta Workflow: Deleted the
.github/workflows/beta.ymlfile, which previously handled releases for the beta branch. (.github/workflows/beta.yml, - Updated Main Workflow: Modified
.github/workflows/main.ymlto reflect publishing packages for the main branch instead of the beta branch. (.github/workflows/main.yml,
Dependency Cleanup:
- Removed
libs.versions.toml: Deleted thegradle/libs.versions.tomlfile, which contained dependency version mappings.
These changes collectively improve the functionality, organization, and maintainability of the codebase.
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:2mTOUpeA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q790UNpr:2mTOUpeA"
}

