1.0.2
Compatibility
Changes
DGspawners 1.0.2
A bug-fix release targeting two issues reported by the community. Big thanks to ShiroX for the detailed reports and screenshots that made these easy to track down!
Fixes
- Fixed duplicate / leftover holograms. Hologram armor stands were being saved to disk with the chunk, so every server restart left invisible orphans behind. Mining a spawner then removed only the new hologram, leaving the old one floating forever. Holograms are now never written to the world save, and any orphans from previous versions are cleaned up automatically as chunks load. No manual cleanup needed, your world heals itself.
- Fixed spawner data occasionally reverting after a save. Async save tasks could finish out of order, letting an older snapshot overwrite a newer one on disk (most visible as "my spawners.yml reset"). Saves are now versioned so the newest data always wins.
New
settings.force-placementconfig option. By default DGspawners overrides placement restrictions so spawners can be placed anywhere. If you run a claims or protection plugin (GriefPrevention, Lands, WorldGuard, Towny...), set this tofalseso players can't place spawners inside other players' protected areas. Mob spawning on any surface keeps working either way.
Upgrade Notes
- Drop-in update. The new config option is added automatically with the default value, so existing setups behave exactly as before.
- Existing orphaned holograms in your world will disappear on their own as players load those chunks.
Found a bug? Report it on our Discord and you might get a shout-out too: https://discord.gg/H9uvbjphPK
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:8B8MwBcd:ci1AxAbB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8B8MwBcd:ci1AxAbB"
}

