Links
Tags
Creators
Details
0.6.3
Compatibility
Changes
0.6.3 Build no longer hard-requires JDK 21 toolchain. Gradle now uses installed JDK (including Java 21) while compiling with --release 17. This improves offline/low-bandwidth setup and keeps runtime compatibility for Java 17 servers. Added helper script build-java17-compatible.ps1 to auto-detect local JDK 17+ and run Gradle without manual JAVA_HOME setup. 0.6.2 Added functional rift item stat combat pipeline (attack/defense/speed) so statted drops now affect damage and mitigation in real fights. Added active artifact system: right-click with artifact in main hand (and empty off-hand) grants timed buffs with cooldown. Added weapon progression system up to level 1000 with XP-on-kill, level scaling, and dynamic lore updates. Added world chest integration for rift loot injection, including boosted chances in ruined portals and high-tier structures. Extended progression defaults: max zones 150, mob max level 1000, skill max level 1000. Increased monster progression pace and ability trigger rates for more aggressive RPG combat flow. Added new config sections: itemStats, itemProgression, artifactActive, worldLoot. Updated version metadata to 0.6.2. 0.6.1 Fixed rift teleport cancellation bug: legitimate portal-driven teleports to fx_rift_* worlds are now allowed. Hardened portal entry detection with service-side cooldown and periodic proximity checks for more reliable entry. Updated movement-based portal detection to use PlayerMoveEvent#getTo location. Upgraded Solo-style portal visuals with denser double-ring sigils, stronger spiral vortex core, and safe particle fallback mode. Updated plugin/build/config version metadata to
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:v1yHN2vV:PnQSJohT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v1yHN2vV:PnQSJohT"
}

