Anybody have any idea of the structure of the data for the tasks files in hex? it seems the pwtools sTaskEdit reads in the version from bytes 4-8 and then the number of entries from 9-12 and begins looping over that count as int32 values (4 bytes) but on the FW tasks the next 4 bytes = 29
The 4 bytes after that appear to be an Epoch time stamp similar to the elements.data? just wondering if anyone has tried to break it down and has any info they can share?
The 4 bytes after that appear to be an Epoch time stamp similar to the elements.data? just wondering if anyone has tried to break it down and has any info they can share?
Last edited: