May i ask what was insufficient in the interact behaviour?
Of course:
There are 2 known issues I've encountered with InteractWith. (Sorry I have not posted an official bug report on them)
1) In Ruins of Guo-Lai, on Quests "Hard as a Rock" and "No Stone Unturned", the Mogu Statues in the area need to be Right-Clicked to activate. There are two outcomes:
1 statue (63447) will come to life and attack!
The second (63556) will tip over and die.
The issue is after the first statue is interacted with (whether its the first or second type) the second will not accept the interact command. It will loop endlessly saying it is interacting, showing in the logs that it is properly interacting, but no change occurs on screen. I went into the plugin and added a "If != NULL, then Interact" to both types. This fix was used with the flames in Mistfall Village, and every time you walk over one, it gets "right-clicked". This fixed the problem, since InteractWith already closed the gap to 1 yard (by Range), then the plugin takes over and right-clicks.
2) In Mistfall Village, I've noticed that any InteractWith commands to seek out multiple objects (examples: Flames on ground, Cornered Villagers) will report to the bot that it is interacting with a HUGE list of them all at once (shows: Interacting with: Cornered Villager, Cornered Villager, Cornered Villager, Cornered Villager, Cornered Villager, Cornered Villager, Cornered Villager, Cornered Villager, Cornered Villager, Cornered Villager) As it is interacting (with villagers) it moves around properly, does as intended, but never breaks the InteractWith command after completion. Even with a NumOfTimes="1", it will still interact endlessly between all Villagers, new and old at the time of execution.
2a) Secondly is the Flames on the ground for "My Town, Its on Fire". There are lots. And as I said above, if I use InteractWith, it makes a list of Flames a mile long (see above example with villagers). It will approach one of the flames.......pause for 5 seconds.....interact with the flame intended.....pause for ~20-30 seconds......then attempt to interact with the same flame again whether or not it is there. Even though there are MANY more around it, it will stick to one spawn and never move. I countered this with adding the Fire[0].Interact into the plugin ages ago, but it only works while the bot is in motion over flames, so i changed it altogether to farm for water buckets and use them...which does bring up another issue...
3...or C...or maybe III) UseItemTargetLocation: If items intended for use = 1, and is properly used, Custom Behavior then sticks, thinking 0 is a valid number of inventory items and tries to use endlessly. I have countered this by making sure it never drops below 1 in inventory (GetItemCount check) but it would be more efficient if I only had to get 1 at a time.
Sorry for hijaking the post for a bug report.