Links
Tags
Creators
Details
1.16.5-2.1.2
Compatibility
Changes
Compatibility Fixes:
- Changed the version required for Botania from "409" to "1.16.3-409". This should fix any compatibility issues people are having with newer versions of Minecraft Forge.
Misc Tweaks:
- Re-coloured the Bronze Shields slightly to use a new palette that I think looks better imo. This will be more obvious when in the next major Spartan Weaponry release.
- Updated Forge version to 36.1.2 on Minecraft 1.16.5
Changes in version "2.1.1":
Bugfixes:
- Fixed the attribute values for Obsidian Shields. They were supposed to give a 30% decrease in speed, rather than a 70% increase. Oops.
Changes in release version "2.1.0":
Bugfixes:
- Removed the Lexica Botania extension data from this mod, at least temporarily. This is due to the Patchouli mod (that the Lexica Botania uses to make the book work) being in more widespread use amongst other mods. If Botania isn't installed but Patchouli is, then it causes serious issues including lag and crashing. If you want this back, I'll consider making a data pack that will restore this. Just keep in mind that this requires both Spartan Shields and Botania to be installed to use it correctly.
Tweaks:
- Reduced the console spam when attempting to stitching textures (which is used for adding the Tower Shield textures). It should only come up once when the Tower Shield textures has been added now.
Changes in version "2.1.0 beta-1":
Additions:
- Netherite Strengthened Shield
Can be upgraded from a Diamond Reinforced Shield in a Smithing Table by using a Netherite Ingot
- Netherite Tower Shield
Same as above but using a Diamond Tower Shield instead
- JEI Integration
Hang on a sec, what would we need JEI integration for? Simple. It adds a recipe category that shows how to apply banners to shields.
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:W5rjEyqs:NxUo9uS1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:W5rjEyqs:NxUo9uS1"
}

