Feedback, Complaints or Problems

Long time member, I love this site. I've been off PC Gaming for about two years and I noticed a trend on this site. I was wondering if we can have requests to avoid this trend.

You're Trainers used to be amazing you press 1,2,3,4,5,6,7,8 and something awesome happens that was preprogramed... Those were the days....

Now I am noticing a lot of RPG or other trainers don't use this simple method anymore and use that thing CoSMOS. I am not good at hex editting I never have been thats why I don't use those other editors. I don't want to feel like I need to take a programming class to use a trainer.

Perhaps putting up requests to do a trainer the old fashioned way might be a benefit meaning the request would be a trainer but not made using CoSMOS or a hex editor type of deal?

Thank you

Sorry, but we won't be making two different versions of every trainer for every game. People wanted more customization over the amounts the trainer was giving them so they complained they trainer gave them too much of this or too little of that. We fixed it by adding in the Editor functions. It's not difficult to use. Many trainers still have one hotkey functions plus editor options. It's just the evolution of the trainer.

I guess the people have spoken. Thanks man

I'll let the trainer makers chime in here as well. Perhaps there is some sort of middle ground which wouldn't require additional effort for the trainer makers on every trainer.

Most data in games are stored in something called

STRUCTS

Or at least thats sort of what we name them. Structs generally are a collection of "things" that are specific to an object or a type of object. Like "player" or "units" or "City" or "Resources".

The struct is a section of memory dedicated to that object. So likely a bunch of stuff so let's call them "traits" of the object that are pertinent to that object is in that section of memory. Like health, stamina, speed, strength, etc. Or gold, wood, stone. Usually each "trait" is located at a static position from the beginning of the memory of the struct. So:

Struct for Object "Player" contains "Health" and it's 100 bytes from the beginning of the struct.

We can quickly make an editor containing a LOT of "traits" maybe like 20 or more! for a struct using our template. A lot of times people can quickly click a unit in the game for instance, and all that unit's "traits" that we made and editor option for pop into the editor. You can quickly edit the entire unit's "traits" and see what hey are LIVE. For an RPG game, you can see a LOT of information and edit it for a character, or edit values of resources for example to be exactly what you want.

Coding 20 options that require a keypress is a LOT of work, doesn't allow as much flexibility to see and edit, and when we have updates of the game and they update A LOT, we have a LOT MORE WORK updating the trainer.

So this makes sense in many aspects. Now if you are playing on a tiny notebook, and want to play serious games in fullscreen window mode and have to alt-tab, I can see where this may not be the same for you. However, we are seeing that the trend for gaming at least is 4K, larger screens, and more workspace and larger monitors for PC gaming. If you are going to play a game that has a lot of RPG or many elements that need editing, playing the game windowed with the trainer beside it works best.

As a side note, some games the values for many things run through the same functions. In those cases, we sometimes make an editor option rather than an "old school" on off option so people can see the value they are editing is matching what they are intending to edit in the game. It's rare, but sometimes this is the only way to avoid unintended consequences.

I hope this helps you understand, at least.

best,
Cal

Ask different people and you get different answers. Some people just like hotkeys. Other people like having hotkeys + the option to customize the value the hotkeys adds or subtracts. And others want to edit the value direct, they dislike hotkeys.

Our latest trainer template is very flexible and trying to cover everyone needs. We have male and female voices (tell me one other trainer template which has this). We have an option to mute ALL hotkeys, we have option to mute SPECIFIC hotkeys. We also have the option to HIDE (and mute) specific trainer options. We have customizable values which are saved and restored. We have customizable hotkeys which are saved and restored. We have editor items which can be a number or even a combobox (list) to choose items by name. We have a dark and white design you can choose from.

But some things still depend on the trainer makers decision. For example when I as a trainer maker make a character editor which lets you change the hair, age, width or height etc. I don't create hotkeys for ALL editor options. This is because if I would do, then I'm taking away 20 keys from your keyboard just for options which you are basically only press once at all.

So I for myself create hotkeys where I believe it makes sense and then let people use the option request system if they want to request the possibility to change an editor item by a hotkey which currently has none.

There are so many people using our trainer and everyone use it differently. We always give our best but often it's not enough. It's great to hear feedback like yours though as it allows us to fine tune our process and letting us know where we can improve stuff.

Thanks for that, guys. I don't fully understand all of it but I do enjoy reading it. I've always appreciated how fortunate we are to be able to enjoy the combined wealth of knowledge from both of our programmers.




[Edited by Jaks, 7/13/2020 10:44:32 PM]

Thats some good explanation right there