Es läuft ...

[mn123]

der jarb geht nicht -.-

[Gertos]

I have added a usefull link from Night Dragon to the first post.
This link can save you a lot of time.

[Night Dragon]

Originally Posted by Gertos

I have added a usefull link from Night Dragon to the first post.
This link can save you a lot of time.

HINT: Heads up, you will need to know Visual Basic/C++ if you want to use these files since you will have to figure out where the interface commands are.

[meilleur]

Originally Posted by Night Dragon

HINT: Heads up, you will need to know Visual Basic/C++ if you want to use these files since you will have to figure out where the interface commands are.

U have more hints, me too i want to make my own bot, well i have little knowladge in c++ but not engouth to make an advanced program, atm iam trying the way that given hallimasch.

[meilleur]

What consist of built our own driver? and what is the goal? got new commande not blocked by GG and let us communicate with mouse/kyboard? what language should i use?, is pmx.dll and winring0.dll do the same function?

[Gertos]

A world about the different Ready-to-use Device driver that are downloadable somewhere in the net.

GG knows this driver as well and has some 'tricks' to stop the functions.

The Typical Construct is this

BOT GUI --(1)--> Device-Driver --(2)--> Windows Core --(3)--> Game

GG don't sees any difference between your data and the normal mouse /key data at 2 and 3. So it is impossible to stop the injected infos there.

Therefore they try to stop the data at 1!
All common way to talk with a device driver are stopped from them.

But the nice fact on position 1 is , you own the control on both parts ( sender and receiver) So you can use a lot different ways to transfer your data to your driver.


So make sure your device driver has a 'special' way to communicate.

If you see an effect like:
All works perfect with any programm,but stoped working with the rappelz window, your may found the above problem.

[Night Dragon]

Originally Posted by Gertos

A world about the different Ready-to-use Device driver that are downloadable somewhere in the net.

GG knows this driver as well and has some 'tricks' to stop the functions.

The Typical Construct is this

BOT GUI --(1)--> Device-Driver --(2)--> Windows Core --(3)--> Game

GG don't sees any difference between your data and the normal mouse /key data at 2 and 3. So it is impossible to stop the injected infos there.

Therefore they try to stop the data at 1!
All common way to talk with a device driver are stopped from them.

But the nice fact on position 1 is , you own the control on both parts ( sender and receiver) So you can use a lot different ways to transfer your data to your driver.


So make sure your device driver has a 'special' way to communicate.

If you see an effect like:
All works perfect with any programm,but stoped working with the rappelz window, your may found the above problem.

Are you sending the keystrokes from kernel mode?

[Gertos]

yes, I do.

[meilleur]

Any one know how I can find port adress for exemple I/O port keyboard?

[Gertos]

Why do you want to know the keyboard port ?
Writing data into a port works under DOS , but not under windows.

But anyway, check the properties of your Device Manager from windows.
There is a page with the used resources

[TheMan!!]

Originally Posted by KentuckyFC

Da gegen kannste nix machen musste den bot umschreiben damit der es richtig liest

Doch kann man,man muss mit CE die Pointer adressen herausfinden die werden
nie geändert ^^

[Night Dragon]

Well if its the same thing as JT's bot but just updated to work with the new GG then the instructions for it should be the same. You can find more info here:

[gremium]

Looks to me like a virus,
Trojan Agent.bcn found by antivir ...

[aenileb]

oh no, trojan....... i will search for a new bot

[meilleur]

I want to use the commande /position, how can i make my bot read this ?