
Modern Companions
Recruit 14 RPG-style human followers with unique AI, infinite leveling, custom weapons, and useful tools! Pack them into Soul Gems, then summon your fully geared squad in any dimension to guard, patrol, or follow as you carve a campaign across Minecraft!
Tags
Creators
Details
3.49
Compatibility
Changes
Modern Companions v3.49
Cross-Mod Food Support
- Companions can now automatically recognize compatible standard foods from other mods for healing, favorite foods, and taming requests.
- Vanilla foods remain available during recruitment.
- Foods with harmful, unsafe, or unpredictable effects are excluded from automatic selection.
- Custom consumables can still be configured manually through
allFoodsandextraHealConsumables.
Health Persistence
- Companion health now persists correctly when maximum health changes due to leveling or other bonuses.
- Companions that were at full health before gaining additional maximum health will remain full after relogging or chunk reloads.
- Injured companions will retain their previously saved health instead of being incorrectly healed or recalculated.
Weapon Enchantments
- Custom daggers, clubs, hammers, spears, quarterstaves, and glaives can now be enchanted normally in survival.
- These weapons now support applicable standard sword-compatible combat, durability, and repair enchantments.
Beastmaster Pet Safety
- Beastmaster pets, including non-tamable pets such as Ocelots, no longer flee from nearby players while following their Beastmaster.
- Companion and summoned-companion attacks can no longer damage Beastmaster pets while Companion Friendly Fire is disabled.
- The
friendlyFireCompanionssetting now controls damage between companions, summoned companions, and Beastmaster pets. - This protection applies to melee, ranged, magic, and summoned attacks.
- Enable
friendlyFireCompanionsif you want allied companions and Beastmaster pets to be able to damage one another.
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:428soLwa:GHQQGyhP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:428soLwa:GHQQGyhP"
}
