Posted August 21, 201213 yr 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?
August 21, 201213 yr 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
August 22, 201213 yr The mcmod.info being a separate file is for easy parsing *before* the class files start loading.
August 22, 201213 yr Perhaps both will be compatible? And if both are present, it will use the @Mod instead.
August 22, 201213 yr 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.
August 22, 201213 yr 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. I do Forge for free, however the servers to run it arn't free, so anything is appreciated. Consider supporting the team on Patreon
August 22, 201213 yr 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. http://www.millenaire.org/img/dynamicsig.png[/img]
August 23, 201213 yr Author 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.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.