Tags
Creators
Details
All versions
1.3.0
Release
MCA Capitals 1.3.0 - Fabric 1.21.12 months ago 758
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
Changes
- Completely overhauled dialogue and localization. Nearly all player-facing text is now fully translatable, including dialogue, menus, diplomacy, justice, decrees, titles, notices and command feedback.
- Personality-based dialogue expanded. Villagers now use dedicated dialogue based on their MCA personality, rank and court office.
- Added Talk of the Town evening conversations. Villagers can naturally talk to one another in short call-and-response conversations around the Capital.
- Expanded dynamic dialogue. Villagers can naturally reference the Sovereign, Hand, heir, Herald, Ambassador, Master of Laws, noble houses, foreign Capitals and other people or offices.
- Chronicles remain tied to individual Capitals. Bound Chronicles continue opening their own Capital, while new Chronicles bind to the Capital the player is currently visiting.
- Added Herald announcement variety. Each Herald event can choose from three different proclamations, with more natural use of titles such as “Her Majesty, His Royal Highness, and Her Grace.”
- Improved royal and noble forms of address. Sovereigns, heirs, princes, princesses, dukes and duchesses are referenced more naturally by title, name and appropriate honorific.
- Improved multiplayer localization. Clients receive translatable text and semantic identities instead of finished server-side English.
- MCA movement states now use MCA's actual Staying/Following state instead of reading localized text.
Bug Fixes
- Fixed a bug wherein Capitals did not appropriately honor the MCA Reborn config option for displaying Name Tags. Name tags should now be hidden when disabled in MCA Reborn config options
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:tHmppiXj:vsTwvK7u"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tHmppiXj:vsTwvK7u"
}

