Tags
Creators
Details
0.9.4-alpha-1.21.1
Compatibility
Changes
This update improves resource scanning stability when testing Complexity Analyzer in development environments. Bundled web packs inside packaged archives are now properly detected and loaded instead of being skipped.
๐ฅ What's New for Developers
- Packaged JAR Scanning:
- Dev-Mode Build Testing: Added support for reading web packs directly from
.jarfiles in development mode, allowing you to test packaged mod builds locally without manual resource extraction.
- Dev-Mode Build Testing: Added support for reading web packs directly from
โก Performance & Stability
- Mod Asset Discovery (
WebPackScanner): Resolved an issue whereComplexityAnalyzerskipped its own resources in dev environments by verifying the file path against.jarinstead of unconditionally discarding the mod ID.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| complexityanalyzer-0.9.4-alpha-1.21.1-sources.jar | Unknown | 1.16 MiB |
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:RQjlpUyI:CSYICjHj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RQjlpUyI:CSYICjHj"
}

