Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 3 weeks ago
All versions
1.8.3
Release
SmartSpawner 1.8.33 weeks ago 12.9K
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.6–1.21.11
Platforms
Folia
Paper
Purpur
Changes
Fixed
- Opening a spawner's storage while another player was using it could leave the menu stuck open with its ghost items takeable. In creative mode those items were kept. The player now stays on the spawner menu with a "storage in use" message.
Added
- Custom spawners: any number of extra spawners for the same mob or item, each with its own loot, set up under
custom_spawners. They stack only with each other and are given by their own name. display_namegives a spawner its own name on the item, in menus and on the hologram, so players can tell custom spawners apart.- Each spawner can have its own menu head and drop chance. A custom spawner takes anything it leaves out, except loot, from the normal spawner of its mob or item.
- A custom spawner can be renamed without losing the ones already placed by listing the old name under
aliases. - The console warns about spawner names that clash, and about placed spawners whose spawner was removed from the settings files.
Changed
/ss giveis shorter:/ss give <player> <spawner> [amount], for example/ss give Steve zombie 5. Vanilla spawners use/ss give <player> vanilla <mob> [amount].spawner_mobs.ymlandspawner_items.ymluse a simpler layout. Each mob or item is listed under its own name, and custom spawners have their own section. See the details below.
Notes
- Both settings files are converted on the first start, and the old files are kept with a
.1.8-backupending. Placed spawners and spawner items keep working and stack with new ones. No action is required. - The old give form (
smart_spawner,item_spawner,vanilla_spawner) still works from the console and command blocks, so shop, crate and vote setups need no changes.
Configuration file details
- Entries are keyed by the mob or item itself:
zombie_spawner:withentity: ZOMBIEbecomeszombie:, anddiamond_spawner:withitem: DIAMONDbecomesdiamond:. - Entries that were not named after their mob or item move under
custom_spawners, keeping theirentityoritemline. - New optional keys on every entry:
display_nameandaliases. - Spawner names now match the entry keys, so
zombie_spawneriszombiein commands. The old names are still accepted.
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:47df3bzh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9tQwxSFr:47df3bzh"
}

