Quote:
Originally Posted by Roibot
However our bot does not inject code or mess with the client in any unsafe ways.
|
Sorry, I didn't mean to offend you. I wasn't trying to make your bot seem less secured or reliable in any way.
I was just trying to make a general point. obviously I am thankful and grateful for your sharing.
it was just a general point.
Quote:
Originally Posted by Roibot
What it does is what a human would do. Typing on the keyboard like I would now to type this sentence. It is safe in the form that they can't tell if it's a real human or not.
|
That's the point. that is what I was trying to tell you, anything you do in with a game client is the same.
the endresult of every action you do in your client is a packet being sent to the server letting it know about it.
so sending that packet manually/automatically, playing normally or having a macro is all the same.
Also, again, I'm just making a general point, but anything client-based can be detected.
how? when you use API functions like ReadProcessMemory, the process can know you used it.
and even if you use API functions like SendMessage/PostMessage/SendInput/etc, the process can still see it in its WndProc function.
window messages are a little tricky since those messages will be the same as the real ones a player will send without a macro.
but it's still possible, especially with games that are using DirectInput which is talking directly with the hardware.
So in theory, if a macro is detected by the client, it can send a packet to the server to let it know you're using a macro.
where if you only use packets, such thing will never happen.
Quote:
Originally Posted by Roibot
What I was speaking of is If you send in the wrong packets or something of the sort. You can be instantly banned, When I say I rather not mess with it. It is because of that reason alone. Which is a yes I do not understand packets on the same level as you.
|
Again, that is exactly what I'm trying to explain here.
obviously sending incorrect packets is more risky than not sending them at all.
but you were willing to try what Shane posted if it was something with CE but not with packets because of the reasoning that packets have a higher chance of banning.
but you fail to understand that if you'd edit something with CE and then let your client tell that to the server, it would do that by the exact same way, by sending a packet, the same packet actually.
so not only it's the same (functioning-wise) it has a higher risk because you actually use ReadProcessMemory/WriteProcessMemory or even injection which can easily be detected by the client and told to the server.
my point was, if you are ready to try it with CE, there's no reason not to try it with packets.
not trying to force you into anything of course, just trying to explain the subject better
Anyways, I can't stress this enough. I wasn't trying to dis you in any way, I guess it was just a bad choice of words by saying "your bot", it just seemed easier to explain.
once again - I respect, thankful and grateful for your sharing. I'm sure your program is very good and reliable and I really was just trying to make a general point which wasn't directed to you.
it was just bad choice of words.
sorry if I offended you.
I mean. How to use those packets.
