Links
Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 4 months ago
All versions
6.1.1
Release
RPG Tweaks 6.1.14 months ago 117
Compatibility
Minecraft: Java Edition
1.21.1–1.21.8
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Changelog — RPG Tweaks 6.1.1
✨ New Features
Sleep + FTB Quests Integration
- Added quest-gated sleep: configure a single FTB Quests Reward ID to block all players from sleeping until they individually claim it.
- Players who have claimed the reward can sleep normally; those who have not will receive a message and be blocked.
- Configurable via the Sleep category in the mod config screen (only visible when FTB Quests is installed).
Skill Locks Book (Reskillable Reimagined)
- Press
Lin-game to open the Skill Locks Book, a paginated GUI showing all items configured inskill_locks.json. - Items are organized by skill category in a sidebar. Each entry displays the item icon, name, required skill level, and unlock status (green ✔ if unlocked, red ✘ if not) based on the current player's skill levels.
- Navigation uses a book layout showing up to 4 items per sheet.
- Custom skills defined in
custom_skills.jsonare fully supported. - Keybind is configurable in Minecraft's Controls menu under the RPG Tweaks category.
🐛 Bug Fixes
- Mob Kill XP data loss: Configuring Kill XP for a mob and then opening a sack tier sub-screen before saving caused the XP values to be discarded. Kill XP is now configured in its own dedicated sub-screen, eliminating the unsaved state issue.
- Ore XP reset to (0, 0): Using
/rpg_tweaks config reset ore_xpor resetting a specific ore entry via command was setting XP values to (0, 0) instead of restoring vanilla defaults. Reset now correctly restores the original default values for all vanilla ore tags and blocks.
Optional dependencies
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:BokILEuA:edig3h54"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BokILEuA:edig3h54"
}



