Tags
Creators
Details
Licensed ARR
Published 8 months ago
Updated 6 months ago
All versions
V1.1
Release
VirtualSpawnerPro V1.18 months ago 110
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
๐ Changelog - v1.0.0-STABLE
โ Added
- OP/Admin Bypass: Added a check for the
vspawner.adminpermission, ensuring OPs and Admins can always upgrade regardless of level-specific permission settings. - Granular Permission Support: Fully implemented
vspawner.speed.<level>andvspawner.storage.<level>checks for non-admin players. - Centralized Reload System: The
/vsp reloadcommand now simultaneously refreshesconfig.yml,drops.yml, andprices.yml.
๐ง Fixed
- CRITICAL: Config Path Mismatch: Fixed an issue where the plugin was looking for upgrade settings under
spawner-settingsinstead of the correcteconomy-settingspath defined in the config. - CRITICAL: Upgrade Logic Lock: Fixed a bug that prevented all players (including OPs) from upgrading because of incorrect permission evaluation.
- Economy Calculation: Fixed the cost calculation logic in the GUI to correctly multiply the base cost by the current level and stack amount.
- Economy Manager Deposit: Fixed a compilation error in
EconomyManager.javawhere thedepositmethod was not correctly utilizing the amount parameter. - Drop Reloading: Fixed an issue where
drops.ymlwould not refresh properly without a full server restart.
โ๏ธ Optimization
- Hologram Syncing: Improved the timing of Text Display updates after selling items to ensure the "Storage" count updates instantly.
- GUI Performance: Cleaned up the
MenuManagerclick listener to reduce overhead when interacting with spawner menus.
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:cr5GwuSS:5a8QJ9jj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cr5GwuSS:5a8QJ9jj"
}

