Trainer Recommendations
 

The following is a list on how to make your trainer as good as it can be:

1. Make it organized! - We dont like haphazardly placed buttons on trainers!
2. Use a programming language that does not require other software. E.g. Visual Basic 6 (NOT .net) or C++
3. Make the game screen big! (If applicable)
4. Be stylish! Be creative! We don't want boring trainers!
5. SEARCH THE FORUM before making a trainer to see if anyone else has made a trainer for your game. If it has, try to find other hacks. If it doesn't, make a trainer with whatever you want.
6. Use ZIP instead of RAR because not all people can open rars!
7. Be sure you include credits so people know you made it!
8. Include as many features as possible.

I wish you luck on your next trainer!:D Goodbye!

Oh lordy!

1. Sure thats a good point.

2. ASM also

3. The what now? Whats that got to do with trainers?

4. You get what you get, excuse me if I dont make my trainer dibalicious.

5. Just because there is a trainer already, does not mean people should not do one, for one its good experience and secondly its another option incase one trainer fails for people.

6. RAR is standard and has better compression. But its upto the author if they wish to use ZIP's or RAR's.

7. Well that is of course common sense :)

8. Thats the goal for most trainer makers, but some options can take a while or possibly not able to be done.

1. should always be in mind
   
   Quote:

   Use a programming language that does not require other software. E.g. Visual Basic 6 (NOT .net) or C++

   visual basic should be taken outside and given a huge kicking.. it can still require dependancy libraries / dlls if incorrectly configured, same with c++
   
   Quote:

   Make the game screen big! (If applicable)

   big != good..
   
   Quote:

   Be stylish! Be creative! We don't want boring trainers! SEARCH THE FORUM before making a trainer to see if anyone else has made a trainer for your game. If it has, try to find other hacks. If it doesn't, make a trainer with whatever you want. Use ZIP instead of RAR because not all people can open rars! Be sure you include credits so people know you made it! Include as many features as possible.

'we'.. you're the trainer police now?

Ok, so i should remove all my trainers from gamecopyworld because they sucks too much? :,(

nah, just dont try to educate people in the manner you're attempting to do
and maybe learn a better programming language

TippeX you do realise Pikachu is not the OP :P

Brenhein: you forgot to tell us what debugger to use... in case that i might use the wrong one :eek: .

Just joking by the way :p

In my book, a good trainer is a working one, that's it. i dont care if it's done in c++, vb or even gwbasic.

I think the hardest part in making trainer is to debug the sh#@ out. So the esthetic is secondary.

Ok, basic sucks (except maybe powerbasic) but C++, come-on dude!. Not all C++ compiler does generate huge files and plethora's of dlls like microsoft visu...caught! caught!!

I'm hurt now! :'(

well in that bit i didn't mean (though i can see it could be implied) that visual c should be given a kicking too (visual basic definately).. i was sort of adding it into the category of dependancys and (getting too common these days) the need for the visual c runtimes (winsxs - which leads to clutter and confusion) :)

I don't really care how pretty a trainer looks as long as it's functional. It can be a dull grey window with a list of buttons (or hotkeys, w/e) and that's it. I'd be completely satisfied.

I guess the only time I might care is if someone decided to make it with a pure black background and bright neon lettering that blinds me every time I open it. Even then, I wouldn't cease to use a good and functional trainer based on that.

It is so damn easy to create something that looks and works nicely: just some sense for aesthetics is needed.