EQ2Bot - Recent looting issues?

[TheDragon]

Hopefully, I am posting this in the right forum.

I'm not sure exactly when it started, but over the last few days, I've noticed that chests aren't always be looted by the brigand or fury scripts. I haven't tested any other toons, as those are the only characters I have using with the bot. The chests just sit, unopened. If I manually click on the chest, EQ2BOT jumps in and loots it... otherwise, it will run by it.

In addition, I've noticed several chests that refuse to be looted if they contain a no trade item. Specifically, a NO TRADE page for collections. The chest gets opened, but not looted. The item in question is NOT lore, so it's not trying to loot two LORE items.

Is this a known issue? I don't remember it happening this often before. I did notice that there was some recent changes to the loot menu in the UI.

I am running the latest build of EQ2Bot from SVN with a 54 brigand and a 33 fury with unmodified class scripts.

 

[Amadeus]

The whole looting thing is going to be redone soon. The "Multiple items in a chest" thing specially should be fixed soon. The skipping of chests is something that I noticed myself but should not be happening. Hopefully it will be addressed soon.

As a side note, eq2bot is not designed to be run without ANYONE at the keyboard ..lol...so, the fact that it is not clicking on chests is not a huge deal since someone should always be playing SOME toon that can click on a chest easily.

 

[Amadeus]

I just updated eq2bot to fix the whole "skipping chests" thing. Looting should happen now as it was prior.

 

[TheDragon]

Thank you!

 

[TheDragon]

I wanted to confirm that whatever fix you made seemed to do the trick.

 

[Amadeus]

I have noticed some weirdness with FastMove() ....which might be causing issues as well. For some reason it's returning STUCK sometimes when it should not be.

 

[Amadeus]

Actually, it finally hit me that the reason my eq2bot wasn't looting was because it couldn't "move" since that EQ2 session was not "in focus" (ie, the same reason eq2harvest will not run if other windows are open on top of it.)

Anyway, I decided to work on this. Here are the patch notes from the latest version of eq2bot:

;2.7.2 (Amadeus)
; * If your 'forward' key is mapped to one supported by the new "EQ2Press" command, you will now move to loot chests and corpses even if
;   the bot is not in focus (ie, if another window is opened on top of the one in which the bot is running.)
;   (Dev. Note:  This change was applied to FastMove(), so any call to it should now work in the same fashion.  Also, see FastMove() on how
;                to properly impliment the new "EQ2Press" command.

and ISXEQ2:

April 26, 2008 -- By Amadeus
[ISXEQ2-20080408.0111]
* Added new MEMBER to the 'isxeq2' datatype:
  1. IsValidEQ2PressKey["keyname"]   (bool type)   "return TRUE if the 'keyname' is a valid "EQ2Press" key combination"
* Added new COMMAND "EQ2Press":
  ~ Syntax: EQ2Press -keylist
            EQ2Press -hold <key combination>
            EQ2Press -release <key combination>
****
**** The benefit of "EQ2Press" versus "Press" (innerspace command) is that it will work even when the EQ2 session in question
**** is not the one in focus (ie, you have another window opened on top of it).  However, not all 'key combinations' are supported
**** initially, so scripts should double-check using ${ISXEQ2.IsValidEQ2PressKey[]} before issuing the command (else use "Press")
**** and users/scripters should check "EQ2Press -keylist" periodically to see what key combinations are available.  (Requests can
**** be made on the forums.  Also, please note that only keys that are designed to be "held down" work properly with this system.
****
**** Another bit of good news with this system is that if you are "holding" down a key using eq2press (ie, the "w" key for moving
**** forward), you can type <enter> and use the keyboard without it typing "wwww..." into the chat window.  You will pause moving
**** while typing; however, once you hit <enter> again, you will resume on your way.

I will be adjusting more of eq2bot and eq2harvest to utilize this new functionality soon.