Links
Tags
Creators
Details
1.1.0
Compatibility
Changes
✨ v1.1.0
🎒 Soulbound Upgrade (new)
A new functional upgrade with its own Oraxen texture. A backpack with this upgrade stays with you when you die instead of dropping, and you keep it after respawn.
- Dupe-safe next to grave/deadbody plugins: the death handler runs at
LOWESTpriority and removes soulbound backpacks from the death drops before grave plugins read them. Backpack content lives server-side by ID, so even a stray copy would share the same storage (no content dupe). A per-player instance guard prevents double-restore, with a join fallback for relog-while-dead. - Recipe: Totem of Undying + Soul Soil around Upgrade Leather (configurable).
🎨 Carried backpack now uses your colors (fix)
The carried/held Oraxen backpack baked the tier color into its overlay layer, which sits on top and hid the tinted base (main color) and the swapped accent — e.g. an Emerald backpack stayed green, and dyeing the accent didn't fully show. The overlay is now neutral / tier-independent, so the body takes your main color (dyeable base) and the accent variant colors the straps/pockets — the same principle as the v1.0.9 fix for placed backpacks.
Resource-pack change – run
/oraxen reloadonce after updating. Existing backpacks refresh automatically on open/join.
🧹 Chores
- Oraxen
asset-version6 → 7,config-version8 → 9 (auto-migrates; old config backed up).
Installation: drop yourShika-Backpacks-1.1.0.jar into plugins/ on Paper 26.1.2 (Java 25), then run /oraxen reload.
Full Changelog: https://github.com/yourShika/yourShika-Backpacks/compare/v1.0.9...v1.1.0
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:1qdzviDZ:f8mwdyTG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1qdzviDZ:f8mwdyTG"
}

