Reading process memory detectable

If it's external, only reading memory and your the only one using it the chance of getting banned is close to none.
For extra security, you could try to make your hack run in ring0(Google what it is) or make it run as system/local system.

every hack you use will always put you at risk of being banned

Running in ring0 does next to nothing just look at the 'common' paid cheats.

Make a cloaked kernel mode driver with the cheat built in and it will take vac double the usual time or more.
I looked up the system account, it does nothing. Running the cheat did nothing, so ignore that..

Double the time, doesn't make it 'undetectable'. It's a waste of time.

Not if it's a hack that few people uses.

If it's only a few people using Valve uses signature detection and if it's not WPM it'll be UD.

Btw, as you taught me, internal is just as detectable as external. I forgot to mention that to the OP.

External is no safer than internal exactly. Internal obvious you can do more with and in my opinion is the way to go. However who in their right mind is gonna release their own UD hook?

Anyone who loves to code, as they can just code a new one.
A hook is not really needed, depending on what you are going to do.

My attitude toward to it is: why waste something? Like seriously.

Anyways can't be fucked arguing, talk to me on skype and gimme your copy/paster knowledge.

~Bayley_

The logic is real. Reading about something and knowing is copy/paste everybody!
The information were meant for the op, not you.

For the OP, not bayley:
If you write your own internal or external hack and avoid writing to memory and you should be fine. Don't use too much public code snippets, as it can trigger vac signature bans.
@Color, this thread is going nowhere and is solved now.