Thanks. I'll check out your version.
What I'd like to see is a patch that updates sprites. Why transmit an entire 60MB file to fix 1MB of bad data? Same with the Starfleet2CE.exe -- only a few bytes will change in 2.676. I've never written a binary patcher. I've always distributed complete replacements (.exe, .q3, .txt).
I haven't made any changes to offsets.txt. I could add a tab for weapon arcs...but the associated bitmaps wouldn't match any player-defined arc. At this point, CE's offsets.txt won't change unless a player requests additional customization.
It has logic what you say.
But a binary update will only work if the original files match the ones we want to update.
For example, imagine a person that bought the vanilla version just now, and one that is using the lastest v2675. Now we would require 2 diferent patches!
Same with the sprites.q3 file. There is the vannila file and the one we zipped with 2675. We would need to create 2 patches.
Now imagine if someone has been using the SFC Editor to personalize something. Now we would have EXE's with diferent checksums... how would we know?
Same applies to someone that changes any sprite on the sprites.q3 file. It would have diferent sizes, offsets and checksums.
Nowdays, with the fast internet connections that there are, i dunno if it makes sense.
The 2675 patch is
23.4 MB only! And it has the EXE, one sprites.q3 file, and all the other things (+90MB).