Links
Tags
Creators
Details
All versions
1.2.0+26.2-neoforge
Release
Keep My Sword 1.2.0 — 26.2 Neoforge5 days ago 11
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Keep My Sword 1.2.0
Features & Improvements
- TOML configuration: Added
config/keep_my_sword.tomlloaded via NightConfig on game startup (restart required after edits). - Item exclusion list: Added
excludedItemsto configure items that bypass broken-item protection. Supports item IDs (such as"minecraft:diamond_sword") and item tags (such as"#slashblade:swords"). Defaults to an empty list[]. - Existing compatibility: The native
#keep_my_sword:excludeditem tag remains fully supported alongside the configuration file. - Core behavior preserved: Broken equipment protection, anvil repair mechanics, and item data persistence remain unchanged.
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:pPO0fpz4:H3ADufyg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pPO0fpz4:H3ADufyg"
}

