1.0.1
Compatibility
Changes
DGspawners 1.0.1
Full text customization plus a round of stability and performance fixes. No config changes needed, just drop in the new jar (two new files generate automatically).
New: Customizable Messages & GUIs
Every piece of text the plugin shows is now editable. Two new files generate on startup:
messages.yml- all chat messages, with color codes and placeholders. Change wording, translate to your language, tweak the prefix, whatever you like.gui.yml- every GUI title, button name, and lore line. Fully rearrange or reword your menus.
Missing a line? No problem. The plugin falls back to sensible defaults, so a partial file never breaks anything. Reload live with /sadmin reload.
Fixes
- Fixed item loss when withdrawing from virtual storage with a full or nearly full inventory. Items that don't fit now stay safely in storage instead of vanishing.
- Fixed money loss on empty spawner conversion. If the spawner was broken while the convert menu was open, you're no longer charged for nothing.
- Fixed inflated kill stats. Kill counts no longer increase when mobs fail to spawn (no free space or un-spawnable type).
- Fixed console spam from spawners with mob types that can't be world-spawned. These now log once instead of every cycle.
- Fixed a lingering state entry when a player quit mid-way through adding a trusted player.
Performance
- Cached Vault economy lookups instead of resolving them on every transaction (noticeably lighter when opening the shop).
- Cached hot-path spawn settings so they aren't re-read from config on every spawner tick.
- Save operations are now guarded against overlapping writes for safer data storage on busy servers.
Other
- Added
softdepend: [Vault]so the plugin always loads after your economy plugin.
Thanks for using DGspawners! Report bugs or suggest features on our Discord: https://discord.gg/ZZhVKUtSNS
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:NkIv9jez"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8B8MwBcd:NkIv9jez"
}

