General Discussions

This is simple curiosity, nothing more really. If you can spare the time, what kinda steps does it take to make a trainer? I've always wondered how involved it is, what you have to do, ect.

if Pwizard or Calibur or the other staff could spare the time. I'd appreciate it.

Simply wish to understand what you all have to go through better is all.

There are tutorials of how to make some trainers if you're interested in getting an overview of the process.

Link

I don't have the patience to make my own, but I'll look em over, I was just curious the process pwizard and them go through for their personal stuff, don't even have to really tell their secrets. I'll read the link tho.

If you think there is this super easy way, there isn't.

If you don't understand Assembly then you will only get so far before you start licking windows not knowing what to do next.

When you say you don't have the patience, I would tell you right now, then there is no point finding out or trying.

Mostly. I just wanna understand what you staff go through to set one up. Its mostly because I wanna understand YOU guys better, thats all. I never thought there was a super easy way, coding for anything is a right *****, from my understanding, and gets progressively more anal the more complex things are.

Please don't misunderstand me, I mostly am curious cause I've seen posts from Calibur and Pwizard how it takes up most of their day handling all the trainers and stuff, and I just wanted to know what they go through. Call me empathic or crazy, I just like trying to understand people better. I hope this isn't a problem.

If it is, I can just drop the subject and move on.

[Edited by NexusCron, 8/20/2014 8:55:21 AM]

There is no misunderstanding on our part. There is no "easy way" to go over the technical aspect. You have to grind out the tutorial to get a feel for it. Any higher than that would just be a 101 lesson in the software development cycle from analysis to development to QA to O&M.

[Edited by Neo7, 8/20/2014 5:37:29 PM]

Ouuuuuch. Okay, Yeah. I'll read the tutorial.

101 Lesson would make my head explode. Sorry to bother you all about this, i had simple curiosity as to what you guys go through. I like being a nice person and learning about other things.

Simple way to explain:

1. Play the game
2. Finding code spots of interests (like health function)
3. Writing a code injection
4. Put everything in a trainer template (Caliber or I have created over time)

Step 2 takes the most time. There may be game where things are pretty easy to find as they are stored of what you see, but other games using XOR encryption or have memory scanners active or other things you need to take care of as well.

Well and nowadays we have a lot of games being made by Unity engine. Which creates code on the fly, so you have to find a valid array of byte and then your trainer needs to be able to scan the whole game memory for this array of byte in a short time. Because for nearly each option you would have an array of byte and some people feel annoyed if they need to wait for trainer activation. We have also games being made on JAVA or Adobe AIR (especially the smartphone apps which have been ported to PC) but Caliber can you tell more details about these environments.

Oh and there are also scripted games, containing loop functions which hundreds or thousands of addresses running through and you need to filter properly or back trace until its isolated.

The knowledge and range of difficulty is very far on game hacking. As tutorials will stop somewhere on easy difficulty you need to try out a lot on your own and make your own experience and see how things go. Or you have someone experienced to teach you.