Please understand I am not trying to be sarcastic here, this is a legit inquiry. Tone is difficult to translate into text.
If I'm reading that right, the "trainer maker", IE Caliber, intended the lock feature (which was working perfectly, awesomely) to not be available? We need to request new features to get back a feature that was already in the game?
Assuming they are not breaking/causing crashes, why would we not want these lock features in game?
I'm sincerely confused.
It is up to each trainer maker to decide for each trainer whether or not they want to allow the locking of values. There was a bug in Aurora that ignored the trainer maker's intention and so it was fixed. The reason is that in some games locking the values can cause crashes or other issues, especially depending on what the user locks the value to. We had an array of different trainers where people were reporting random crashes that we could not replicate and spent a ton of time trying. It was then that one of the trainer makers determined that users were locking certain values that were not supposed to be locked and that is what was causing all these crashes.
Now, if you believe that the locking of values in THIS particular trainer never causes or caused any harm then you can petition for the trainer maker to allow the locking of values and submitting a new trainer.
I hope that clears it up.