well it's a difficult decision.
Landing direct on the node :
"bot hunter" player can report you, because most "but hunter" player don't believe you can land direct on a node without beeing a bot (most people don't know you coul do this with click to walk without beein a bot)
Landing near a node:
as you seed the bot could get stucked and this looks more "bottish" than landing direct on a node
But back to "bot hunter" Player. In most "bot hunter guides" made by "bot hunter" player you could read methods to dectect a bot. As an example, these guides could be reading within the battlenet board. Most "guides" says you can detect a bot just by seeing how it gathers herbs / mines. Bots fly over the herb, dismount and now the fall down and gather the herb.
No human flys over the herb and falls down, the fly to the ground and dismount.
But, as most parts of hb are open source users how want to avoid the risc of beeing detected by "bot hunter players" and want to increase the risk of beeing detected during the enviroment (getting stacked) should be able to change the bot behavior.
I thought we could easly change FlyToAction.cs
PHP:
protected override RunStatus Run(object context) {
if (!IsDone)
{
if (ObjectManager.Me.Location.Distance(loc) > 6)
{
Flightor.MoveTo(loc);
TreeRoot.StatusText = string.Format("Flying to location {0}", loc);
}
else
{
if (Dismount)
Mount.Dismount("Dismounting flying mount");
//Lua.DoString("Dismount() CancelShapeshiftForm()");
IsDone = true;
TreeRoot.StatusText = string.Format("Arrived at location {0}", loc);
}
return RunStatus.Running;
}
return RunStatus.Failure;
}
and change the 6 to... maybe 1 but that had no effect.
Maybe someone could give a hint were to look for ;-)
With this way its a user decision with risk he votes higher.