Forum Replies Created
-
Posts
-
Scenario updates are new functions.
Qol updates are stuff like pause, better ui, etc: https://miqobot.com/forum/forums/topic/planned-qol-updates/As in, no “full casting” of healing mode. In the sense that you would Divine Benison the person with the highest aggro (MT), you’d Regen them (because why not, it’s only 1 GCD), Tetra, Plenary Indulgence.
You can already do this by simply putting GCD heals on a single hotbar and telling Miqo to ignore it in advanced settings.
Gunbreaker has quite a few clicks per minute (dark knight as well). Often Miqo will fight you, trying to get in those off globals and such. So you’re hitting your A key and you stutter step, often not getting out of the AE that you would have cleared easily on another class.
You have a keybind collision somewhere. Like when Miqo pushes Alt-1 to trigger an icon and theres Alt-A somewhere else in your keybinds so when you hit A key it gets triggered too. I play gunbreaker quite a lot and theres no stutter stepping at all. I certainly had it in the past but i remember clearly that removing keybind collisions fixed it instantly.
There are quite a few squadron scenarios in the index: https://miqobot.com/forum/forums/topic/index-scenarios/#Trust
Just set it to run the dungeon you need and adjust the purchase key() sequence to match ventures.Scenario generator is not a part of Miqo. If you ask about the one made by Shishio then its basically an open source tool he created for the community. So you should probably post it in his thread.
As for Miqo itself there are functions like afkFor() and afkUntil() which you can use to arrive at the correct time. Im not sure if they are generated by Shishio as i havent used his tool.
Take a look here: https://miqobot.com/forum/forums/topic/request-new-levinstrike-aethersand-scenario/
People were posting different versions of their scenarios. Might need a little tweaking.Dont move your mouse during keystrokes or scenario will break.
An issue wherein Miqobot would fail to move a game cursor, under extensive mouse movement.
Unfortunately, this can not be fixed without code injections, and we have no plans for implementing code injections.
Miqobot is aware of this situation, and she will patiently wait for mouse to stop moving before making another attempt. She needs a small fraction of a second (about 0.25 sec) in order to recover from this issue. Under normal circumstances you wouldn’t even notice this behaviour.
If you want to prevent this behaviour completely, please consider switching the game to Windowed mode and minimizing it, when you run Miqobot in the background. Thus, mouse cursor will not be able to run over the game’s window and will not interfere.Reentering diadem is not supported by Miqo so the author made a custom workaround. Its weird he neglected to mention it.
My scenario is flexible. It lists all nodes within each mini route and i can easily toggle them on or off depending on what i need at the moment. It looks like this.
grid(Diadem1-8) waypoint(11) gather(1) waypoint(15) gather(1) waypoint(20) gather(1) ...The first chapter covers 8 nodes in total. The next chapter sets grid(Diadem9-16) and covers the next 8 nodes. And so on. Ive actually described this structure a while ago so ill just quote myself if you dont mind.
Well since diademBoom() is a scenario thing i think the best approach is to split the whole grid in separate chunks and work on them separately. When you enter Diadem theres one miner node spawned directly to the right. And it spawns the next 8 nodes in a chain. So you can start by mapping these 8 and restart Diadem. Then make a separate grid and start mapping from #9 which is also spawned on your immediate arrival. Then the third grid and so on. The whole Diadem can be split into six grids.
Grid 1: #1-#8
Grid 2: #9-#16
Grid 3: #17-#24
Grid 4: #25-#32
Grid 5: #33-#40
Grid 6: #41-#48Im using the old botanist map for reference but the idea is the same: https://www.reddit.com/r/ffxiv/comments/fhb5be/advanced_guide_to_diadem_farming_map_of_all_nodes/
Once you finish a grid you make a separate chapter for it with diademBoom() in the end. It probably doesnt change much if your goal is a complete Diadem map. But it makes things easier to manage in my opinion.
So i have 6 chapters with 8 nodes each. Its basically the same as farming unspoileds but without afkUntil(). No compass and no beacons needed. Miqo just follows my grid and farms it exactly how i want. Easy and fast.
