Forum › Forums › Discussion › Can't target certain Mining Node.
This topic contains 10 replies, has 7 voices, and was last updated by ryann 7 years, 2 months ago.
-
AuthorPosts
-
October 13, 2017 at 11:51 pm #5469
So far this is the only node i’ve seen Miqo have trouble with.
I see a shiny node at (-569.864319, -170.215195, 15.974350).
The Lochs > The High Bank
When mining Molybdenum ore.
She walks to the node, i see the camera pan all around looking for it, and she spams.
Ummm. I don’t see any sparkles here 🙁
Ummm. I don’t see any sparkles here 🙁
Ummm. I don’t see any sparkles here 🙁
Ummm. I don’t see any sparkles here 🙁This didn’t happen before the update, so i’m not sure why this one node is causing an issue, but You have to baby sit this area because she will just stand there until you do.
Sorry if this is a wrong location, I don’t see a bug post location.
October 14, 2017 at 12:26 am #5471Please contact our Tech Support directly: https://miqobot.com/#support
October 14, 2017 at 1:43 am #5472October 14, 2017 at 2:04 pm #5473it happen to me as well thats a ingame bug it has nothing with bot to do :d all controller players cannot target this node until SE hopefully fix it
you need report this in SE forums as bug since you cannot autotarget it with a controller
- This reply was modified 7 years, 2 months ago by smaller.
October 15, 2017 at 4:27 pm #5487I’m starting to have the same problem myself
[EDIT] I can confirm it’s the same node as stated above (molybdenum ore), and that it simply cannot be targetted without a mouseclick
So if, like me, it was while using the aethersands scenario, i think we better put a wait timer instead of the startGathering(2) on that pair of nodes for now until it gets fixed. Gonna test this now
- This reply was modified 7 years, 2 months ago by Zatsh.
October 15, 2017 at 6:43 pm #5489We have investigated this issue closely, and we would like to inform you that Miqobot already has a built-in solution for cases like this: Gathering Nodes Blacklist.
It triggers automatically after 3 unsuccessful attempts to target a problematic node.
The only downside is that compass sense becomes unavailable, because Lay of the Land will keep pointing to the same node.All you have to do is add beacons to your grid, which will allow Miqobot to continue gathering without Lay of the Land. Additionally, you may instruct Miqobot to ignore this node by disconnecting it from waypoints altogether. This is achieved by setting a lower value for “max branch distance”.
Here is an example of grid that fixes this issue.
Attachments:
You must be logged in to view attached files.October 16, 2017 at 12:18 pm #5497this might sound silly, but I was having this same problem yesterday, and just now found that the key bind for “target nearest NPC or object” was unassigned, when it should be NUM0
and NUM0 is assigned to something else now, although still works as target npc when i press it manually =p
but any way, assigning “target nearest NPC or object” with a key has fixed the issue for me, just thought I’d shareOctober 16, 2017 at 3:37 pm #5498October 24, 2017 at 6:20 am #5540October 24, 2017 at 4:45 pm #5548October 25, 2017 at 2:44 pm #5551 -
AuthorPosts
You must be logged in to reply to this topic.