Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
2.0.0
A ground-up rewrite. The altar/scroll mechanic from 1.x is removed entirely; respec now runs through a /respec command. Old config files (respec-skill.toml) are ignored — a fresh respec-skill.properties is written on first launch.
Game/Loader support
- Updated to Minecraft 26.1.2
Player-facing changes
- New:
/respecopens a chat-clickable menu listing every Puffish skill category loaded on the server. - New:
/respec <namespace:category>performs the respec directly (used by the menu's[Reset]button). - New: Every Puffish category is auto-discovered from
SkillsAPI.streamCategories()— admins no longer have to list categories in the config. - New: Per-respec cost is paid from the player's inventory (default: 16 emeralds; configurable).
- New: Optional per-player cooldown (
cooldown_seconds, in-memory only — resets on server restart). - Removed: Respec Scroll item, the recipe, the lodestone-on-base-block altar mechanic, and the
UseBlockCallbackhandler.
Prestige
- One-way ascensions from one category into another. Configure with
prestige.<n> = <from>, <to>, <min_points>, <xp_carryover_factor>, <cost_item>, <cost_count>. /respec prestigelists configured paths (ineligible ones are shown greyed out with current vs required points)./respec prestige <from_category>executes the ascension: source category is erased, target category gainscurrentXp × xp_carryover_factor, cost is consumed.- When any prestige path is configured,
/respeclinks to the prestige menu at the bottom of its output.
Migration from 1.x
- Delete (or ignore) the old
respec-skill.toml. A newrespec-skill.propertieswill be generated on first launch. - Tell players the altar/scroll is gone — they use
/respecnow. - If you were using prestige in 1.x, port the mappings to the new schema (see Prestige section in the README). 1.x prestige used
from_skill(path only); 2.x uses fullnamespace:pathidentifiers.
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:qDLXlSn1:TJVPbIll"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qDLXlSn1:TJVPbIll"
}

