A question concerning Exiva Buy

[Lithium]

We know that this was the unhealthy exiva cmd sending out wrong packets if we were not near the vendor or have the cap and try to buy MORE then the character can actually hold ( normal Tibia menu would not do this ) I suggest a few things here.

1 . Always buy the correct amount of potions, have this pre - calculated. I have explained this on a thread before but It may have been missed so I will explain very briefly I hope you catch the drift.

Start Script > Walk to cave > Fill up at Cave > Start Deposit > Go Directly to Mana Shop, say Hi, Deposit All, Yes. >
Goto Banker and Deposit All Cash ( Empties were now turned into Cash ) > Deposit Loot > Withdraw 5000 Gold > Walk Back to Mana Shop Exiva Buy:01 0C:100 > Back to Depot > Re-Loop Script.

That is very brief and broken down, but I made sure that every time he only buys 100 Potions and he withdrew the exact amount of gold FOR 100 potions.

2. I was thinking since the only other reason this actually did not work was because either you were Blocked and couldn't path to the Mana shop, and or lag or some reason your bot did not make it to the shop and says Exiva Buy:xx xx:n in the middle of the depot. ( Not a good thing ) So I was thinking over it and It came to me, what if there was an .. IfTrue MyXYZ=(xxxxx,xxxxx,x) Exiva Buy:XX XX:N

So technically he would just double check that he was at the co-ordinates infront of the mana vendor and THEN he would actually send the Exiva Buy:xx xx:n

Any suggestions tips would be greatly appreciated,

-Lith

[provocate]

Smart indeed.

Well this is how I do it usually ...

Well it's kind of the same lol ^_^. I just record packets in Proxy and use them in the actual script as 'sayMessage exiva > blablablablablablablabla', if it's either for opening hole with a shovel, roping or buying potions.

So for example, 300 mana potions is more than enough for me to fill full cap of gold in a cave, therefor bot will buy mana potions until it caps them 300 or more like so:




IfTrue ($countitems:0C 01$#number<#300) Goto $nlineoflabel:xodet$
:xodet
move 32399,32220,7
sayInTrade hi
waitX 1
sayInTrade trade
waitX 1
sayMessage exiva > 7A 0C 01 00 0A 00 00
waitX 1
stackItems
waitX 1
IfTrue ($countitems:0C 01$#number<#300) gotoScriptLine 7
IfTrue ($countitems:0C 01$#number>=#300) Goto $nlineoflabel:backtothecave$



sayMessage exiva > 7A 0C 01 00 0A 00 00 ... Buys 10 mana potions.
IfTrue ($countitems:0C 01$#number<#300) gotoScriptLine 7 ... Assuming that 'sayMessage exiva > 7A 0C 01 00 0A 00 00' is on line 7.

Of course, you can buy more than 10 potions at once, even 100, I just put 10 for an example, because if someones needs only 300 potions for one round then it's useless buying 100 at once if you already have like 290 capped, then you'd have 390 capped, which from point of capacity left for gold ain't that good. Better loop script 10 times than buy too much pots than needed. :)

Of course like you Lithium said, you gotta make sure you have enough cash, so I always deposit empty vials, deposit gold at the bank, withdraw cash for at least 300 mana potions and then I head back to Magic Shop. 10 mana potions cost 500 gp so leftover cash isn't really a 'cap issue' since those platinum coins weigh less than 10oz.

Hope it helps somehow. My scripts are usually FULL of 'sayMessage exiva > blabla' commands along with ifTrue's, it looks a mess, but it works like a charm! :)

Edit: You might have noticed that I use a lot of waitX 1's ... I don't know, I always put these in front of and after the 'sayMessage exiva > blabla' commands and after or before ifTrue's ... I find it more secure than just flying through script like a mad man and probably get caught. I take it slow, few more seconds won't hurt.

Edit2: @Lithium, what's your timer in Cavebot usually?

[Lithium]

I totally agree with you, I toss in extra waitx1s when necessary. See the thing I really dont like about this and correct me if im wrong, but every update it seems I would have to update this string? "sayMessage exiva > 7A 0C 01 00 0A 00 00" What is to say next patch when I just run my bot script and he gets banned because these are no longer the packets to buy mana potions? What I am saying is we need a universal type of "Buy" that doesn't involve having to update our packets every patch and need to worry about sending "wrong" packets. But thank you very much for the explanation, I would love to learn how to write the fastExiva msgs myself and how to "record" the packets like you say you do. If you are ever up for giving me a lesson send me a PM I am always thirsty for knowledge,

Sincerely,
Lith

[provocate]

You're right, it may change from update to update, but I haven't noticed any change for quite a while now, since like ... I don't know, didn't even notice any change after all this years playing Tibia. Yeah, it hasn't change at all.

And of course that can get you easily banned if you're using outdated version and if they decide to change packets fot that, that's why I try to check those packets I'm sending every new update and update my scripts if necessary.

I love to record these packets and use them in scripts simply because those are the same packets I'd send if I wasn't using any bot at all. Which adds to security quite a lot.

And no problem, it's damn easy to record them, I'll take a few screenies and send you a PM explaining all. Probably tomorow. Off to bed in like an hour and I still have to script Thais north Rotworm cave for some nice profit. ^_^

Or I'll maybe write a little tutorial so anyone can easily script things with this amazing bot! D: ^_^

[provocate]

Whoa this is weird! o__O! Noticed it yesterday when I recorded packet for roping myself one floor above at certain rope spot and it seems like it ain't safe anymore ... o__O?!

http://i.imgur.com/A7NXR.png

But why is that?! If I load the script I wrote above for mana shop which uses 'sayMessage exiva > blabla' as well, it doesn't give a warning sign at all ... Weird! o__O

I thought that was the most secure option to do, record packets tibia client is sending to Tibia and use them everytime you get to that certain rope spot for an example.

Now I'm not sure if I should write a tutorial at all, cuz this is super weird! One 'exiva' command is detectable and the other one isn't D:!

[xHellsx]

Whoa this is weird! o__O! Noticed it yesterday when I recorded packet for roping myself one floor above at certain rope spot and it seems like it ain't safe anymore ... o__O?!


But why is that?! If I load the script I wrote above for mana shop which uses 'sayMessage exiva > blabla' as well, it doesn't give a warning sign at all ... Weird! o__O

I thought that was the most secure option to do, record packets tibia client is sending to Tibia and use them everytime you get to that certain rope spot for an example.

Now I'm not sure if I should write a tutorial at all, cuz this is super weird! One 'exiva' command is detectable and the other one isn't D:!

All Hex scripts now come with a warning so that newbi people are aware a script they downloaded may be detectable.

Also, why use a hex for rope/shovel? BlackD finds and does this automatically... Using a hex ontop of it will likely result in a double hex being sent and you being detected.

[provocate]

Also, why use a hex for rope/shovel? BlackD finds and does this automatically... Using a hex ontop of it will likely result in a double hex being sent and you being detected.

Never happened D:. There's always a chance of course, but I've always used hexes no matter what. I'm just being careful it doesn't send those twice, for an example slightly larger cavebot timer. Worked like a charm everytime! D:

Edit: Obviously every bot is detectable, there's no doubt about it, I guess banwaves are just random among those who were reported, that's all. D:

[Lithium]

I think Hells is correct there Provo~ If you were to attempt going into Fibula Well or through a Locked Door, then yes by all means your Fastexiva> string works, but when using regular ladders/rope holes/stairs, all that is required is the simple Move command.

ex. move xxxxx,xxxxx,5
ex. move xxxxx,xxxxx,6

Basically you just need the direct spot under the hole/ladder ( Right infront of the stair 1 SQ before moving up a floor ) and the exact waypoint when you land up the hole/ladder/stair. and Voila no hexing required for that. I would still love to see your tutorial on the fastExiva > Mana strings though, I have never understood that and I am quite lazy so I probably wont use/update it every patch like you, I have multiple scripts and multiple accs to bot I do not have time to check if they are safe EVERY patch. That is why I suggested a quick method of fix with the IfTrue MyXYZ, Seems like the most brilliant solution to me but I am not an advanced scripter so I would like to hear any suggestions on how to fix the EXIVA BUY command so we do NOT have to send large strings of packets.

Edit; By the way I honestly do not care for the buying manas part. All of my scripts are pre-set with Food/Enough Manas to take care of themselves and fully blessed to never lose a piece. I am working on a fix for those who like to run everything 100% hands free and I would like to make it a little easier for beginner scripters than having to learn large strings of the FastExiva cmds.

-Lith

[xHellsx]

You don't even have to have waypoint on rope spot/above. just the general idea and blackd will find a way!

[Lithium]

I remember when I was a beginner scripter and I did not use the way I speak of Hells, there would always be a problem and he would be stuck saying There is no way. Since I started scripting like I speak of, Blackd has little to no troubles of ever making the mistake. I think the most problems were the dwarf caves in Kazordoon, I had to re-write that script many of times before it would ever properly work, and once it did all hail the Iron Ore.

Any suggestions and the ifTrue MyXYZ=(xxxxx,xxxxx,x) would actually work or is this just hoping and wishing?

-Lith