I'm sure you have no control over this as the questing profiles have no listing on how to do it.
But when the bot needs to go and repair it doesn't use flying mounts, it only uses ground mounts, and with the distance between you and the repair vendor/if you are that island in Borean Tundra, HB cannot produce a path to the repair vendor.
Again I don't believe you have control over this, but is there any way we can get the repairing methods to fly to the vendor. Even if it does get a full path it still uses the ground mount, and thus has to kill everything on the way there, which may be very difficult if your gear is severely damaged.
There is no way a profile writer can arrange for this in a 'reactive' mode (say you got into a string of unfortunate deaths and needed to go repair). Honorbuddy itself--not the profile writer--determines when it needs to go repair. The profile writer can adjust the 'go repair' threshold, but that's about it. In short, the
profile is not running when Honorbuddy goes to make its repair/mail runs. Since the Honorbuddy Levelbot (used for questing and grinding) doesn't natively fly--it only flies when the profile writer tells it to--there is no way a suspended profile can issue the needed 'flight directives'.
The only thing that any profile writer can do is to 'proactively' repair/mail. This means that every time the toon passes by a repair vendor or mailbox while picking up, advancing, or turning in a quest, it visits the repair vendor and mailbox. Some users may find this kind of behavior annoying, as the tests would have to be moved from "armor at 20% capacity requires repair" to "armor at 80% capacity requires repair". Of course, its the bot's time, and not yours, so it may not really be a problem.
I believe such 'proactive repair/mail' is wrong to do for two reasons:
- The code to do such would bloat the profile considerably.
This significantly makes a very involved questing profile harder to debug, and much harder to maintain.
- The root cause is that the Honorbuddy Levelbot does not natively fly.
I'm a big believer in solving problems at the root cause. "Chewing gum and shoestring" solutions always lead to problems.
Just some info and my $0.02. But I
very much appreciate your position. I've had a long-standing belief that native flying for the Honorbuddy Levelbot is overdue by more than a year. Kick's even poked fun at me about this by skewing the results of
this poll (subtract 1000 from the actual vote tally to figure out where 'native flying' falls in the priorities of our Community).
Native flying does
so much more than solve the repair/mail runs. It would virtually eliminate all 'stuck' situations in the nav system, among other things. For instance, when you fall off a path onto a ledge with no navigable path, you simply fly away rather than stand there until reported/logout. It also solves problems in Twilight Highlands and other places. While questing or grinding, when your bot is trying to walk through that hill to get a harvest, it would just fly to the harvest rather than getting reported/logged out. Etc.
cheers,
chinajade