Has anyone noticed recently that trainers withing the aurora software can no longer "lock" in an editor value? I've noticed this across several games. Some will accept the value. But others, like Humankind, don't. At least not consistently.
I'm assuming this is a bug in Aurora? Because it appears this is universal to all editor sides of all trainers.
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
Important Board Topics
Trending Topics