Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last month
All versions
0.3.0+mc26.1.2
Release
MultiGolem 0.3.0 for Minecraft 26.1.25 months ago 95
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
- Disabled golem healing no longer plays the normal heal feedback when players use matching materials on damaged golems.
- Villages can now naturally spawn MultiGolem variants as defenders.
- Added server config for village spawn weights. Iron, Copper, Gold, and Emerald are common by default, Diamond is rare, and Netherite has a default weight of
0so villages do not naturally spawn fire-starting Netherite defenders unless a server owner opts in. - Server owners can now control who may create or heal each MultiGolem tier using Fabric Permissions API-compatible permission providers.
- Permissions are permissive by default, so existing servers keep their current creation and healing behavior unless a permissions plugin denies a node.
- Permission checks apply to player-built MultiGolem creation, ingot-based healing, marked spawn egg use, and marked spawn egg spawner configuration.
- Added Copper, Gold, Emerald, Diamond, and Netherite Golem Spawn Egg variants as marked vanilla iron golem spawn eggs.
- The MultiGolem Copper Golem Spawn Egg uses a different icon from the vanilla Copper Golem Spawn Egg, but both spawn eggs have the same name.
- Marked MultiGolem spawn eggs can configure monster spawners to spawn the matching MultiGolem variant.
- Added a MultiGolem icon and project links for ModMenu and mod list screens.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| multigolem-0.3.0+mc26.1.2-sources.jar | Unknown | 133.22 KiB |
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:KTpFotEw:R9bMIQwt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KTpFotEw:R9bMIQwt"
}

