Investigate disappearance of the mission briefing modification

[Henrik Heimbuerger]

The mission briefing modification always disappears after a while (and goes back to the original version).

This needs to be investigated. It almost seems that, although missionbrief.mdl is not on ASGS lockdown, it is nevertheless overwritten by autoupdates.

[SVN]

New commit by cortex (revision [66]):
[Potential fix for ticket #12] Updated CortUI's missionbrief.mdl to contain the BSG mission strings.

That might fix the issue with CortUI's missionbrief.mdl being overwritten by AU.

[Henrik Heimbuerger]

[66] doesn't fix it. Seems like, while modifying the missionbrief.mdl does not trigger and autoupdate, it is still detected as not having the right signature during the next autoupdate, and Allegiance will overwrite it.

Unfortunate, but I don't see what I could do about it. I don't even see how a code change could look like to 'fix' this behaviour -- it does make sense that autoupdate detects files from its list which have been modified to overwrite them.

[Henrik Heimbuerger]

After a discussion in IRC, let me add some clarification:

The Allegiance client maintains a list of artwork files (%ALLEGDIR%/filelist.txt). It seems like the lobby server has the same list.

As soon as either the local file changes/gets deleted or the remote file changes, the client regenerates all checksums and downloads those which do not match the checksums of the server.

Therefore, the modified missionbrief.mdl works until the next time either the local filelist.txt or the one on the server changes. When that happens, the client shows the autoupdate dialog before entering the lobby and downloads all files which have changed. That obviously includes missionbrief.mdl, because my modification's checksum doesn't match the one of the lobby server.

Note that any change of the local/remote filelist.txt triggers this. Example: a new version of Community Core is released and put on the lobby server. The lobby server updates its filelist.txt with the new checksum of the .igc file. The next time a client connects, it detects that the local and remote lists are no longer in sync and now updates both it's local .igc file and the missionbrief.mdl.