Exception in thread "main" java.lang.module.ResolutionException: Modules tklib and supercircuitmaker export package com.technicalitiesmc.lib.circuit.interfaces.wire to module trashcans
at java.base/java.lang.module.Resolver.resolveFail(Resolver.java:901)
at java.base/java.lang.module.Resolver.failTwoSuppliers(Resolver.java:815)
at java.base/java.lang.module.Resolver.checkExportSuppliers(Resolver.java:736)
at java.base/java.lang.module.Resolver.finish(Resolver.java:380)
at java.base/java.lang.module.Configuration.(Configuration.java:140)
at java.base/java.lang.module.Configuration.resolveAndBind(Configuration.java:494)
at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.ModuleLayerHandler.buildLayer(ModuleLayerHandler.java:70)
at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.TransformationServicesHandler.buildTransformingClassLoader(TransformationServicesHandler.java:61)
at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.run(Launcher.java:104)
at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.main(Launcher.java:77)
at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26)
at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23)
at [email protected]/cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:90)

Alrighty, let's call it that then. Thanks! :)

I just ran into this issue and I apparently also had several mod jars with different versions in my instance - Removing the older jars fixed the issue, so I'd say you can call this fixed :)

Alright, it turned out that Curseforge is being stupid, and when you update a mod, leaves the original jar in the folder. I eventually gave up on hunting them down and remade the modpack manually, and it promptly worked. Sorry for the trouble.

Hey! What version of the mod is this?

I know someone who had this issue because I shipped Super Circuit Maker and TKLib in the same file, but the latest release (0.1.4) splits them into separate files, which should fix it.

That's really really odd. I just downloaded 0.1.4 and doesn't have any com.technicalitiesmc.lib packages anymore, so I don't see how that could be happening...

Could I have the full latest.log and debug.log files? There might be some more useful info there.

I am having the same issue, but every time I launch it says a different mod instead of trashcans. Interestingly, the issue persists even if SCM and TKLib are disabled, or backdated to an older version. I presently can't launch the pack I have this in on forge, even if I disable SCM altogether.

I can send you some log files if that helps

Here are some log files: Let me know if you think we need to delete some library files or something. When I have time later today I am going to try a new install and run some tests like if running just SCM on what versions causes the crash etc.
Logs.zip

Now that one's interesting. That pack seems to have multiple versions of several mods, including SCM.

SereneSeasons-1.18.1-6.0.0.10-universal.jar
SereneSeasons-1.18.1-6.0.0.8-universal.jar
shetiphiancore-1.18-3.10.0.jar
shetiphiancore-1.18-3.10.1.jar
Shrines-1.18.1-3.0.0-Beta4.jar
Shrines-1.18.1-3.0.0-Beta7.jar
SuperCircuitMaker2-1.18.1_0.1.0.jar
SuperCircuitMaker2-1.18.1_0.1.4.jar
[...]

My suspicion here is that when Forge is trying to figure out which of those is the latest version, it's loading both, and the old one is causing issues.

Can you try to see what happens when you manually remove SuperCircuitMaker2-1.18.1_0.1.0.jar?

Oh wild I didn't notice lol.
The issue seems to be with curse not removing mods when I updated them, only adding the new file and not removing the old. In fact, it looks like my attempts at backdating SCM may have gotten out of hand haha...

.

That appears to have fixed the issue, sorry for bothering you with this, I didn't think to look for duplicates since all I had done with this pack was update some mods. I should have payed attention to that, all I saw was SCM attached to the fatal error and assumed that was the issue. Thanks for the help!

CurseForge has a bug where it currently doesn't properly delete the old file when updating a mod. They are working on a hotfix right now. For more info see the announcements channel on the CurseForge discord.

No worries! Let's hope CurseForge can fix the issue soon and that this is indeed what's happening with @Delta4Phoenix's instance as well :)