I keep encountering an issue (using multiple different profiles) where Order Bot will successfully open an interaction menu (for say Mining) but will still be too far away to actually be able to activate any options. I'll have to manually close the interaction window, Order Bot will then automatically move closer and reopen the interaction menu, and then normal function will resume. The logs don't show anything other than the large timestamp gaps between it happening and manually resolving it. I've also noticed it attempting to move after opening the interaction menu (even though it was already in range of the node), and then freezing (I assume because it's still trying to move or is confused that the interaction menu is already open). Here's a log showing the behavior: Code: [07:26:44.456 D] [POI Set] Type: Gather [07:26:44.515 D] Requesting path on 152 from <-17.25724, -4.008679, 316.8916> to <-24.3394, -6.965389, 262.707> [07:26:44.586 D] Generated path to <-24.3394, -6.965389, 262.707> in 00:00:00.0705189 ms [07:26:44.700 N] Sprinting [07:26:44.700 D] DoAction Spell 3 0xE0000000 [07:26:46.761 D] Moving to next hop: <-24.24239, -7.833789, 271.9018> (Moving to gather) D: 30.78656 [07:26:50.585 D] Moving to next hop: <-23.0727, -7.833789, 265.9056> (Moving to gather) D: 7.006962 [07:26:51.367 D] Moving to next hop: <-27.21716, -7.841306, 264.4191> (Moving to gather) D: 4.650029 [07:26:51.728 D] Targeting Rocky Outcrop 0x400001B7 0x1365ECA0 [07:26:51.787 D] Interacting with Rocky Outcrop 0x1365ECA0 [07:26:51.846 D] Moving to next hop: <-25.48599, -7.833789, 262.9527> (Moving to gather) D: 2.152558 Here's the log again after I manually closed the interaction menu in-game: Code: [07:26:44.456 D] [POI Set] Type: Gather [07:26:44.515 D] Requesting path on 152 from <-17.25724, -4.008679, 316.8916> to <-24.3394, -6.965389, 262.707> [07:26:44.586 D] Generated path to <-24.3394, -6.965389, 262.707> in 00:00:00.0705189 ms [07:26:44.700 N] Sprinting [07:26:44.700 D] DoAction Spell 3 0xE0000000 [07:26:46.761 D] Moving to next hop: <-24.24239, -7.833789, 271.9018> (Moving to gather) D: 30.78656 [07:26:50.585 D] Moving to next hop: <-23.0727, -7.833789, 265.9056> (Moving to gather) D: 7.006962 [07:26:51.367 D] Moving to next hop: <-27.21716, -7.841306, 264.4191> (Moving to gather) D: 4.650029 [07:26:51.728 D] Targeting Rocky Outcrop 0x400001B7 0x1365ECA0 [07:26:51.787 D] Interacting with Rocky Outcrop 0x1365ECA0 [07:26:51.846 D] Moving to next hop: <-25.48599, -7.833789, 262.9527> (Moving to gather) D: 2.152558 [B][07:49:01.338 D] Interacting with Rocky Outcrop 0x1365ECA0 [07:49:01.800 D] Targeting Rocky Outcrop 0x400001B7 0x1365ECA0 [07:49:01.848 D] Interacting with Rocky Outcrop 0x1365ECA0 [07:49:02.875 V] Blacklisting 400001B7 for 00:00:30 [Type: All] - Reason : So we don't auto target [07:49:02.878 N] Gathering ItemName:Wind Crystal Chance:100 HqChance:255 Amount:1 RawItemId:10 [07:49:10.329 V] [Poi.Clear] Reason: Node is gone[/B]
Can you share the profile your having problems with? For me I always get right up next to the node in the areas I have tested.
I have this very rarely on certain profiles too, but I never thought it had to do with distance... the bot opens the gathering window but then does nothing. I noticed it a few times while farming Wind Shards with the following profile: View attachment Miner_WindShardCrystal.xml
That was where I had noticed it the most too (Wind Crystal farming). Although my hotspot was: <HotSpot Radius="95" XYZ="-57.55798, -10.11146, 288.4624" /> It hung up a few times during Lightning Crystal farming as well but seemed to do it more in the Wind area.
Now I'm Earth Crystal farming and it's still doing the same: Code: [19:40:27.860 D] [POI Set] Type: Gather [19:40:27.916 D] Requesting path on 135 from <255.3849, 73.2607, -310.0782> to <236.2066, 74.69251, -330.9582> [19:40:27.985 D] Generated path to <236.2066, 74.69251, -330.9582> in 00:00:00.0688494 ms [19:40:28.087 N] Sprinting [19:40:28.087 D] DoAction Spell 3 0xE0000000 [19:40:30.666 D] Moving to next hop: <238.3532, 74.71199, -334.206> (Moving to gather) D: 10.95711 [19:40:31.949 D] Moving to next hop: <237.1645, 74.31455, -334.9602> (Moving to gather) D: 2.330176 [19:40:32.116 D] Moving to next hop: <234.8028, 74.03137, -333.7213> (Moving to gather) D: 3.257867 [19:40:32.394 D] Targeting Rocky Outcrop 0x40000193 0x140CA170 [19:40:32.450 D] Interacting with Rocky Outcrop 0x140CA170 [19:40:32.507 D] Moving to next hop: <235.1027, 74.29298, -332.0846> (Moving to gather) D: 1.730204 (hangs there until I intervene) Profile: Code: <GatherObject>Rocky Outcrop</GatherObject> <HotSpots> <HotSpot Radius="95" XYZ="-122.5412, 21.88736, -489.5768" /> </HotSpots> <ItemNames> <ItemName>Lightning Crystal</ItemName> <ItemName>Lightning Shard</ItemName> </ItemNames> <GatheringSkillOrder> <GatheringSkill SpellName="Byregot's Ward" TimesToCast="1" /> </GatheringSkillOrder> I do have the Botanist cross-class skills BTW (just to eliminate that possibility). It seems to happen regardless of crystal type/spell cast (I haven't tried gathering a non crystal/shard since this issue started occurring). EDIT: And again: Code: [21:58:26.267 D] [POI Set] Type: Gather [21:58:26.324 D] Requesting path on 135 from <267.489, 74.26173, -306.0905> to <236.2066, 74.69251, -330.9582> [21:58:26.400 D] Generated path to <236.2066, 74.69251, -330.9582> in 00:00:00.0764955 ms [21:58:33.122 D] Targeting Rocky Outcrop 0x40000193 0x13BC8A30 [21:58:33.177 D] Interacting with Rocky Outcrop 0x13BC8A30 [21:58:33.232 D] Moving to next hop: <234.9562, 74.07243, -333.5296> (Moving to gather) D: 2.997132
Can you guys tell me what version of patching you are using? I'm specifically interested in the general not settings. Are you using the random path generation, the raw path generation, or one of the other ones. I had this issue when I set it to random. I changed it to "raw" and it worked fine for me
Global Settings > Navigation Post-Processing > Random What are the main differences between them all anyway? They're not very descriptive (at least not in layman's terms lol).
That would be a question for Mastahg...can you try out doing the Raw one and see if you still run into that issue.
Been running the RAW for about 12 hours now with no hang-ups. I'll keep going (and try some other nodes) but it does indeed seem to be an issue with how random pathing is generated (the paths themselves aren't bad, I just think Order Bot might not give enough time for the random path to be fully calculated).
Looks like orderbot was using old path precision value (1.25) where fatebot was using .8. I've adjusted it to the proper value for the next version along with modifying the way gathertag approaches the nodes.