Christian fe73f11443 Versions now have two flavours: the @Mod(version) which is the "programmatic version" and ... is used for all version relationship calculation. The "display version" as sourced from mcmod.info is used for display purposes only and can be literally anything. Note: they fall back to one another when they're missing, and to "1.0" if both are absent. Also, changed @Instance. Now, you can inject *other* mods using @Instance as long as you depend on them as a "before" or "dependency" relationship. Classes containing @Instance will only be loaded if the Mod the @Instance refers is present. So you don't have to worry about runtime class resolution.		2012-08-26 10:45:00 -04:00
..
.settings	Add a "checkpatches" target and check if your patches are up to date before running a repatch operation	2012-07-06 09:19:58 -04:00
src/net/minecraft/src	Versions now have two flavours: the @Mod(version) which is the "programmatic version" and	2012-08-26 10:45:00 -04:00
.classpath	Add a "checkpatches" target and check if your patches are up to date before running a repatch operation	2012-07-06 09:19:58 -04:00
.project	Check in some eclipse crapola.	2012-05-03 14:04:16 -04:00