Tags
Creators
Details
Licensed CC-BY-SA-4.0
Published 5 months ago
Updated last week
All versions
1.3.1
Release
Fiw Custom Items 1.3.1 (fabric 1.21.8)last month 16
Compatibility
Minecraft: Java Edition
1.21.8
Platform
Fabric
Supported environments
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Changes
[1.3.1] - NeoForge Kotlin crash fix and boss phase tools
NeoForge users running Kotlin for Forge or KotlinLangForge: update immediately. 1.3.0 crashes those packs at startup.
Fixed
- NeoForge startup crash next to Kotlin for Forge / KotlinLangForge (#1). The NeoForge jars
merged the Kotlin standard library's classes into the mod jar, so the
fiw_toolsmodule exportedkotlin.*packages and module resolution failed (ResolutionException: Modules fiw_tools and kotlin.stdlib export package ...). Kotlin now ships as a nested Jar-in-Jar library: NeoForge deduplicates it against any other mod's copy and loads the newest. Fiw Custom Items still needs no extra Kotlin mod on NeoForge. Affected NeoForge 1.21.1, 1.21.8 and 1.21.11; Fabric was not affected.
Added
on_boss_phasetrigger — fires held and worn item abilities for players near a FIW Bosses boss when it changes phase, with the boss as the target. Filter withrange,phase(only when entering that phase) andbosses(boss config ids). Needs FIW Bosses 1.2.0+.boss_phaseability — admin tool that moves a FIW Bosses boss to thenext,prev, or asetphase without touching its HP. Operator-only by default (requireOp). A refused use says why (single-phase boss, already first/last phase, fight not started), at most once per second. Example:examples/fiw_bosses_integration/items/phase_warden_rod.json;raiders_sigil.jsonshowson_boss_phase.
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:VHLQczbA:bSeqH32V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VHLQczbA:bSeqH32V"
}

