Forum › Forums › Discussion › Revisit Gathering will likely break Miqobot
This topic contains 13 replies, has 8 voices, and was last updated by Miqobot 2 months, 1 week ago.
-
AuthorPosts
-
August 18, 2024 at 10:06 am #41378August 19, 2024 at 3:01 pm #41397August 19, 2024 at 7:06 pm #41399
I don’t use scenario but having gathering assist on and manually moving to nodes Miqo’s reaction to a reclaim proc is inconsistent, it sometimes will repeat the set rotation but other times it will just continue to hit ignoring the rotation.
by the text in Miqo itself it seems it just sees it as a new node.
it doesn’t break it is just not fully optimized in this situation as expected.Someone else would need to give feedback on how it reacts using scenario paths, its useful to actually have the infomation instead of just wording theories.
August 20, 2024 at 2:13 am #41402So far after testing a few gathering paths i’ve setup Revisit always breaks Miqo. Once it ‘finishes’ the node it acts like it wants to goto the next node and ignores the fact that Revisit triggered and the node window is still open. It doesn’t try to close the window. Only thing I can think of to by pass this is to create a scenario that gathers a node (1) time and repeats the gathering (x) number of times, always clearing any windows with (esc) after it finishes the node to clear out the Revisit trigger. I will play with it for a while to see how it goes.
August 20, 2024 at 2:27 am #41403So this simple scenario seems to bypass/fix the Revisit issue.
startGathering(1)
key(esc, 1)
repeatAll(300)Just set your gathering tab settings how you like and change the 300 in repeatAll to however many times you want it farm nodes. The esc,1 seems to clear the window fast enough and then miqo will reopen the node window and farm it. But more testing may be needed.
August 22, 2024 at 5:50 pm #41416So this simple scenario seems to bypass/fix the Revisit issue.
startGathering(1)
key(esc, 1)
repeatAll(300)Just set your gathering tab settings how you like and change the 300 in repeatAll to however many times you want it farm nodes. The esc,1 seems to clear the window fast enough and then miqo will reopen the node window and farm it. But more testing may be needed.
this sometimes works, but every 3-4 revisits it crashes the Miqo. i’ve tried with other number values but with same result. anyone know any other working solution?
August 23, 2024 at 3:35 am #41417August 23, 2024 at 6:11 am #41418August 23, 2024 at 3:34 pm #41419Looking at my gathering preset for Magnesia powder:
I have:
– a good grid that doesn’t get miqo stuck, I assume you as well
– specified gathering node: “Rocky Outcrop”
– specifies slot: 1
– count: used 150/70/60/30 all completed with no problems
– senses: use compass I/II
– simple rotation: +2 Yield skill
– gather by name: Magnesia Powder (might be redundant)nothing breaks, I believe it’s because of the senses options
August 23, 2024 at 3:36 pm #41422August 23, 2024 at 8:50 pm #41427can you share your gathering path that’s brakes miqo?
https://miqobot.com/forum/wp-content/uploads/2021/12/Lv90MIN-E-PoietenOikos-AmbrosialWater.Annite.RawBlueZircon.txt
https://miqobot.com/forum/wp-content/uploads/2019/07/BTN-80-Lakeland-Harvesting.txtambriosal water & light gerbera. the thing is i used both with same settings before 7.0 and everything was excelent, now after update it crashes after few revisits. someties after 15 minutes, sometimes after 2h, but it breaks every time. kill switch triggers and my character just stand there until logged out cause of afk.
August 23, 2024 at 11:51 pm #41429I ran your ambrosial water grid.
No problems so far, but I have my three suspicions (in order of how difficult it is to solve)
1. you do not have compass skill on your hotbar – just to make sure lol
2. Your grid is clunky, you might be causing the bot to bug out simply because of how the grid is set up. I have a suspicion it has something to do with beacons + revisit interactionMy quick take on how to make a grid:
a. Don’t use beacons
b. Move by foot between close gathering nodes
c. Use compass to determine where to go next – makes the marker order placement more tidy and it will mimic the way miqo wants to move when using the gathering preset (it uses compass to find the next nearest gathering node)
d. Make additional connections that promote a unidirectional movement3. Scenario script is clunky – probably can be solved with a better preset
- This reply was modified 2 months, 1 week ago by Dukuo.
August 24, 2024 at 12:12 am #41431this is a grid I quickly put together.
It’s not the best, I watched it for 3 cycles and made some adjustments, but more could be made
Miqo targets the closest node she sensed which is a little off from what I want her to do.
Had one revisit:I sense something far away (-291, -228). I want to go take a look!
(8:07:05 PM) Going from 25 to 33 in 5 trips.
(8:07:11 PM) 4 trips more..
(8:07:15 PM) 3 trips more..
(8:07:16 PM) 2 trips more..
(8:07:18 PM) 1 trip more..
(8:07:18 PM) Destination reached!
(8:07:18 PM) Scanning for shiny gathering nodes like ‘Rocky Outcrop’ *.*
(8:07:18 PM) I see a shiny node at (-291.209290, -228.924393, 136.404694).
(8:07:18 PM) Going from 33 to 33 in 1 trips.
(8:07:18 PM) 1 trip more..
(8:07:18 PM) Destination reached!
(8:07:20 PM) Using action: (Start)
(8:07:20 PM) Hitting that poor node. :3
(8:07:29 PM) Hitting that poor node. :3
(8:07:32 PM) My precious shiny sparkles! (3/150)
(8:07:32 PM) Scanning for shiny gathering nodes like ‘Rocky Outcrop’ *.*
(8:07:32 PM) I see a shiny node at (-291.209290, -228.924393, 136.404694).
(8:07:33 PM) Going from 33 to 33 in 1 trips.
(8:07:33 PM) 1 trip more..
(8:07:33 PM) Destination reached!
(8:07:36 PM) Using action: (Start)
(8:07:36 PM) Hitting that poor node. :3
(8:07:44 PM) Hitting that poor node. :3
(8:07:48 PM) My precious shiny sparkles! (4/150)
(8:07:48 PM) Scanning for shiny gathering nodes like ‘Rocky Outcrop’ *.*Attachments:
You must be logged in to view attached files.August 24, 2024 at 7:51 am #41440Revisit issue has been addressed in Miqobot v1.3.51.1.
-
AuthorPosts
You must be logged in to reply to this topic.