will mcmod.info get rolled in to @Mod?

[leftler]

It seems that @Mod and mcmod.info share a lot of the same features. Is the plan to phase out mcmod.info and just only use @Mod or does mcmod.info still have a future?

[Viper283]

i would prefer if it was in the @Mod as it makes it easier and you it's easier to maintain, but they should keep the ability for a mcmod.info just for compatibility

[OvermindDL1]

The mcmod.info being a separate file is for easy parsing *before* the class files start loading.

[REDX36]

Perhaps both will be compatible? And if both are present, it will use the @Mod instead.

[OvermindDL1]

Still good to parse the file *BEFORE* loading classes.  Maybe not such an issue in 1.3 anymore, but that was the original reason I could guess.

[LexManos]

One of the main reasons for having a external mcmod.info is for launchers to have access to that info without having to parse the classfile itself.

[Kinniken]

A better solution might be an option to have the mcmod.info file be automatically generated based from the tag data, maybe when the code is re-obfuscated.

[leftler]

A better solution might be an option to have the mcmod.info file be automatically generated based from the tag data, maybe when the code is re-obfuscated.

 

I really like this idea, it gives the best of both worlds. Information near the class in the code + parsability without loading the class.