Forum Replies Created
-
Posts
-
Alongside defaulting the keybinds or changing the scenario, keep in mind any scenario with
key()commands is fragile. It’s best to leave it running on the computer and go do something else. Alternatively, you could have the game client on a second monitor you won’t move your cursor to or, as a last resort, minimised. Any cursor movement over the game, even if the game is in the background of another window, runs the risk of breaking the sequence and scenario.Currently there is no way to call combat assist in a scenario.
If you are wanting Miqo to run instances she doesn’t have in the squadrons drop-down then you will need to manually make a navigation grid and have
key()commands to repeat attacks until things are dead. If you can time everything correctly you could even have Miqo move out of mechanics that are predictably timed.It’s a lot of work and probably a good portion of why it takes a long time to get a supported dungeon added.
If all you want is clusters then the easiest will be Mor Dhona which six nodes a day for any element you want. Aetherial reduction is still more yield than camping Mor Dhona.
Levin Mint and Thunder Rock actually have three spawn times each per day. The only issue with reduction now is that collectability is currently broken in Miqo because of the game update. You will either need to have a gather sequence with
key()in the scenario or gather preset macro, but there’s no guarantee you’ll get high collectability for good reductions.If you mean outdated by collectability being broken, Miqo needs to update or macro it.
You might likely need to take out some skills so even with both procs you won’t cap out and break the scenario. Figure out the minimum and maximum of what your stats can give you and adjust from there. You will run the risk of getting lower collectability for your minimum value but at least your max won’t cap and break the scenario. This is the unfortunate forced work-around until Miqo’s collectability is updated.
There are also plenty of people uploading new reduction scenarios, but iirc those are having to be manual because collectability is currently broken in Miqo with the new changes.
The scenario index and gather grid index have options.
Late getting back to this as I just started gathering again but yes Miqo does use cordials while gathering in scenarios. I just watched her do it. You just need the “use cordial” box check in the gathering preset, save, and the cordials on a hotbar. I remember it being done before as well so /shrug
TLDR Yes you can probably just import a Diadem scenario and it will basically handle everything you’re asking for.
1.) Does miqobot handle the reapplication of food, potions, and repair dark matter?
You will need to time the reapplication of food buffs, or deal with a little overlap or time missing the buff. Miqo does not yet automatically detect this.
repair()via darkmatter is supported.2.) While gathering in the diadem, how does miqobot utilize the aetheromatic auger? I have a preference in the targets I would like to shoot (ie miner only targets when I enter as a miner) and would like to avoid sprites entirely as they do not accumulate points.
Yes, Miqo can choose specific targets for
boomtarget().3.) I saw that the bot while crafting the expert recipes prefers using muscle memory as opposed to reflect. Due to my stats having higher relative craftsmanship to control of the “meta” melds I do not know if miqobot can account for something like this. Would this require some tinkering on my part?
Miqo does support expert recipes but I don’t have experience with 4* recipes yet. The solver will calculate the best possible outcome and go with that based on your stats. At the very worst if you don’t want her to use a skill take it off your hotbar, or macro it without /micon, as the “ignore hotbar” seems to be a combat-only thing.
4.) A second question on crafting, does the bot prefer cp syrup or control syrup?
Doesn’t matter, Miqo solver calculates based on your current stats, either when you start or when the buffs run out and she needs to recalculate.
5.) How does turning in items and kupo of fortune work.
Miqo handles
delivercollectables()turn in, but kupo tickets might need to be done withkey(). I don’t use diadem so I don’t know exactly. You might want to just import one of the many diadem scenarios and backwards engineer it from there.Basic scenario scripting information
Basic crafting information and crafting development
Diadem scenariosAlso keep in mind keybinds might be different. I always kept them to default so /shrug
I wrote my own for reassigning ventures. Just add some extra afk time at the beginning so when you start your scenario at your retainer chapter you have some time to get back into or away from the game and move away from your mouse. Once you have the sequence for resending one retainer from the common point of opening said retainer all you need to do is copy paste for each retainer with extra keys for down to go through all of them.
It all depends how you want to organise your scenario. You don’t need a scenario to gather an item. You can make a grid and a preset and just gather from the gather tab. However, if you’re wanting multiple items in different maps yes you will need a scenario to automate that travel. You also don’t need a chapter for each different item, but starting in the middle of a loop gets more annoying if not separated into chapters and it can start looking hectic especially when you need to go back and fix something.
You can find details including restrictions of all scenario functions with the
?button on the scenario tab. Reverse engineering a downloaded scenario and reading is IMO the best way to teach yourself how Miqo works to build what you really need.Miqo also has posts in the help forum for understanding the basics of her functions. They are old so some things have changed since then but the core premise is still true.
– https://miqobot.com/forum/forums/forum/help/
– https://miqobot.com/forum/forums/topic/beta-scenario-scripting-engine/
