When a mod contains forge mod, coremod and mixin, the forge mod won't be loaded when used as dependency in dev environment

[Niko-sk2x]

MalisisCore is an issue again.

I probably just didn't notice it before when testing. The coremod and mixins load jut find, but the forge mod isn't loaded at all.

Log: https://pastebin.com/raw/NxuJqDqf

[Mumfrey]

But from the log it looks like it's specified on the command line, so are you sure you're running with --noCoreSearch? Basically mixin isn't managing the injection of the coremod if it's specified on the command line, which is an intentional situation generated as a solution to the previous issue.

[Niko-sk2x]

I tried with --noCoreSearch before, and thought maybe that was the issue so I removed that argument. I will post a log with --noCoreSearch in a few minutes.

[Niko-sk2x]

The log (cut after starting loading world because there was my own debug spam at starting from there):
log_mixin_malisiscore.txt

[Mumfrey]

All indications are that things are working as normal, can you verify that the malisis jar definitely contains an FMLCorePluginContainsFMLMod entry?

[Niko-sk2x]

This is the whole MANIFEST.MF copied as is

Manifest-Version: 1.0
Implementation-Title: jar
Implementation-Version: 1.12-6.0.5-SNAPSHOT
Built-By: Ordinastie
FMLAT: malisiscore_at.cfg
TweakClass: org.spongepowered.asm.launch.MixinTweaker
Implementation-Vendor: http://github.com/Ordinastie/MalisisCore
TweakOrder: 0
MixinConfigs: mixins.malisiscore.core.json
FMLCorePluginContainsFMLMod: true
ForceLoadAsMod: true
Created-By: 25.131-b11 (Oracle Corporation)
FMLCorePlugin: net.malisis.core.asm.MalisisCorePlugin

[Mumfrey]

Sorry I've been over the log with a fine-tooth comb and I seriously can't see anything wrong, everything looks like it should, I'm completely baffled as to why it wouldn't work unless there's some underlying issue in FML that we're inadvertently tripping over.

Literally as far as I can tell, the mixin fml agent is doing exactly what it's supposed to at exactly the right times. I have no idea how to proceed to be honest, we might need to get someone from forge to take a look at it.

[Niko-sk2x]

Oh well, right now I can get things to more-or-less "work" without the mod being loaded (all GUI textures are missing), even if forge complains about impossible errors. So I ca wait for it to be fixed.

Note that I will be away for the next 2 weeks, maybe with internet access on my phone. So if I don't reply, that's why.

I am having the same issue. My forge mod isn't being loaded at all when trying to use mixins with it in a development environment.

[Mumfrey]

I am having the same issue. My forge mod isn't being loaded at all when trying to use mixins with it in a development environment.

@V0idSt4r Open an issue, provide logs, you cannot just piggy-back on someone else's issue. This specific issue pertains to a very specific situation with using deobfCompile dependencies containing mixins and also a regular @Mod-annotated classes, it is not a general-purpose bandwagon thread, this is not a forum. Saying "me too" with no corollary evidence or even a basic description of your current setup and previously-taken troubleshooting steps just serves to pollute a perfectly sensible issue with unhelpful line noise.

Either make a new issue describing your problem, or provide logs to support and enhance this issue, but do not post further banal nonsense because I'll just delete it as off-topic next time.

This very specific situation happens to be the exact same situation I'm in. My mod has a coremod and a normal mod but is not being loaded, mixins is working fine. I don't see why it's necessary to open a new issue you'll just be copy pasting the same messages to both issues to get it solved.

[Mumfrey]

But you keep saying "your mod", when this issue is not about a mod, but is specifically about a mod being used as a dependency in development. You also still haven't provided any logs so I don't know what you're adding to this issue by simply saying "me too"?

Are you talking about your mod not being loaded from a jar container in production? Are you talking about it not loading as a deobfCompile dependency in development in someone else's workspace? You haven't provided any useful primary or corollary information about your issue, so your comments on this issue are of zero practical use to me in trying to rectify any underlying issue.

Provide some actual information, or open a new issue if your problem does not fit the criteria outlined above.

Yes, as a dependency in development. I'll provide logs when I get home today but I didn't see anything suspicious.

[Niko-sk2x]

Any progress on this? The issue makes it near impossible to work work on some parts of my code. I really don't know what other information I could provide to help find the issue.

[Mumfrey]

I've not investigated any further because as far as I can tell this is not a fault with Mixin. @V0idSt4r said he was going to provide logs since he's having the same issue but didn't actually do so. There's no indication from FML as to why it's skipping the malisis core container, by all accounts the normal discovery process does two things: it adds the container to the reparseable collection, and injects it into the classloader. Since the file is already in the classloader and mixin is adding the container to the reparseable collection itself (as shown in the logs) it just doesn't make sense why it wouldn't scan it, because the behaviour should basically be the same.