From: | streu |
---|---|
Thread: | TRN BaseBuildShip with zero values |
Forum: | Planets |
In reply to: | Re: TRN BaseBuildShip with zero values |
Date: | Sat, 2020-07-11 13:07 GMT |
Hmm, ok. I wouldn't expect a "cancel" order on turn 19 with only ~250 ships built. Is it possible that this TRN command could be sent to mean "not building anything this turn" instead of "cancel previous build order", since with <500 ships there really shouldn't be any pre-existing build orders.
Yes, this could be, if someone just sends out a BaseBuildShip for all bases instead of just looking at changes.
I'm confirming with the user what client they use, but is there something in the TRN file itself that differentiates Winplan vs PCC (vs c2mkturn vs VPA vs EchoView vs etc)? I know there's the trailer block at the end of the TRN file which I haven't yet set up for parsing but at a quick glance it just seems to contain a bunch of checksums. I guess the registered user block is interesting, but I don't see anything with regards to client identification.
There's this field
+4 DWORD Contains random data with original MAKETURN. Some MAKETURNs put a signature here.
which can give a hint.
It seems I didn't document the values I know for this field? Anyway, un-trn / c2untrn will decode it. Works like a fourcc for videos The following programs write specific values into this field; Tim's maketurn leaves it uninitialized. So, any of the following values is an indication (but not a guarantee) to have a file written by that program:
- 0x00000000 = VPMaketurn
- 0x21434350 = "PCC!" = PCC
- 0x2E522E53 = "S.R." = Portable Maketurn
- 0x32434350 = "PCC2" = PCC2
- 0x474E3243 = "c2ng" = PCC2ng
- 0x49494343 = "CCII" = PCC2 (early versions)
- 0x6F72654B = "Kero" = k-Maketurn
- 0x6F72656B = "kero" = k-Maketurn
- same as file position = VPA
Stefan