Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 3 weeks ago
All versions
1.6.9
Release
SmartSpawner 1.6.95 months ago 3,396
Compatibility
Minecraft: Java Edition
26.1.x
1.21.5–1.21.11
Platforms
Folia
Paper
Purpur
Changes
This release expands GUI customization and improves the reliability of spawner management across different server environments.
What's New
- Added support for
custom player-head textureson buttons in the main and storage GUIs. - Custom textures can be applied to navigation, storage, experience, sorting, selling, and other configurable GUI buttons.
- Added a dedicated GUI layout guide with examples for configuring custom textures and conditional button styles.
Improvements
- Improved spawner removal from management menus, including spawners located in unloaded chunks.
- Related menus now close automatically when a spawner is removed, preventing players from interacting with outdated inventories.
- Improved the reliability of stacking and admin management actions while a spawner is being modified or removed.
- Improved nearby-spawner highlight cleanup and session handling.
- Refreshed the documentation website with clearer navigation, updated branding, and improved readability.
Compatibility
- Updated compatibility with newer SimpleClaimSystem releases.
- Updated compatibility with plugins using the latest NightCore release.
Developer API
- Added
removeSpawner(String spawnerId)to remove a SmartSpawner by its unique ID. - Added
removeSpawner(Location location)to remove a SmartSpawner at a specific location. - Both methods return a
CompletableFuture<Boolean>and complete after the spawner block and stored data have been removed, including when its chunk must be loaded first.
Fixes
- Fixed the
en_US_DonutSMP_v2language pack not being included under the expected resource path, which caused missing-resource warnings and prevented its language files from loading. - Prevented overlapping spawner actions from causing inconsistent spawner data.
- Prevented explosions and manual breaking from interfering with spawners already being removed.
- Improved menu behavior when a managed spawner is no longer available.
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:a7VtEgFt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9tQwxSFr:a7VtEgFt"
}

