
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.62
Compatibility
Changes
Modern Companions 3.62
Recruitment and configuration
- Added configurable recruitment requirements through
recruitmentRequirements. - Requirements use
companion_id|item_id|countrows and support:- Multiple required items per companion
*wildcard defaults- Vanilla and modded registry IDs
- Random requirements for companions without overrides
- Recruitment requirements now synchronize and persist as arbitrary-length lists while remaining compatible with older saves.
- Customized
allFoodslists are now authoritative for healing, favorites, and recruitment. The default list still automatically discovers safe foods from other mods. - Added a complete configuration reference in
config/Explanation.md. - Fixed recruitment messages so food names resolve correctly for clients and modded items.
Cleric combat and support
- Clerics now prioritize:
- Healing their owner
- Healing other companions
- Healing themselves
- Firing holy spark projectiles
- Melee combat as a final fallback
- Holy sparks use holy-colored particle effects and deal double damage to undead.
- Clerics keep their distance while healing or using ranged attacks, then close in when forced into melee.
- Melee and magic projectile kills now allow Clerics to gain combat experience.
- Cleric support spells and holy sparks cost 6 Mana instead of 10.
- Mana regeneration is slightly faster for all magical companions.
- Clerics no longer spend Mana on unrelated utility spells before healing priorities are handled.
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:dVxg7Vdp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:428soLwa:dVxg7Vdp"
}
