astath wrote:Colonel32 wrote:CSDset version 1.1 was released!
*cough* DOS version! *cough*

Coming right up, but first this message to the CSDSet team:
PLEASE!! If you're going to release something, release
both DOS and Win versions, unless there's an exceedingly good reason[0] not to.
Besides avoiding complaints like astath's, you avoid lists of bugs like this[1][2]:
Sprite 0 is incorrect
The action 1s at sprites 50 and 69 declare sprites that are never used.
CargoID 2 is not used between its definitions at sprites 769 and 838
CargoID 3 is not used between its definitions at sprites:
180 and 358
765 and 839
899 and 957
957 and 1193
1348 and 1422
Cargo ID 3 is not used following its final definition at sprite 2359.
Sprites 765 and 770 are both 4 bytes longer than necessary.
My local version has these bugs fixed, and I am tempted to release it, but I won't unless it is requested by The Powers That Be.
I would have posted this in the CSDSet dev thread, but I could not find it. The closest I could come was the CSDCargoSet dev thread. (On request, I'll move it there.)
[0] e.g. an appropriate DOS version of TTDPatch has not yet been released.
[1] If your coder speaks English, he could also avoid this list by running NFORenum, as this list is just a massaged version of NFORenum's output. The next version will have all messages in the same file, and in proper printf format, for easy translation.
[2] If I release a GRF file, I *will* run NFORenum on it first.