All versions
3.4.0-fabric-1.21.1
Release
Mebahel's RPG - Villager Quests & Companions 3.4.0-fabric-1.21.13 weeks ago 139
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Client and server
Changes
Mebahel's RPG - Villager Quests & Companions v3.4.0
Minecraft 1.21.1
What's new
- Courier deliveries: A courier can now find you outdoors during the day and hand over Quest Books through a conversation. If several letters are ready, they arrive in one visit. Read each book when you are ready to begin its quest.
- A new path for Rusk: Sparing the witness in False Hero can lead to a letter from him and a new quest branch. Follow his story to uncover the Black-Road Ledger and decide whether he earns a place at your side.
- Blackthorn House: A new quest line begins with a mysterious invitation and leads you through the house's long-buried secrets. Spare Merrin, the skeleton steward, and see his story through to recruit him as a companion. He will fight alongside you when the house's former servants appear.
- More companion control: Tell companions to follow, wait, guard an area, or change their combat stance. You can also set or change their home, summon official companions with commands, and have guards use doors.
Improvements and fixes
- Companions now join fights against enemies you attack when they have no target and gradually recover health after 10 seconds out of combat. Allies involved in the Rusk and No Banner quests also help during their fights.
- Iron golems leave companions and recruitable quest allies alone. Companion names remain visible to their owner within 32 blocks, even when they are not being aimed at.
- Dialogue choices transition smoothly, with improved scrolling for long lists and no flicker when the speaker's line stays the same. Rusk's mercy dialogue has also been expanded.
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:jNqtpcJu:syUCaydy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jNqtpcJu:syUCaydy"
}

