Question related to configuration of coremods/coremod guidelines

[Kitlith 1]

A few days ago, I created a coremod called OldBoosters, made a thread here, etc. Then I realized that it didn't follow the coremod guidelines.

 

Signing the jar is something I need to do, as well as not bundle/fatjar/etc. the mixin library. However, first I need to seperate the coremod from the forge mod.

 

Technically, I could say that's already done, I just need to jar them separately, maybe use jar in jar to load the mod from the coremod or visa versa. However, all the mod is doing is providing configuration to the coremod using an @Config annotation, so I was wondering if there's a better way to provide configuration to a coremod.

 

Am I understanding the guidelines correctly in what I need to do? Is there a better way to provide the configuration I'd like?

[Cadiboo 365]

Anything to do with coremodding isn’t supported on this forum

[diesieben07 7696]

The coremod should do nothing besides what must be done in a coremod. All logic should reside in your mod. The coremod does not need config, it only transforms classes.