unless you use a hex editor to edit the datefile and suddenly the character info is all there alongside the hex codes :)
perhaps you could do something with terrabits data packer at runtime so that the program can write its own timestamp back into the pak file rendering it incaccessible to users? possibly encrypt it as well.. a simple crc32 checksum of the install date would probably suffice especially if you mess with the generator this would reduce the date/time string to 4 bytes :) bear in mind tho that if you want to check against current date to stop people setting the clock back then you need a 2 way encryption
perhaps you could do something with terrabits data packer at runtime so that the program can write its own timestamp back into the pak file rendering it incaccessible to users? possibly encrypt it as well.. a simple crc32 checksum of the install date would probably suffice especially if you mess with the generator this would reduce the date/time string to 4 bytes :) bear in mind tho that if you want to check against current date to stop people setting the clock back then you need a 2 way encryption