1.5.1
Compatibility
Changes
New Loader Support
MedievalPlus now officially supports Folia, the neccessary plugin settings and implementation of regions have been made and its now fully functional on both loaders. Additionally, the plugin has been tested for Purpur and seems to run without issues there too, so consider this the official statement for its support.
New Command - MpMob
A general trouble of development and something which offers more unique customization. The /mpmob <mob_id> command allows to spawn in any custom medieval plus mob. All ids are auto completed and this also features single mobs which are normally only present in their respective events like the thief or piglin_pirate_captain. The command takes the senders position as position, so it can be used in command blocks and respects execute positioned as position argument. It comes with the permission medievalplus.mpmob which is granted to ops per default.
Fixed some Issues & Adjustments
- Fixed an issue where the golden axe dropped by PiglinSmith would not have proper attributes and behaved like a non-weapon item
- Readded custom heads for KatanaSmith and UndeadSamurai as they somehow got lost
- Stopped evolutions like the DeepSeaDrowned and DryOceanPiglin from dropping their leather armor. Mobs equipped with real armor will still drop them, but now "cosmetic" leather armor will not be dropped again
- Adjusted some weapon drop rates of evos to feel more in line with minecraft, like the harpoon
- Removed the Chain Scythe Forging Template drop from WitherReaper as it can be found in fortress chests already
Optional dependencies
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:dQlmFWNb:kgQ5lDoc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dQlmFWNb:kgQ5lDoc"
}

