REQ: Stolen trainers to be removed from GCW

[Caliber]

Originally Posted by Jacardis

i have been to your site and was disapointed i been looking for a trainer that coincided with a game im very fond of stormrise. but when i saw you had one with limted option and had to purchase a full membership just to get it . that turned me off from your site, sorry.

we didn't make a promo for stormrise because we could only create TWO options for this game. those 'limited' options took me the best of 8 hours to create.

FIRST- this game is DX-10 ONLY, which limits the OS that a trainer maker has to have to be able to just RUN the game.

SECOND - the fact that it is VISTA also affects the TOOLS we can use and this game crashes when breakpointed with a debugger (even with PLUGS)

THIRD - this game uses LUA scripting to perform all of it's decision making and variable updating. What does this mean? This means that ALL variables and data are routed through TWO code locations ONLY. THOUSANDS of variables run through these code sections every couple milliseconds. Divining out the HEALTH or POWER or whatever of the PLAYER ONLY vs. the thousands of other variables running through that code section is a nightmare. If you've never made a trainer then you HAVE NO IDEA WHAT I AM TALKING ABOUT.

why am i going into all of this? basically you won't see any other trainers other than OURS for this game, because nobody is going to screw with this game for 8 hours, dealing with crashes and dead ends over and over trying to make options for a VISTA only game. i don't often try to boost myself like this, but this trainer is a F'ing accomplishment. we have way too much other work for me to try and put 8 to 12 more hours into this mildly popular game just so i can *maybe* find a way to do more options.

Those two options are quite powerful, by the way, and took alot of creative thinking, skill, and home-made tools I programmed myself to accomplish.

So i take exception to you putting down our 'limited' trainer and I will go out on a limb and say that I doubt we see any other trainers for that game (unless someone looks at my code and tries to copy it). There's good reasons why some trainers have limited options. That doesn't mean they didn't take skill and alot of work to create them-

good luck finding another trainer for that game. By the way, a subscription to our site enables you to download ALL the members only trainers, but you know that already...

best,
Cal

[apache-yesitisme]

Originally Posted by Caliber

I will go out on a limb and say that I doubt we see any other trainers for that game (unless someone looks at my code and tries to copy it).
best,
Cal

OMFG! what are you like lol , your way too paranoid
anyway was not the end means of this thread to seek a resolve for cheathappens problem of people allegedly ripping certain trainers? how about requiring members legit home address and isp base? dna fingerprints and first born child as collateral or not releasing ANY full trainers to the public domain then i guess u have some kind of software legal protection??? or maybe more legal clout but then again proving somebody is stealing code would be difficult i guess
besides from what i have read on here(this thread) caliber, ch is doing better then ever? so is this 'stealing' really damaging your site? or is this and other similar thread giving cheathappens.com unprecedented free publicity
Now chris iam not deflaming cheathappens btw i have actually been in the same dilemma and i couldnt think of a solution

[Joe Forster/STA]

Hmmm, fingerprints are well possible in a software...

If you have a strong secondary PC and lots of space on your web server, you could create user-specific versions of all downloads. In a very simplified version, you hide a redundant "MOV EAX, user_id" in a well-defined place of the code - I mean, 1) assemble "MOV EAX, 0" into the common version, 2) patch into it the user_id for each user-specific version and 3) compress/encrypt only afterwards. If your web server is strong and you don't have that many downloads, it could be done on-the-fly by the web server instead.

Then, if you see your code being ripped off and that code contains the hidden fingerprint, you'll be able to find out which user on your site stole it (or leaked it to the thief). This assumes, of course, that A) the thief is not smart enough to find the fingerprint and/or B) the ripped off code is sophisticated enough for such a fingerprint to stay well hidden in it (it does not become obvious that that particular instruction is not needed for the functionality) and C) the thief does not have access to two (or more) user-specific versions that - after decompression and decrypting - only differ in the fingerprint.

Wanna attend a polymorphic virus coding course?

[...] Or another simple example, taken from SecuROM. Whenever using constants, use "MOV EAX, (value XOR user_id XOR random_value); XOR EAX, (user_id XOR random_value)" instead of a plain "MOV EAX, value". Because of the randomness of the actual values, the user_id won't be seen anywhere "naked" but you, the author knowing the random_value for at least one such tricky assignment, can easily find out. Yes, this can be unwinded, but, when sophisticated enough, only with lots of struggles and "visual debugging" (watch the code in a disassembler and find out in your head what it does) becomes extremely annoying, too.