All versions
1.0.1
Release
Mineable Trial Spawner & Vault 1.0.14 months ago 41
Compatibility
Minecraft: Java Edition
26.1–26.1.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
1.0.1
-
Multi-Version & Multi-Loader Support
- Supports 26.1.1 Fabric and NeoForge
- Supports 1.21.11 Fabric and NeoForge
-
Mining & Silk Touch
- Trial Spawners and Vaults are now mineable (Hardness: 2.5).
- Silk Touch support: Trial Spawners and Vaults drop themselves.
- Breaking a Trial Spawner now drops the contained Spawn Egg as a separate item.
- Cooldown Preservation: The remaining cooldown duration is now saved to the item NBT and restored upon placement, ensuring spawner cycles aren't skipped by breaking them.
- Entity Clearing: Breaking a configured Trial Spawner now resets the dropped block item's entity data (since the egg has already been dropped).
- Silk-touched blocks preserve their internal configuration (rewards, state, etc.).
-
Ominous Spawner & Vault Support
- Trial Spawners now correctly swap to Ominous reward tables when active.
- Vaults now require Ominous Trial Keys and dispense Ominous loot when in an Ominous state.
- Cooldowns are now preserved when forcing Ominous states or swapping entities via Spawn Eggs.
-
Interaction Improvements
- Added Spawn Egg safety: Prevents using the same egg type on an existing spawner.
- Spawn Egg Swapping: Using a different Spawn Egg now drops the previous one instead of consuming it.
-
Deactivation & Anti-Abuse
- Added Torch Deactivation: Placing 4 wall torches on horizontal sides disables the Trial Spawner.
- Added 10s Cooldown Force: Deactivated spawners are forced into a cooldown to prevent mid-fight abuse and pausing.
- Disabled particles and sounds for dormant/deactivated spawners on the client.
-
Technical Polish
- Fixed various NBT retrieval and protected access compilation issues.
- Fixed loot tables when breaking the spawner
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:PgHqGO4D:ZbHLHp3h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PgHqGO4D:ZbHLHp3h"
}

