I think it is time an auto update or update notification system was added to spring, so that a mod could have its version checked by the lobby ro spring when ti goes ingame, or the spring setup itself being patched.
I think it'd be better than simply dealing with a 20MB patch file that may include stuff I dont need, and it'd be quicker and easier to distribute.
Auto-Update system
Moderator: Moderators
I heartily agree. Between versions of AA, often only a dozen or so files have been changed; 100 kilobytes at most. A quick solution would be for a new mod definition file tag to be used:
Anything in this archive would have preferential treatment over anything in the "patched" archive. Concurrent patches would also list the previous patches in the "patchedfiles".
If we can convince the guy who controls TASClient updates to have "more mods" link to the wiki, mod makers could easily post their most recent update there, as well as the most recent "core" file.
Code: Select all
patchesfiles=1;
patchedfile1=AASpring10;If we can convince the guy who controls TASClient updates to have "more mods" link to the wiki, mod makers could easily post their most recent update there, as well as the most recent "core" file.