Our beloved mods would like us to believe that it is not possible, that HB must complete a quest before starting on another. Unless of course one of the quests involve hostile mobs that trigger the combat bot. In this case, we get one quest for free, as it were.
But if one of the quests involve neutral mobs, or gathering items, then we are out of luck. We must stand by, helpless, while the toon rushes along the quest mobs/items to look for another mob/item further away. It just does not seem to make any sense. And in fact, it does not.
HB's xml implementation is just that: one possible implementation. It is only a matter of basic programming skills, but mostly of policy, to add extra instructions to the xml model to make multi-questing possible.
The me.hastarget instruction could easily be implemented in xml, and then the bot would attack even neutral mobs if they are part of a quest, whenever it encounters them.
Anybody who has once tried to read a profile has seen the while-instruction at least once. That is a run-time instruction. That is, when Hb encounters this loop, it keeps going back to the start of the instruction until the conditions are fulfilled. A compile-time instruction would be the load-profile-instruction. If you misspell the profile's name, Hb will stop right away.
Me.has.target is a runtime instruction, and once again, there is absolutely no reason why it could not be implemented in HB's xml.
That is, as long as the devs stick to this inefficient model, might as well milk it out.
But if one of the quests involve neutral mobs, or gathering items, then we are out of luck. We must stand by, helpless, while the toon rushes along the quest mobs/items to look for another mob/item further away. It just does not seem to make any sense. And in fact, it does not.
HB's xml implementation is just that: one possible implementation. It is only a matter of basic programming skills, but mostly of policy, to add extra instructions to the xml model to make multi-questing possible.
The me.hastarget instruction could easily be implemented in xml, and then the bot would attack even neutral mobs if they are part of a quest, whenever it encounters them.
Anybody who has once tried to read a profile has seen the while-instruction at least once. That is a run-time instruction. That is, when Hb encounters this loop, it keeps going back to the start of the instruction until the conditions are fulfilled. A compile-time instruction would be the load-profile-instruction. If you misspell the profile's name, Hb will stop right away.
Me.has.target is a runtime instruction, and once again, there is absolutely no reason why it could not be implemented in HB's xml.
That is, as long as the devs stick to this inefficient model, might as well milk it out.