darwinsGate wrote:RD says
It's a 4-byte integer and you can parse the seconds like this:
seconds = byte1 + byte2*256 + byte3*256*256 + byte4*256*256*256
seconds = byte1 + byte2*256 + byte3*65536 + byte4*16777216
Yeah, I don't even know what to say to that...
That's a DWORD in C.
0xE2 0xA6 0x10 0x00 is what I got back from one server.
So following the logic listed above, the seconds left is: 1091298 (226 + (166*256) + (16*65536)) Well... The server has a timelimit of 20 minutes, so... 1091298 / 60 = 18188.3 minutes... Something's not quite right there.
On a 20 minute timelimit server, the highest value this could reach in seconds would be 1200, which equates to:
0xB0 0x04 0x00 0x00
If I had to guess, it's actually in milliseconds: 1091298 / 1000 = seconds, or: 1091.298 seconds (18.1883 minutes), which would appear to be valid.
So I'll just ignore what that guy has to say...
Would you prefer to see it in seconds, or minutes?