Tags
Creators
Details
1.6.7
Compatibility
Changes
New Features
New /ss set Command
Added a new admin command to quickly update SmartSpawner properties in-game.
Admins can now set:
- Stack size
- Spawn range
- Spawn delay
The command can be used on the spawner the player is looking at, or with exact world coordinates for console/admin use.
New Performance Settings
Added new performance options for loot generation. These settings help large stacked spawners run more smoothly by using a faster calculation method when extremely large amounts of loot are generated.
This is enabled by default and is recommended for most servers.
Improvements
Better Loot Generation Performance
Large spawner stacks now handle loot generation more efficiently, reducing heavy processing during big spawn cycles while keeping results realistic over time.
Improved Item Giving Behavior
The /ss give command now handles full inventories more reliably. If the player does not have enough space, extra items will be dropped safely at their location instead of being lost or handled incorrectly.
Clearer Configuration
The selling configuration has been renamed and reorganized to make it easier to understand.
The old custom_economy section has been replaced with sell_integration, which better describes what the feature is used for.
Compatibility Changes
ExcellentEconomy Support
SmartSpawner now supports ExcellentEconomy for storage selling.
CoinsEngine support has been replaced by ExcellentEconomy.
Shop Integration Updates
ExcellentShop integration has been removed.
Supported shop integrations now include:
- EconomyShopGUI
- EconomyShopGUI Premium
- ShopGUI+
- zShop
Important Notes
- SmartSpawner now requires Java 25 or newer.
- Existing sell-related configuration values are migrated where possible.
- A new permission has been added:
smartspawner.command.set.
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:xEXmONpF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9tQwxSFr:xEXmONpF"
}

