Flock [Demo STEAM] +4 Trainer

[Caliber]

for completeness sake:

my demo locations are at:

QUOTA +2828
=====


0045D3C0 0388 28280000 ADD ECX,DWORD PTR DS:[EAX+2828]

QUOTA +2828
=====


0045D3C0 0388 28280000 ADD ECX,DWORD PTR DS:[EAX+2828]


UFO SPEED +27c4 (float)
=========

00450E70 D99D C4270000 FSTP DWORD PTR SS:[EBP+27C4]


SCORE +61c
=====

0042EF6E 8B8E 1C060000 MOV ECX,DWORD PTR DS:[ESI+61C]


BONUS TIMER +928 (float)
===========


0045CCA9 D998 28090000 FSTP DWORD PTR DS:[EAX+928]

AGAIN: once you have attached ollydbg, then log where my trainer attacks the game it's PIE to take this information and create your own trainer...

for the timer you can just convert to FSTP ST

or write the value (mov [esi+0000061c],3b9ac9ff) high

or you can avoid the function altogether.... depends on HOW you want to do it so as to not be noticed...

NOW given all of this, we didn't release our DEMO trainer.... so it's hard to say Hax0r copied us or not. even if he did, how you going to prove it when there's so many ways to TAKE the info and then use it to make your own (slightly different approach) trainer with same options.

what we don't appreciate is when they put out the SAME TRAINER OPTIONS, less than 24 hours after we do with SAME NAMES, in SAME ORDER, with copies of OUR IMAGES in the SAME size (249X339 LOL) taken from the same CODE AREAS with similar or SAME SOLUTIONS.

Tippex been asking for proof of this, well we sent all this to empire quite a while back. i don't have it handy but we also sent a link to cheatengine forums where kelsat was admitting trainer ripping. we DONT HAVE TIME TO GO OVER ALL THIS AGAIN.

there's no way to definitively prove each trainer and our point is that there's enough dots and info to connect these people to our work. If they continue to have a venue here then we are done posting here .... it's that simple. I respect whatever decision EMPIRE arrives at but we ask that he does the SAME regarding our decisions.

also:

mov [esi+0000061c],3b9ac9ff
mov ecx,[esi+0000061c]

is NOT the same as:

mov ecx, 3b9ac9ff

because [esi+0000061c] is holding the float value which declines as time goes on. I don't know if this code snippet has the actual DEC of the float in it but it's better to write to the [esi+0000061c] directly what you want it to be than to rely on the ecx register to carry the new value...

best,
Cal