Tags
Creators
Details
1.41.2.2754
Compatibility
Changes
v1.41.2.2754 Mod Update & Tooltip Hotfix
Changed: HavenBagsPreview data is now being stored in PDC alongside NBT, in order to still support older versions.
Fixed: An issue where hot-swapping the result in the Upgrade GUI, would overwrite the existing item.
Fixed: An issue where bag's tooltip styles on versions >= 1.21.3 where being set to minecraft:null. Any bag updated with this will have it's style reset.
Commit: eeb20f59
Pull: https://github.com/Valorless/HavenBags/pull/32
v1.41.1.2738 Skin Hotfixes
Fixed: Skins broken by update 1.41.0 should now correctly work again.
Fixed: An issue where unopened bags couldn't be skinned.
Commit: 76e61f4
Pull: https://github.com/Valorless/HavenBags/pull/31
v1.41.0.2733 Performance Updates
Important: Changed native version to 1.21.11.
Important: Refactored how data is stored internally, increasing overall performance.
Added: Additional MySQL configs:
mysql:
...
connect_timeout: 30 # Seconds
socket_timeout: 60 # Seconds
max_chunk_size: 200
Added: MySQL no longer saves all bags at once, but instead in chunks of 200.
Changed: Upgraded PvPManager dependency from v3.17.8 to v4.0.4.
Changed: Updated the way bags are stored in the cache, optimizing performance overall.
Changed: Increased performance when updating the bag items.
Changed: ValorlessUtils.SFX to HavenBags.utils.SFX and HavenBags.datamodels.Sound, which should solve SFX issues on certain versions.
Fixed: Increased performance in Lang by not fetching offline players when null.
Fixed: An issue causing skin tokens to not correctly parse the %skin% placeholder.
Fixed: An issue where giving bags would still took 1-6 sizes instead of the new 9, 18, 27, 36 ,45 ,54. Changed TabCompletion to reflect this.
Commit: 6e37f81
Pull: https://github.com/Valorless/HavenBags/pull/26
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:k3mSTyhw:Kg0MiMJ1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k3mSTyhw:Kg0MiMJ1"
}

