floader missing?

[ember sigil]

I'm trying to update a mod to 26.1 but floader is acting like it doesn't exist...

I've updated and temporarily disabled as many dependencies as possible, but it's still complaining that mixinextras requires floader >= 0.14.25 (I have 0.18.6).

This is in dev.

https://gitlab.com/supersaiyansubtlety-group/minecraft-mods/defaulted_drops/-/tree/26.1-dep-res-test

[lucid cosmos]

That's pretty strange, does it still happen if you use 0.18.5?

[ember sigil]

trying now
it did the same thing on 18.4 though

yeah same on 18.5

[blissful fable]

//test_mod:build.gradle L19
dependency dependencies.implementation(dependencies.project(path: ':mod'))

//test_mod:build.gradle L19
dependency(dependencies.implementation(dependencies.project(path: ':mod')) {
  exclude(module: "net.fabricmc:fabric-loader")
})

try something like this

[tropic shale]

MixinExtras requires fabricloader>=0.14.25, the system considers it 'missing'. there are actually two different fabric loader instances conflicting with each other. One comes from your main environment(0.18.6), and the other is brought in again as a dependency by one of your modules (likely a mod module). When MixinExtras checks, it only recognizes the wrong one, or the environment variable error causes the detection to fail.// You might have originally written:
// implementation project(':mod')

// Change to:
implementation(project(':mod')) {
exclude group: 'net.fabricmc', module: 'fabric-loader'
}

plugins {
id 'java'
id 'common'
id 'net.fabricmc.fabric-loom'
}

java {
toolchain {
languageVersion = JavaLanguageVersion.of(java_version)
}
}

loom {
runs {
client {
// This will also add the mod module to the development environment
ideConfigGenerated true
}
}
}

repositories {
maven {
name = "defaulted_drops-GitLab"
url = "https://gitlab.com/api/v4/projects/32841879/packages/maven"
}
}

dependencies {
minecraft libs.minecraft
implementation libs.fabric.loader // ← Loom
implementation libs.fabric.api
implementation(project(':mod')) {
exclude group: 'net.fabricmc', module: 'fabric-loader'
}
}

processResources {
final expanding = [ VERSION: project.version ]
inputs.property('VERSION', project.version)
expanding.putAll sssModMin.fmjExpansion.configureExpansions(processResources, project)
filesMatching('fabric.mod.json') {
expand(expanding)
}
}

[blissful fable]

I mean, there aren't quite two instances of fabric loader.

What happens is that you tell loom that fabric loader is part of your mod, and not a mod itself

And it believes you

The check doesn't actually have anything to do with mixinextras. Any mod that depends on fabric loader will fail in dev

But in prod, the classpath groups are setup correctly and this isn't a problem

[ember sigil]

hm, I tried the exclude methods you each suggested but the issue persists

[blissful fable]

Hmm

I'll give your project a clone in a bit

[ember sigil]

oh, this in the loom mods deps at least gives a different error

dependency(dependencies.implementation(dependencies.project(path: ':mod')) {
    exclude(group: "net.fabricmc", module: "fabric-loader")
})

looks like I need newer java

[blissful fable]

Oh yeah, you don't need to exclude in the dependencies block

Gradle will sort that

[ember sigil]

it didn't work with module: "net.fabricmc:fabric-loader", I had to separate them

but now with java 25 the error is something my mod is doing 🎉
that I should be able to track down

thanks for the help!

[blissful fable]

Oh oops

Makes sense