Completely agree.
The only reason the relative had it at all was because of those old fears. As soon as I learned that they had it bundled with the computer (hate that. Malware’s gotta get in somewhere though I guess), I knew why it was being slow.
I hold this up as an example because even their own troubleshooting website and a program dedicated to the purpose above and beyond the usual uninstaller couldn’t do it though. Avast doesn’t even know its own malware.
Also this nonsense got me the chance to put mint on their computer, but the “switch to Linux” argument isn’t constructive in this particular spot. They didn’t end up sticking to it because a required-for-school piece of software for tests just doesn’t do Linux at all. Couldn’t get it to run in wine or even a virtual machine either, and they’re not great at the whole computer thing so I didn’t wanna be tech support for dual booting.
Depending on the specific game itself, we can boil down the multiple-stat problem in a few ways. If the goal is to get all the stats as high as possible evenly, then we can assign each stat a multiplier based on how low it is. Fixing lower stats becomes worth more than buffing higher stats. That multiplier would depend on the game, on how much it punishes the low stat. The multiplier itself might end up being a whole new problem to solve, but for now I’ll just say its not my problem and call it X.
Whatever X is though, every stat can then be reduced to a single value using it. Super-low fortitude should be buffed over already-high mana according to X, so all of the numerical values in the game become directly comparable at any stage in this problem. Then I expect it will be equivalent to the knapsack problem. Each item in the game will boost several stats in certain ways, and all of those boosts can be combined using X to become our item value in the knapsack problem.
So I consider it to be the knapsack problem + figuring out X (which might be NP-complete on its own, depending on the game).