Tags
Creators
Details
1.6.6
Compatibility
Changes
New Features
-
Auto-Sell & XP Claim on Spawner Break Added support for automatically selling items and claiming XP when a spawner is broken. Configuration loading has also been enhanced for better reliability and flexibility.
-
Version 26.x Support Updated compatibility to include the latest minecraft version, ensuring SmartSpawner works seamlessly on the most recent Minecraft releases.
Improvements
- Experience Fields Migrated to
longType All experience-related fields have been migrated frominttolong, significantly increasing capacity and precision for high-volume or long-running servers.
Bug Fixes
-
Fixed: Spawner Disappearing When Surrounded by Blocks Resolved a critical bug where a spawner would vanish if it was completely enclosed by blocks. The fix ensures a valid drop location is always located nearby, even in tight spaces.
-
Fixed: Money Stacking Up with GUI Open on Full Storage Resolved an issue where currency would continue accumulating even after the spawner storage was full, as long as the GUI remained open. Money will no longer stack up when storage capacity has been reached.
-
Fixed: Drop All Button Dropping Items in Inconsistent Directions The "Drop All" button in the Spawner GUI now drops items in a consistent, predictable direction instead of randomly scattering them.
-
Fixed: Placeholder Errors in Some Embeds Not Displaying Information Certain embed messages were failing to resolve placeholders correctly, resulting in missing or blank information. This has been corrected alongside the event logging improvements.
Removed
- RedProtect Integration Removed All RedProtect hooks and related references have been removed from the codebase. If you were relying on RedProtect integration, please consider an alternative region protection solution.
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:9tQwxSFr:3kSCj1nw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9tQwxSFr:3kSCj1nw"
}

