Included content
| Name | |
|---|---|
Lifeskill System API — Core lifeskill data framework for registering player lifeskills via datapacks. Includes its own UI tab with EXP sources grid, ability list, bonus drop display (with loot table support), and progress timeline. Supports expSourceTags (TagKey<Block>) for block tag-based EXP sources alongside custom per-block overrides. Loot tables and tag contents are resolved server-side and synced to client via component auto-sync.
Enchantment Element Conversion — Weapon enchantments now modify elemental damage ratios. Blends based on enchantment level (e.g. Fire Aspect 1 = 50% fire, Fire Aspect 2 = 100% fire). Tooltip updates in real-time to reflect enchantment-modified elements.
| Enchantment | Element | Lv1 | Lv2 | Lv3 | Lv4 | Lv5 |
|---|---|---|---|---|---|---|
| Fire Aspect | Fire | 50% | 100% | — | — | — |
| Flame | Fire | 100% | — | — | — | — |
| Channeling | Electric | 100% | — | — | — | — |
| Smite | Holy | 20% | 40% | 60% | 80% | 100% |
| Bane of Arthropods | Poison | 20% | 40% | 60% | 80% | 100% |
Burning Projectile → Fire Element — Projectiles that are on fire (lava, fire blocks, etc.) now deal fire elemental damage instead of neutral.
ImGui Intregate — Added ImGui for in-game debug UI. Access via right shift Currently just the light engine properties for easy reference during development.
canEvolveFrom() compared PlayerClass instances by object reference (==), which broke after datapack reloads rebuilt the registry with new objects. Now compares by Identifier so evolution works reliably regardless of registry rebuilds.experienceToNextLevel was not recalculated when evolving to a new class, causing the EXP bar to display the previous class's threshold (e.g. 340 instead of 60). Now properly calls updateNextLvl() after resetting level.| Item | Element |
|---|---|
| Golden Sword | Neutral |
| Golden Spear | Neutral |
| Golden Axe | Neutral |
| Netherite Axe | Neutral |
| Mace | Neutral |
| Trident | Neutral (combat: Melee) |
exam usage (this not include in game)
| Name | |
|---|---|
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.
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:8PTlAPLJ:HlRWvhyB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8PTlAPLJ:HlRWvhyB"
}