There are few ways I can think of:
1. Make your Client root kit.
2. Run your client under different Windows Account and removes other windows account access to read your application. (Permission error something like that.)
3. Make a simple C#/VB.NET application that reads "Window Titles" and loop it. Blocks / closes the Matching window titles when found or close your Client when one of those are found.
4. Sometime ago I laughed when I saw some server renamed their HTLauncher.exe into "MyClient.dll". Thinking that be safe. Well, yea, it might be because players directly look at *.exe and not Dlls. Then again, this is NOT the way you wanted. This is just a very poorly thought out prevention.
But since you already told us that you're noob, I assume you dont have any Idea where to start or what to do with what I said.
Also, Silkroad Online Private servers NOW moves to Packet-protection methods. Which is 100% Server sided.
Look for Projecthax SRO if I remember correctly, ask them if they support other games aside from Silkroad.
Edit:
I made a very basic one before. What it does it what I said in #3.
I have a list of blacklisted titles & black listed *.exe somewhere hosted remotely.
Then, my application downloads the list but never saves it in a file, it just directly store all the black list words in a List box.
Then the application will Loop through the list box and search all *.exe & all black listed titles.
Then Close the found black listed window or *.exe.
Snippet:
Code:
If rP.ProcessName.Contains(blacklistedEXE) Then
rP.CloseMainWindow()
rP.Kill()
MsgBox("Detected: " & rP.ProcessName & ".exe")
End If
This gets the job done. But
KNOW THIS.
THIS IS NOT A SOLUTION.
THEY CAN JUST RENAME THE EXE AND BYPASS IT. lmao
The fun part is that I can also put a memory reader to my basic anti cheat that reads the players Username.
So, when he tries to cheat, I can know WHO because the Anti-cheat logs his username and send it to me through FTP or Mail or even Push bullet.
Example is:
Code:
Player: Master_Unknown
Application: cheatengine-i386.exe
Date: 8:18 PM 3/5/2017