What worries me more than financial loss is the loss of the product. In all the major online games hacking changes the entire dynamic of the game and unfortunately the footprint of the cheaters impacts on the game for the genuine players.
Last night whilst lying in bed I came up with a novel way of storing data where I would have bit level acess in Blitz and there wouldn't be static offset of a globalised variable or function return where it could be read and I could hold the data in memory in an encrypted format that polymorphs whenever I decide to change the seed internally.
It might be a bit slow but for my project that should not matter, my plan is to RGBA values of image data and because Blitz uses a pointer system for image locations I can keep moving it about in memory - and I can move the pointer variable about by using non global variables to hold the image location in memory and pass it about. I'll move the image too by reserving randomly sized blank areas of memory before making the image to hold the data with, and i'll move it about and perhaps even on ocassion store it in texture memory.
I'm not completely sure it will work yet and that it isn't fool proof - but I reckon if nothing else there's no way on Earth that I would attempt to hack that and so it'll hopefuly despoil even the most determined cheater.
Last night whilst lying in bed I came up with a novel way of storing data where I would have bit level acess in Blitz and there wouldn't be static offset of a globalised variable or function return where it could be read and I could hold the data in memory in an encrypted format that polymorphs whenever I decide to change the seed internally.
It might be a bit slow but for my project that should not matter, my plan is to RGBA values of image data and because Blitz uses a pointer system for image locations I can keep moving it about in memory - and I can move the pointer variable about by using non global variables to hold the image location in memory and pass it about. I'll move the image too by reserving randomly sized blank areas of memory before making the image to hold the data with, and i'll move it about and perhaps even on ocassion store it in texture memory.
I'm not completely sure it will work yet and that it isn't fool proof - but I reckon if nothing else there's no way on Earth that I would attempt to hack that and so it'll hopefuly despoil even the most determined cheater.