When writing behavior override profiles its sometimes helpful to know what some of the internals of QBA and what it is doing.

QuestBotAlternative examines all of the NPCs and objects in your general area, and asks each of its handlers if they need to do anything with it.

Each handler is designed to do a specific objective. eg, click on a sparkling quest item lying on the ground.

If a handler says it knows what to do, it's given the opportunity to give QBA a list of single actions to take (move here, interact, then click accept quest. that sort of thing). These are stored in the bots queue.

QuestBotAlternative carries out each of those queued up single actions one by one in order. And only once the queue is done will it look at the other NPCs and objects around you for new stuff to do.

If it can't find anything to do nearby, it moves to a quest objective's AreaPoint Hotspot somewhere else nearby to try looking again.

On its way to the new HotSpot it will keep looking for things to do, and won't continue to the new location if it finds something relevant.

- Because QBA is scanning through the nearby NPCs and objects, it means that the Hotspot that QBA used to get here doesn't need to be 100% accurate.

The scanning range is about 100yards, so you just need to get it into the general area to be able to find the nearby NPC or object its supposed to handle.

However if the quest objective is inside a building, a tall tower or some deep cave you may need to set the Hotspot closer to the objective. These locations often have 2 possible positions in the game world (one deep inside the cave underground, and one above ground), and QBA won't know which place to go looking if you don't tell it.

- When QBA is looking for a handler for an NPC or object it will check all your currently incomplete quests and objectives, if it notices that a quest or an objective has a handler override it won't consider any other handlers than the one you set.

It is expected that this handler will know what to do in this situation, if it doesn't the bot will probably get stuck.

- If the bot notices that you're in combat, it ignores the queue. Most of the time it empties the queue completely.

This is so that after the combat is over it can re-examine the nearby NPCs and objects. So sometimes QBA might ask the same handler if it wants to handle a quest objective over and over, because it keeps getting stuck in combat on the way there.