@advanced scripters: How to open doors in safer way

[blackd]

Blackd Proxy 19.1 :
- New command to do game inspect in a square near you: exiva check x,y,z
- New variable to check last game inspect result: $lastcheckresult$

This should allow advanced scripters to code safe checks over doors (because it is not a good idea to send a open-door packet against an already-opened door)

Safe procedure to deal with a door at position x,y,z:

fastExiva check x,y,z
waitX 5
IfTrue ($lastcheckresult$#string<>#You see a closed door.) Goto $nlineoflabel:alreadyopened$
fastExiva > packettoopendoorXYZ
:alreadyopened
...

(You will need to inspect the packet that open door at x,y,z to get the custom cheat command)

[BldMx]

Thanks so much for listening my suggestion!

How ever this still need to be improved.
$lastcheckresult$ should not return a string that comes from the server but rather the item ID that is there, that way if someone blocked the door with something or someone you could issue and exiva command to move that item or thing or to react accordingly.

[ferigon]

Daniel could you please add some command for that? I've been trying to do a 100% safe way to open doors in my script but it takes so much lines and so much work that I stopped to bot in places that require a key to the door, there are MANY variables that could happen when you try to open a door:

You must use the packet to open/close door at same X, Y, Z position, that will require a X,Y,Z pos check and a procedure to reposition if youre not in the right place.
Its locked by key, so you will need a key to be in a specific square of a Bag/BP, because even the key in a miss square will change the packet. ( The string check of a door locked by key is "You see a closed door. <new line> Its locked." the bot cant detect the new line. )

Anyway I dont recommend people to use scripts with doors on the way, theres a big risk of send invalid packets.

[xHellsx]

Daniel could you please add some command for that? I've been trying to do a 100% safe way to open doors in my script but it takes so much lines and so much work that I stopped to bot in places that require a key to the door, there are MANY variables that could happen when you try to open a door:

You must use the packet to open/close door at same X, Y, Z position, that will require a X,Y,Z pos check and a procedure to reposition if youre not in the right place.
Its locked by key, so you will need a key to be in a specific square of a Bag/BP, because even the key in a miss square will change the packet. ( The string check of a door locked by key is "You see a closed door. <new line> Its locked." the bot cant detect the new line. )

Anyway I dont recommend people to use scripts with doors on the way, theres a big risk of send invalid packets.

With a locked door.

As it is possible to send an open command to one and it be denyed (use a locked door) then just put see door... if its closed use it... if its still closed use key on it.

No bigggy

[Hans Henrik]

With a locked door.

As it is possible to send an open command to one and it be denyed (use a locked door) then just put see door... if its closed use it... if its still closed use key on it.

No bigggy
<strike>just note: that is something the real tibia client will never do, is incapable of doing, without the help of a "3rd-party tool"... thus, i consider this risky.. :p</strike>
just thinking.. Yes, with lag, and 2 persons, the real tibia client is capable of doing this on its own, so nvm what i said ^

[Oufo]

i wana ask what's the packet 2 open door ..
i did fastexiva check Xyz of door
and then wait
and then lastmsg thing
then how to find out the pakcet thing ??