Have you read the compatibility information above?

• Yes, I have read and understand the compatibility note.

Mod Loader

Fabric

Game Version

1.21.1

Mod Version

2.4.7

Environment Type

Other

Provide Your Logs

https://mclo.gs/l1Rwnd1

Describe Your Issue

Crash at the launch stage of the game when working with the modpack. If some mod is to blame, let me know and I'll remove it to use yours.

Steps to Reproduce

1. Download Mods.
2. Launch Minecraft.

This is an issue with Command Keys, they are jar-in-jaring an older version of Mixin Extras which is already included with Fabric Loader.

I would suggest you remove the mod for now and report this issue to them with the explanation I've given here.

I'll write to the author of commandkeys about this.

@IMB11 what makes this a CommandKeys issue? Fabric Loader has no trouble with multiple JiJ'ed versions, it automatically chooses the latest one - indeed if you install CK and Sounds normally they both work as expected.

@mrcrashmer AutoModpack should restructure the directory on first installation of the modpack (when you first join the server, download the modpack and restart the game) as shown below:

First launch

[11:32:15] [main/INFO]: Loading 58 mods:
	- automodpack-bootstrap 1.0.0
	   \-- automodpack 4.0.0-beta27
	        |-- fabric-api-base 0.4.42+6573ed8c19
	        etc.
	- commandkeys 2.3.8+1.21
	   \-- mixinextras 0.4.1 // JiJ
	- fabric-api 0.115.1+1.21.1
	   |-- fabric-api-base 0.4.42+6573ed8c19
	   etc.
	- fabricloader 0.16.10
	   \-- mixinextras 0.4.1 // JiJ
	- java 21
	- minecraft 1.21.1
	- modmenu 11.0.3
	- placeholder-api 2.4.2+1.21

Second launch, after joining the server and downloading the modpack, then restarting the game as instructed

[11:33:16] [main/INFO]: Loading 58 mods:
	- automodpack-bootstrap 1.0.0
	   \-- automodpack 4.0.0-beta27
	        |-- fabric-api-base 0.4.42+6573ed8c19
	        etc.
	- commandkeys 2.3.8+1.21 // JiJ ignored due to MEv0.5.0 standalone installation
	- fabric-api 0.115.1+1.21.1
	   |-- fabric-api-base 0.4.42+6573ed8c19
	   etc.
	- fabricloader 0.16.10 // JiJ ignored due to MEv0.5.0 standalone installation
	- java 21
	- minecraft 1.21.1
	- mixinextras 0.5.0-beta.5 // JiJ'ed by Sounds, installed separately by AutoModpack to ensure that it's included in the initial load
	- modmenu 11.0.3
	- placeholder-api 2.4.2+1.21
...
// automodpack now loads
...
[11:33:17] [main/INFO]: Loading 3 mods:
	- mru 1.0.8+1.21+fabric
	- sounds 2.4.7+1.21.1+fabric // JiJ ignored due to MEv0.5.0 standalone installation
	- yet_another_config_lib_v3 3.6.3+1.21.1-fabric

I don't know why AutoModpack isn't doing that in your case, I'd recommend creating a fresh instance and trying again, then if it still breaks, get in touch with their support.

To be clear, the issue here is that AutoModpack should (and normally does) adjust the JiJ'ed libraries to prevent conflicts caused by loading the modpack mods after the normal mods folder, but in your case, for whatever reason, it hasn't done that.

Thank you so much for the information. Unfortunately, I know everything except mod development.

Sounds jar in jars mixin extras 0.5 beta

Yes, it does. So?

AutoModpack shouldn't be messing with mods JIJ stuff, I don't really know what the problem is here then but clearly it's got nothing to do with Sounds

I'm not saying it does, neither Sounds nor CommandKeys are doing anything wrong. AutoModpack has to mess with the JiJ to make it work with its two-step loading. That isn't normally an issue, but for some reason in OP's case AutoModpack isn't doing its job properly, that's all.

Hence why I directed OP to AutoModpack support.