What I was kicking around would have had three factors - time, gamename, and a LARGE (at least half a meg) keyfile. The starting time would have been used to pick which part of the keyfile was used that session (intending on a 64k block), and the gamename would act as the seed for the encryption algorithm. If the algorithm is changed from a formula to a giant "look up" table then it could also be loaded from a seperate file, which I think takes everything really interesting out of the source code so we could get around the damn immovable object. It could be distributed with two "junk" files so record/playback would function properly even if you had to get a keyfile that the destination page (MARP/Mark/Sniper/T2/...?) would accept to register a score.(posted 9537 days ago)I know the sizes are probably overkill, and I don't have any special ideas how to fight a debugger/disassembler, but maybe it's a start?
Aqua