Tags
Creators
Details
v1.0.25
Compatibility
Required content
Changes
Automated release for version 1.0.25.
Changelog: Merge pull request #32 from JammingDino/detached14
feat(ui): add radial menu for activated skills
Implemented an interactive Radial Skill Screen () that allows players to select and trigger active skills.
Key Features:
- Activation Logic: Added Trigger Type. Skills with this trigger are automatically collected and displayed on the radial menu.
- Visuals: Custom procedural rendering for the Donut menu, including dynamic pie slices, hover expansion, and icon scaling.
- Controls: Bound to 'R' key by default. Menu opens on press, triggers selected skill on release.
feat: implement skill cooldowns and fix editor persistence
Added a comprehensive cooldown system for activated skills and resolved data loss issues in the Developer Editor.
Skill Cooldown System:
- Data: Added field to Skill JSON schema (defaults to 0 ticks).
- Logic: Implemented server-side enforcement in to prevent skill abuse. Cooldowns are tracked per-player via and persist through world time.
- Visuals: Updated with a high-fidelity clock sweep overlay, and a precise countdown timer positioned below the icon.
Developer Editor Fixes:
- Persistence: Updated to include and fields. These now correctly persist in the local autosave file when closing and reopening the editor.
feat: expand skill library with Pyro tree
New Skill Content:
- Pyromancer Branch: Added a full linear progression (Pyro I-V) plus the offshoot. Includes lava speed bonuses, fire/wither immunity, and hit-based combustion.
- Combat & Mobility: - : A high-tier active skill providing powerful buffs at the cost of self-immolation. - : An active movement ability allowing for directional launches.
- Survival: - : A reactive skill that triggers emergency regeneration when taking damage at low health.
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:dnC6tCcs:bMyrktck"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dnC6tCcs:bMyrktck"
}


