Tags
Creators
Details
1.4.0.0
Compatibility
Changes
v1.4.0.0 - Improved reliability and performance improvements
-
Implemented fixes for backpack system crashes, memory leaks, and permission issues:
- Attempted to resolve thread safety issues to prevent server freezing during heavy use.
- Workaround for possible memory leaks by ensuring backpacks properly clean up when players leave.
- Implemented fix for permission changes to handle item preservation and restoration correctly.
- Optimized file operations to make saving/loading more efficient.
- Enhanced overflow system to prevent item loss and duplication on permission changes.
-
Attempts to improve overall plugin functionality:
- Atomic saves to ensure data integrity even during server crashes.
- Admin tools refinement to allow viewing player backpacks without conflicts.
- Constants implementation for navigation arrows and slots to replace magic numbers.
- Loop protection to prevent items from getting stuck in endless loops.
-
Performance optimization attempts
- Reduced memory usage per player.
- Accelerated file operations for faster backpack interactions.
- Improved queue management to reduce "wait to open" occurrences.
Previous Version:
- v1.3.2.0:
- Fixed Messages not loading from file
- Made so if the player has items present in the overflow file, it will be visible from the /bpview command so an admin can take and recover items
- v1.3.1.0:
- Added fallback option to prevent losing items on permission shrinks
- Added lock mechanism to prevent two players accessing the same inventory at the same time (ex. /bp and /bpview), not ideal but safest approach to prevent item duping
- Rewrote Messages, Titles, and Item Names to read from configuration files for player customization
- Command /vsreload no longer needed to update inventory sizes - now done automatically
- Command /vsreload now reloads the text cache used for titles and messages
Full Changelog: https://github.com/852DuartePls/Spigot-VirtualStorages/compare/1.3.1.0...1.4.0.0
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:UsaVodBT:elFyQVpH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UsaVodBT:elFyQVpH"
}

