2PC AI Fine-Tuning

Why do every 2 PC AI providers keep fine-tuning their aim settings until they get worse?

I get that you guys are trying to be more "legit", but wouldn't turning down the aim speeds and such be sufficient that you won't need to keep touching and adding new functions, then making EVERY CONFIG useless and make everyone re-config again?

Seen this with multiple providers that I have tried, and it is starting to get me pissed.

Are there any providers that will stop touching their product and only do minor updates? Don't start with all the humanization and shit which causes everyone to re-configure stuff every single time.

Quote:

Originally Posted by xnordin2 Why do every 2 PC AI providers keep fine-tuning their aim settings until they get worse? I get that you guys are trying to be more "legit", but wouldn't turning down the aim speeds and such be sufficient that you won't need to keep touching and adding new functions, then making EVERY CONFIG useless and make everyone re-config again? Seen this with multiple providers that I have tried, and it is starting to get me pissed. Are there any providers that will stop touching their product and only do minor updates? Don't start with all the humanization and shit which causes everyone to re-configure stuff every single time.

Unfortunately, that’s just where things are at right now. We have to stay ahead of detection and behavior analysis, and that means sometimes changing underlying logic rather than just turning a few speed values down. I know it’s frustrating, because it can invalidate existing configs, but leaving things untouched for too long is usually what gets products flagged or burned.

We try to minimize disruption as much as possible, but when the environment changes, the software has to change with it. In most cases, those adjustments are the difference between something continuing to work long term versus being dead in a few weeks. It’s not about adding features for the sake of it, it’s about survival.

Quote:

Originally Posted by .MOON. Unfortunately, that’s just where things are at right now. We have to stay ahead of detection and behavior analysis, and that means sometimes changing underlying logic rather than just turning a few speed values down. I know it’s frustrating, because it can invalidate existing configs, but leaving things untouched for too long is usually what gets products flagged or burned. We try to minimize disruption as much as possible, but when the environment changes, the software has to change with it. In most cases, those adjustments are the difference between something continuing to work long term versus being dead in a few weeks. It’s not about adding features for the sake of it, it’s about survival.

Maybe the best post ever. Kudos!