Ch now rip Sicheats Trainers?

[Desu[Shield]]

Do you have any problem to show your code to joe?.

Any sensible developer would say no to this question. Posting the algorithms is high sensitive information. You have no definitive proof that Cheat Happens is guilty other than some "time stamp". If anything, Cheat Happens can probably use the exact same argument against you for several trainer titles (and I seriously doubt you are willing to comply in return). From what I've seen from previous topics, Joe is extremely biased against Cheat Happens and favors your work a lot better (and there is no guarantee that he would not slip information to you for your own use).

[cocodrilo]

more word, but.....

My trainer is public released for free, anyone can download and inspect.

can you make a public version to see if there is something similar in your trainer?. sc trainer is public to anyone. feel free to download and decompile it. isn't crypted or compressed.

More simply:

1 : ¿what offset or pattern uses your trainer?

2: ¿any particular reason for this address? please explain.

If anything, Cheat Happens can probably use the exact same argument against you for several trainer titles (and I seriously doubt you are willing to comply in return). From what I've seen from previous topics, Joe is extremely biased against Cheat Happens and favors your work a lot better (and there is no guarantee that he would not slip information to you for your own use).

this trainer has minimum 3 ways to do the same effect in different offsets. would be a casuality to be the same address in the two trainers... ¿right?.

As for what (trainers) I do I can answer without any kind of problems any questions.

Any sensible developer would say no to this question. Posting the algorithms is high sensitive information

Not all code is required, only a function of this trainer and the offset or pattern. for example my pattern:

BYTE patron[] = {0x8B,0x43,0x10,0x89,0x47,0x10,0xEB,0x63,0x8B,0x43,0x10,0x89,0x47,0x10,0x8B,0x43,0x14,0x89,0x47,0x14,0xEB,0x55,0x0F,0x28,0x43,0x10};

is this "sensitive information"?