Tags
Creators
Details
Licensed ARR
Published 8 months ago
Updated 6 months ago
All versions
1.0.0
Release
VirtualSpawnerPro Release8 months ago 32
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
๐ Changelog - v1.0.0-STABLE
โ Added
- Granular Permission Support: Implemented strict permission checks for Speed and Storage upgrades.
- Use
vspawner.speed.<level>to restrict speed upgrades. - Use
vspawner.storage.<pages>to restrict storage expansion.
- Use
- Centralized Reload System: Added
plugin.reloadPlugin()to ensureconfig.yml,drops.yml, andprices.ymlall refresh simultaneously with one command. - Smart Config Mapping: Updated the menu logic to correctly read from the
spawner-settingsandeconomy-settingsblocks in the config.
๐ง Fixed
- CRITICAL: Drops Not Reloading: Fixed an issue where
loadDrops()was using cached data. It now forces a fresh read from the disk usingYamlConfiguration.loadConfiguration. - CRITICAL: Compilation Error: Fixed a variable scope error in
EconomyManager.javawhere thedepositmethod was incorrectly referencingtotalValueinstead of the passedamount. - RELOAD Command: Fixed the
/vsp reloadcommand inCommandManager.javawhich was previously skipping theTickEnginereload logic. - Economy Bypass: Fixed a bug where de-opped players could bypass level restrictions if they had enough money; permission nodes are now checked before any transaction occurs.
โ๏ธ Optimization
- Hologram Syncing: Improved the timing of hologram updates after storage sells to prevent "ghost" data displays.
- Thread Safety: Optimized the
synchronizedblocks inTickEnginefor better performance during high-volume loot generation.
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:A5dQpVfK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cr5GwuSS:A5dQpVfK"
}

