1.5.0
Compatibility
Changes
Ambience Update
This update aims to improve the general ambience of how medievalPlus affects the world, not in a direct stept but rather helps refine the existing world to feel more natural.
Ressource Pack
After quite some time an official ressource pack has finally emerged! This is ready to drop in on existing servers even without this version upgrade as the custom data models needed are already present since v1.0. The pack features unique design for each forgery and applies vanilla-style materials for tiered materials. This is a first but it seems to have turned out well, even incorporating 3D models for the tridents and shields, thanks to Blockbench.
The ressource pack is its own project though, it should be linked to this version but you can also get it from here: Ressource Pack
Finding templates in structures
A few forgery templates were in a kinda loose spot, with only specific enemies dropping even an already forged weapon as only source. In order to make these forgeries feel more natural, certain minecraft strutures now have a possibility of including forgery templates in their loot. You can check out this new info in the MpGuide but here's a quick overview:
- Chain Scythe: 50% in Nether Bridge (minecraft name for fortress chests)
- Firebalde: 20% in Nether Bridge
- Iceblade: 100% in Igloo
- Poisonblade: 60% in Jungle Temple (both chests can have it)
- Pick: 50% in Mineshaft, Dungeon and non-library stronghold chests
- Saber: 50% in Shipwrecks (for added pirate ambience)
Additionally, this new feature also displays Great Hammer being found in Trial Chambers, which it already was before but it was not noted. (20% to aquire when completing a trial spawner)
Small Fixes
- The page count inside Forgery guide had an issue since lance was added, so essentially the default template was not displayed, now page 3 is added back again
- Fixed an issue where Great Hammer Forging Template could be dropped multiple times from one trial spawner if multiple items were ejected
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:4USO4y6b"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dQlmFWNb:4USO4y6b"
}

