Fairly simple and straightfoward, you should create a logout() function that closes the connectiong between the client and tibia so we can create scripts that xlog under certain circumstances.
Printable View
Fairly simple and straightfoward, you should create a logout() function that closes the connectiong between the client and tibia so we can create scripts that xlog under certain circumstances.
Could achieve the same thing by creating a script to watch your targets health. (not real code, just an example in simple english):
Basically, if the targets health goes up, then stop targeting and send the walker to the label 'exit:'Quote:
targetCurrentHealth = target.health
if target.health > targetCurrentHealth then
cavebot.stop()
walker.start()
Walker.Goto("exit")
end
Of course, if the monster you are hunting heals itself, then you would have to set a specific amount of healing to trigger the effect.
ive got my script in order, and what your suggesting doesnt work because I could be anywere on the wpts offscreen from where the exit label would be. the logout function is an imperative necesity to what i am suggesting.
How would a logout function help you? If you are fighting a monster and someone heals it, you cannot logout because you are in battle. And if you xlog then you will stop healing yourself and die. What is it you want this function to do?
It is an xlog function bro, if someone heals my monsters it usually means they haven't got me surrounded yet. So if it auto disconnects the moment they heal it I will xlog, making the monster stop atking me for 30 seconds then giving me a 30 second window to logout before I die. My knight and a lot of other peoples knights are high enough levels to live for 30 seconds without healing. That's why, and whether or not you can think of a use for the function it would be helpful in a lot of other situations.
You guys could also stop complaining about a feature that everybot used to have and this one doesnt, it would be nice to have, usefull sometimes, thats it. I approve this one.
And if you bothered checking Suggestion List II then you would know that it has already been suggested and you also would have seen that DarkstaR said "No comment" about it.
I've seen this suggested before, however - I honestly can't believe that this bot does not have this function. It's such a great bot - but I agree with @Funkgary that this would be SOOOO useful for a very wide variety of applications, despite what anyone says.
I realize there are some other work arounds, but once again - I agree is it not the same thing as a log out function or Xlog function... Just my 2 cents
I went out of the way to create my own program that will reconnect after disconnects. I have the .LUA write a variable to a text file upon logging out because of low stamina and my program reads that file. It avoids logging in around server save and makes several checks so it does not attempt to inject or log in after an update. This allows me to run 24/7 basically on any account with 3 or more characters. Whenever the settings are loaded for a script. I have the .LUA open the backpacks and then I make a bunch location checks with an isLocation() function that I created to find out where to move the walker to, avoiding the walker stuck. There are still a few bugs in it, but I have been running 3 accounts for almost 3 days straight now switching between characters with no problem. It is really nice for when my ISP disconnects or Tibia lags... Sadly, I had to rely on mouse clicks to control xenobot as it has some sort of protection against debugging tools.
I don't understand why Xeno does not have a logout/reconnect feature built in. I have heard it was unsafe but never heard the explanation as to why.