Feedback, Complaints or Problems

I've been using trainers via Cheat Happens for years. I've convinced half a dozen friends to sign up and support... and even before Aurora I have never had issues, never did until recently that is. I can't be the only who has an issue with the "update" that according to other posts, was believed to be a bug (that's how great of an "update" it was). This latest "fix" doesn't allow me to lock-in values, and I'm wondering why, as far as I can remember I have always been able to lock-in values, so why now can I no longer lock-in?

I understand it's up to author as stated on another post, but it was up to CheatHappens not that long ago, everything was working lovely, smooth as butter.
Not being able to lock-in is not only making my experience extremely buggy, but it's wasting more time than it's worth. I could be playing the game instead of tinkering with everything trying to get it to work. This is happening with multiple trainers most notably Baldur's Gate 3 and CyberPunk2077 among the many.

Again, I realize the author can incorporate such a feature, but the problem is the whole thing (new update) is not playing nice with Aurora currently, like it used to be.
The values aren't staying put and reset when I click away, but also do nothing when I just type the numbers (with no "ENTER" confirmation... or in this case, a "lock".

In other words, I will input a number and nothing happens, they stay there until I click away which they then disappear -- but before clicking away with the values typed, it also does nothing while the numbers are in the box, since there is no enter/lock option. Almost a whole hour later it finally randomly accepted my value, so I copy/paste the process and nothing again.

I really like CheatHappens as a whole, and even Aurora client which for some reason a lot of people complain about. Literally never had any issues until this recent so-called "fix/update".
For goodness-sake guys, I can still see the lock gfx icon, it does nothing now! Please revert back and let's not turn into Riot Games where we make a product worse with over-updating instead of just leaving perfection be, left alone and untouched.

Regardless of this one and critical issue for me. I want to thank you guys for making trainers easy and fun for new users and gamers in general. Thank you for your contribution to the gaming community, and fingers-crossed this issue is resolved soon, please allow "force value-locking" in Aurora to fix issues it has created being absent, like the currently broken trainers, I can't say it's the case for all games, but I'm playing some of the biggest games of the year and all that have the "EDITOR" section where you used to lock-in values... no longer function properly.

I've uninstalled, reinstalled, tried portable and installer versions, also tried admin and a bunch of other troubleshooting before looking at the forums and noticing others complaining about the same issues. Hope the issue is resolved soon as again, trainers are only half working right now. Any trainer with an "Editor" is non-functional for me.

We heard you (and all the others who don't like the change). So we changed it to allow freezing but showing a warning when it's not recommended by trainer author.

As for changing values all you have to do is to press TAB key after you entered your value. I've just tested it and it works fine. If values don't stick then its probably game related. Either the value gets overwritten by game or trainer or you just run into a case of why freezing was not recommended.

I am just repeating what 0x90 said. We have heard your complaints and there was no real easy "fix" to "fixing" an issue that should not have been allowed in the first place. So, we have produced a STOP-GAP version of Aurora which basically rolls back the "fix" that everyone is upset about, but also added a WARNING which we hope that you take seriously. If you start locking values that has a warning about locking values and your game crashes, or your save is corrupted, then this will be on you. It's also likely to get a trainer retired if we start getting a lot of complaints about crashes when locking values that you were warned against locking.

Again, this is a stop-gap while our trainer programmers decide the best course of action moving forward.

New Aurora: Link

[Edited by moderator PWizard, 11/13/2023 3:58:59 PM]

First let me say that I understand your frustration. We never want members to have something they like or enjoyed be "taken away" from them if at all possible.

Second, let me explain what is going on here in better terms.

The game has FUNCTIONS that are called. Look at it like a small section of code that is doing something. Maybe it's a function that we will call "READ HEALTH". Or "IS THIS PLAYER" and the function returns a value that the game will use or display. Some functions are simple and are great.. like "READ PLAYER HEALTH". They are never "labelled" like this, but in many instances we can infer that they are, in fact, just for the player.

However, more often, there are functions that are used by the game to do many things. Some of them are functions like "READ VALUE". This function, as you can imagine, may read all sorts of values. In some cases, it may be "READ HEALTH" but it could be the health of 100 things, so it sort of depends on what part of the program is calling the function.

The point of me going into all of this is that sometimes, maybe a good deal of the time, we have to intercept code to read things, and capture what is called the BASE ADDRESS, then that base address is used to display in the trainer the value of something. For instance it might be GOLD. So the BASE ADDRESS plus an OFFSET will hold the GOLD value. Maybe it's BASEADDRESS+10. However, there may be only ONE CODE AREA that is reading the value of GOLD. It might be one of those code areas that is simply "READ RESOURCE VALUE" or something like that. SO we often will give you instructions like "PRESS THE INVENTORY BUTTON, THEN THE VALUE WILL FILL IN, THEN YOU CAN EDIT IT".. You may notice if you press the player stats button, for instance, it may show a different value. OR when you are loading or saving the game, the BASE ADDRESS may not even be created yet or is some old value. This can set up problems.

So if you are using the FREEZE or LOCK feature and it's NOT INTENDED, you are telling the trainer to write to this BASE ADDRESS that might not actually BE the Base address any more or is "nothing". When you have something writing to wrong values or having a game filled with addresses that have wrong offsets or old data, it's a perfect setup for CRASHES. In fact, it's usually just a matter of time.

When I made these trainers, I intentionally had the feature to LOCK these values OFF. Due to an update of Aurora or some other reason (0x90 can explain) the LOCK feature was still able to be used. I HAD NO IDEA. And this had been going on for weeks, maybe years? So apologies that you got used to using something that wasn't intended, but this ALSO may have been the source of people complaining that the trainer "is crashing the game after some time", which is impossible for me to know or "fix" and frankly wasn't supposed to be possible TO BEGIN WITH.

So just understand that you were using a feature that isn't always possible to do, and wasn't supposed to be used, TO PROTECT YOUR GAME and KEEP YOU FROM CRASHING YOUR GAME.

Now understand how it feels to have members here threatening us, complaining to us as if we are some horrible company or did something improper. The trainer is actually working as it was always intended. And NOW we have come up with this "fix" to allow you to basically use the trainer feature that wasn't supposed to be used to begin with, which will likely or COULD cause you to CRASH YOUR GAME, which will inevitably cause MORE COMPLAINTS.

"You made the product worse". And this comes after we've updated these games 100's of times, hours of work, dozens of patches, multiple rewrites, and people are threatening us or want to abandon us over a LOCK FEATURE that wasn't supposed to be ON to begin with? WOW... I mean Baldur's Gate and Cyberpunk alone probably an estimated 400 man hours on those games, and dozens of patches over months/years and NOW you just find our trainers to be "broken" and this issue is just too much of a problem? I am taken aback, I must say.

Ok, so we've put back the broken feature so you can use it. Just understand, that this means we go back to people complaining that the "trainer crashes my game sometimes" which most likely is YOU crashing the game sometimes, with ME not being able to help you at all.

I apologize to be so frank and so... upset. As the reason for this WAS TO PREVENT GAME CRASHES and PREVENT BAD OUTCOMES of locking addresses that aren't fixed and aren't isolated. THERE WILL BE CRASHES and POSSIBLE ISSUES.

So, JUST SO WE ARE CLEAR, the warning is a REAL THING. If you locked values in Baldur's Gate 3 (for instance) and had no crashes, then probably you will get away with it.

Future games, if people override the lock, then so be it. Keep that in mind when you are complaining that the "trainer is crashing the game". I personally don't WANT or INTEND for people to be able to LOCK EVERY VALUE. But if this is ALL people appreciate about or work the last 10 years and all the patches and updates and hours, then by all means let's make sure its back before people try to go elsewhere and find out that "other trainer sources" are 3 days behind on releases, and sometimes months behind on trainer updates.

best,
Cal

We just fixed a broken feature that wasn’t intended to be like that in the first place and as a programmer let me explain you why I don’t allow it, imagine a function inside a game that is used to read resources and health and stamina and Resource Id at the same time but it’s called from different parts of the code and it’s event based meaning it is only called when needed, for example in when you open then inventory tab inside the game and mouse over an item then this function is called to retrieve it’s amount or when game updates your items then it calls this function to retrieve it’s Id or when you lose health then it’s called to fetch your health value and so on, now we make a use of this function to intercept item amount while you’re inside the inventory to create an inventory editor where you could just point your mouse on your desired item and edit it on the fly and as long as you are in the inventory this function isn’t called to fetch Resource Id or health so if you Freeze the value then close the inventory and game calls that function to retrieve resource id but receives something different than what it’s supposed to be because you locked it on a certain value then it will crash or worse case will corrupt your save game so as a programmer I have to make sure this doesn’t happens by not allowing it in the first place.

That's why I've rarely used the lock option for years and never needed to do so most of the time; I didn't even see it wasn't working (intended), and I agree that if it causes crashes/corrupt save games, it should be disabled or at least with a Warning.
But is it safe to lock the editor value when there's no need to for example Open the inventory? because then the base adress won't change right? Or is it the same

And Thanks for the update guys <3

Technically no it’s not safe to lock the value even when you’re inside the inventory because we don’t know what game does exactly when you mouse over items and if you choose to do it outside of the inventory it’s even more worse because the function is multi propose thus it’s heavily shared and you might unintentionally overwrite something critical that might result in save game corruption or crashes but this is totally game dependent and we allow it only when we are completely sure of it’s safety and reliability, anyway, the feature is now back on the track with a warning.

Generally I would advice you to backup your saves before locking out values in the editor when it’s disabled by the trainer author.