Malmis
07-07-2007, 23:15
I have seen it used in a few scripts, but I thought I'd try to explain how you do it.
It is recomended you only are using one client when you try to do this. But if you have several clients online, first find out what ID your client has in the Proxy. To do this, I don't know if there is a better way, but I go to "tools" and use the "Fake messages to self" function and try different IDs there.
When you know what ID the right client is open the "Proxy" window. Here you check the small box called "log packets" and then you open and close the door, then you uncheck the box. Now you should have a bunch of logged packets.
The ones we are interested in are the ones that have the prefix "GAMCLIENT-ID->( hex )". Try to find the first line that is sent FROM your client ( > ) and copy only the hex. But remove the first four characters from the hex, they're called headers and the "exiva" command automatically adds them. Stand next to the door and write "exiva > -hex-". If it is the right hex the door will now open. Try to find the hex to close the door, it should look very similar to the first hex you have.
Try both hexes a few times to open and close the door. Then you make a waypoint at one side of the door and add a "sayMessage exiva > -hex to open-" to open the door. Then make a waypoint at the other side of the door and use "sayMessage > -hex to close-". You don't really need to close the door again, but you can if you wish. Make sure you really use the right arrow ">" and not "<", because if you do the client will crash.
To make sure you are at the right spot when sendind the hex, make a waypoint at the door and then another one. Because of lag or too fast execution the bot may not be at the right coordinates.
To use a key to enter a place (like Fibula rots), place the key in the ammo slot, there it will have a "fixed" position, if you have it anywhere else the hex to use it may change. You record the hex in the same way as with normal doors.
Sorry that I don't have any screenshots, but I hope this may be useful anyways.
It is recomended you only are using one client when you try to do this. But if you have several clients online, first find out what ID your client has in the Proxy. To do this, I don't know if there is a better way, but I go to "tools" and use the "Fake messages to self" function and try different IDs there.
When you know what ID the right client is open the "Proxy" window. Here you check the small box called "log packets" and then you open and close the door, then you uncheck the box. Now you should have a bunch of logged packets.
The ones we are interested in are the ones that have the prefix "GAMCLIENT-ID->( hex )". Try to find the first line that is sent FROM your client ( > ) and copy only the hex. But remove the first four characters from the hex, they're called headers and the "exiva" command automatically adds them. Stand next to the door and write "exiva > -hex-". If it is the right hex the door will now open. Try to find the hex to close the door, it should look very similar to the first hex you have.
Try both hexes a few times to open and close the door. Then you make a waypoint at one side of the door and add a "sayMessage exiva > -hex to open-" to open the door. Then make a waypoint at the other side of the door and use "sayMessage > -hex to close-". You don't really need to close the door again, but you can if you wish. Make sure you really use the right arrow ">" and not "<", because if you do the client will crash.
To make sure you are at the right spot when sendind the hex, make a waypoint at the door and then another one. Because of lag or too fast execution the bot may not be at the right coordinates.
To use a key to enter a place (like Fibula rots), place the key in the ammo slot, there it will have a "fixed" position, if you have it anywhere else the hex to use it may change. You record the hex in the same way as with normal doors.
Sorry that I don't have any screenshots, but I hope this may be useful anyways.