Tags
Creators
Details
1.5.0-beta
Compatibility
Changes
Changelog: 21.01.2025 [Beta 1.5.0]
Important Notes
⚠️ Note: This version introduces significant changes that may not be compatible with previous versions unless
config.ymlis updated. If something doesn't work as it should report the error on discord
⚠️ Warning: Before proceeding with this update:
- Backup the
BackpackPlusfolder to avoid losing custom configurations or data.- If you are using a MySQL database, ensure it is backed up to prevent any potential data loss.
Key Changes
-
Configuration Overhaul:
- Major updates to
config.yml. Refer to the updated documentation for details on the required changes. - Added new configuration options to enhance flexibility and control.
- Major updates to
-
Database Enhancements:
- Optimized database queries for better performance.
- Introduced support for additional database configurations.
- Improved compatibility with MySQL and SQLite.
-
Added:
- Message displayed if a backpack fails to load from the database (or does not exist).
- Saving of backpacks in inventory after player's death:
- To enable, set
keep-backpacks-after-deathtotrue - You can also configure permissions for this feature. The default is:
backpackplus.keep.backpacks
- To enable, set
- Per-backpack material customization.
- Cache system for improved performance.
- Ability to set the backpack type to "filtered," allowing only specified items to be stored.
- Command to change basic backpack settings:
/backpackplus settings <tier> - Sounds when moving items in a backpack.
- To enable, set
play-song-when-item-moved-in-backpacktotrue
- To enable, set
- Additional MySQL database options related to HikariCP settings.
- Ability to set backpack descriptions in the configuration.
- Option to disable displaying the contents of backpacks.
Upgrade Steps
- Backup the necessary files and database as described above.
- Replace the existing plugin files with the new version.
- Update
config.ymlaccording to the latest format (refer to the provided config template). - Restart the server and verify that everything is functioning correctly.
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:lDAFcnRN:MJgzkAVO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lDAFcnRN:MJgzkAVO"
}

