Quote:
Originally Posted by Paul Miller
Why would that be a bad thing? Isn't it just better?
|
Not necessarily.
If you can't bypass VAC without using a driver, then you shouldn't be making cheats, and it shows you can't really make undetected cheats at all.
Anybody can paste a driver, though it's a terrible idea.
It's like a lot of the DMA providers, there's many who can't make undetected cheats so they use public hardware as a crutch.
Quote:
Originally Posted by zebleer
I think what he was trying to say is that a customer would rather have a user-mode cheat made by a developer who knows what they are doing rather than a kernel-mode cheat made by a paster
Either that or he's saying customers should buy from a "real man" developer who doesn't go hide in kernel-mode from the anti-cheat and fights it in user-mode instead
His point is pretty weak either way. In 2023 a customer should be buying kernel-mode cheats from skilled developers (not pasters) & nothing else should be considered
Obviously when I say kernel-mode cheat I just mean a cheat that handles as much in the kernel as possible. Usually no cheat handles everything there
|
You bring up my exact point, as it's a well-known one, yet try to deflect it.
You know just as well as I that there's a ton of developers who don't even know what vac does, so they paste a driver and say it's undetected.
These same pasters from CS, after realizing they can compile a driver, flood the EAC/BE market as well.
That probably sums up 80% of your competition.
You know the market, you know what I'm talking about.
As far as the customer goes, they never know what they're buying so they don't care. It is what it is.
