Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 3 months ago
All versions
0.0.5
Alpha
0.0.5last year 117
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
0.0.5
- data-driven features refactor, items are now defined as itemStacks in the known format
- added an optional additional dimension for public locations
- added several new blocks
- Player Detector Block, triggers another block when a player enters an area
- Lootable Vault Block, a variant of the Vault Block that has integration for the 'Lootable' mod
- Triggering Trial Spawner, a variant of the Trial Spawner, that can trigger blocks when changing the Trial Spawner State
- Triggered Villager Spawner Block, a variant of the Triggered Spawner specifically for all entities that have VillagerData (has automatic support for mods that add villager professions or types)
- Triggered Entity Remover Block, discards all non-player entities in an area when triggered
- Triggered Dispenser Block, variant of the vanilla dispenser, but needs to be triggered, doesn't drop it's inventory and can't be interacted with in survival/adventure mode
- Aesthetic Nether Portal, looks and sounds like a nether portal block, but is just aesthetic
- Aesthetic Decorated Pot, looks like a decorated pot, but has no inventory and can't be smashed
- Triggered Redstone Block, emits a redstone signal when triggered, has several states (signal strength, toggle/pulse) that change on (shift) right-click
- added 'Fake Villager' entity type, looks and sounds like a villager, but has no AI and no default right-click interaction
Optional dependencies
Any compatible version
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:ubmgmYs9:3uxPuyLH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ubmgmYs9:3uxPuyLH"
}

