All versions
3.3.0
Release
Shadow's Complexity Swords 3.3.0 (2ND ANNIVERSARY)3 months ago 26
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Server-side
Singleplayer
Changes
I have been waiting specifically until this day to update the mod. This is the 2nd anniversary update.
- Added the locked box. It can be combined with the key to unlock it and get a diamond block from it. I was gonna make it drop from Ravagers, but I couldn't do that so I switched to fishing, and I again couldn't do that so I made Journeyman fishermen villagers trade it for a fishing rod and 6 cooked salmon.
- Added the unlocked box. It can store six item stacks and is a leftover from combining the locked box with the key.
- Added silver chakri and divine chakri, the "Whisperer of Secrets".
- Added the Holy Greatsword. It serves as a mix of the Holy Dagger and Holy Silver, as it enchants itself like the former and has the same right-click function as the latter. This is the anniversary weapon.
- The Burning Dagger now enchants itself with Fire Aspect III when crafted. Who would've thought the 1st anniversary weapon would be updated in the 2nd anniversary update?
- Added weights. They're crafted with a steel rod and 2 iron ingots, and they give you a 20-second strength boost when used. They have 5 uses before breaking.
- Fixed the soapy sponge not returning a wet sponge when used to craft the Clean Slate.
- Fixed the Ordinary Travel Rune achievement being in its own category instead of being in Story.
- Added 2 new achievements, one for the Whisperer of Secrets and one for the Holy Greatsword. Beware that I accidentally marked the HG achievement as "silvergreatswordachievement" instead of "holygreatswordachievement".
- Made some more minor bugfixes.
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:YClk5MBV:EDfsIQ9N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YClk5MBV:EDfsIQ9N"
}

