Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 2 months ago
All versions
1.3.10
Release
Cuffed - 1.3.10 - Forge - 1.20last year 186
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Additions
- Added a new config option for whether or not to drop heads from the guillotine
- You can now escort a player to a bunk click it to force-set their spawn.
- Added the bundle recipe from 1.21 to make it craftable for Cuffed
- Restraints can now be equipped/unequipped by sneaking and left clicking while look at your feet/forward/head to equip/unequip legs/arms/head respectively. Still requires keys and sneaking to unequip restraints.
Fixes
- Fixed Epic Fight compat crashing on startup in more recent epic fight versions.
- Fixed an issue causing players to be positioned wrong when escorting them to a pillory.
- Fixed guillotine doing damage instead of straight up killing the player.
- Added a usage tooltip to show how to use restraints.
- Added a tooltip to show what key removes each restraint.
- Fixed some tooltip errors, specifically on Handcuffs, Fuzzy Handcuffs, and Shackles.
- Fixed un-enchantable restraints not getting removed on death.
- Buffed mana drain from Drain enchantment to better counter Ars Novuea
- Fixed padlocks locking chests that are next to each other whether or not those chests are connected.
- Fixed Duck Tape restraining a player's arms
- Finally added Russion translation
- Removed A Warden's Guide recipe
- Fixed can_reinforce_padlock item tag containing an invalid item ("diamond_ingot" lol)
- Added Shadow Locked Away poster to the Creative Menu
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:KrZm8J8s:Ln8jvCRM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KrZm8J8s:Ln8jvCRM"
}

