[Update] XenoBot v2.8.8

[sirmate]

You can pick target priority. What the fuck is "stickiness?"

"stickiness" > Whether targeting should tend to stick on the target it has previously chosen (currently attacking) or nope.
Guess it's connected with "If still ambiguous, select parameters which creature we're currently attacking" this rule.

[kreoo]

Thats an awesome update! Thx!
Any ideas on when it will come with anti KS? only target monsters that are targeting you? This would help bunches since people are reporting and/or engaging in conversations with my afk chars when I atk their monsters:/

[DarkstaR]

"stickiness" > Whether targeting should tend to stick on the target it has previously chosen (currently attacking) or nope.
Guess it's connected with "If still ambiguous, select parameters which creature we're currently attacking" this rule.

Well, that rule makes it stick to the current target, no matter what, UNLESS a higher priority monster appears. That's how priority works. I may look into stickiness sometime, though.

[XtrmJosh]

Thanks Nick, appreciate this update (and you pushing the logging stuff in to resolve this issue). Sorry if my bug report misled you, though there was a bug, the bug wasn't quite as much of a blocker as suspected.

Not sure about everyone else but I think some advanced logging would be epic (aka a button in Tools or something). It could record all actions, callbacks, function locations (aka called myfunction() from mylib.lua with return value true). I'll make a proposal about it and see where we end up. It's a nice thing for users to be able to monitor, since it will help us fix any situations we're encountering!

[DarkstaR]

Thanks Nick, appreciate this update (and you pushing the logging stuff in to resolve this issue). Sorry if my bug report misled you, though there was a bug, the bug wasn't quite as much of a blocker as suspected.

Not sure about everyone else but I think some advanced logging would be epic (aka a button in Tools or something). It could record all actions, callbacks, function locations (aka called myfunction() from mylib.lua with return value true). I'll make a proposal about it and see where we end up. It's a nice thing for users to be able to monitor, since it will help us fix any situations we're encountering!

This was my initial though. But then I realized something: if the bot crashes, which is usually good cause to read a log, the log is inaccessible.

[XtrmJosh]

This was my initial though. But then I realized something: if the bot crashes, which is usually good cause to read a log, the log is inaccessible.

Perhaps (and this is probably a large amount of work for a little reward) you could use some TCP/IP command system. Whenever a function is called within the bot or in Lua, you could call a TCP/IP send function, and send the command with parameters to a local TCP/IP server, which would simply write the data received to file. That way every function which was called would first be sent to the server and recorded, and although we may not wait for a response from the TCP/IP server, the logs should get updated in time to be able to review the data.

Though I don't think crashes are to be expected, I think this may be the best decision if you intend to use it as a developer resource (I was thinking more as a user resource).

[raiQi]

Gracias senor, will test soon :P

[kreoo]

@DarkstaR , you said we could set it to exori gran if 3+. But lets say I want to use exori min, is it possible at the moment? or it will cast independent of my current direction?

[kreoo]

@Rydan the current script for this action is kinda messy... I mean, when Im using the diagonal instance it just doesnt work, it misses a lot!

Thats why I was wondering if Xeno had it native now since its a spell and its not going away.

Thank you!

[WorkingHandz]

this update sounds promising. how is it working so far? I would update but the current system is good enough for me at the moment so no need to rush.