[LyfoxParticipant]

If youre looking for a solo way in a private instance then yes: https://miqobot.com/forum/forums/topic/would-love-to-see-level-57-60-dungeons-in-the-squadrons/
Running 61+ dungeons in duty finder is faster of course but theres no squadrons there.

[LyfoxParticipant]

Just delete the lines with desynth().

[LyfoxParticipant]

Its just the way the author created the navigation grid for that scenario. Theres no easy way to fix it besides making your own navigation grid. I agree with you it doesnt look very natural but it seems like most people dont really care.

[LyfoxParticipant]

Yea just open the recipe on Armorer job page and dont use search.

[LyfoxParticipant]

Flying is a property of the navigation grid youre using. Does your grid have ‘fly’ waypoints in it? Or is it made with ‘foot’ points only?

[LyfoxParticipant]

Yea you can unclick solver and just type the sequence of keys in the macro box. Just disable Solver > Use and youre good to go.

[LyfoxParticipant]

Its something that they plan to do in scenario update.

[LyfoxParticipant]

If you copy Miqo to a different folder she will regenerate all presets as in clean install. From there you can review the rotations you deleted to see what skills they use. Or you can just export them and then import to your main Miqo.

[LyfoxParticipant]

Miqo always selects the closest NPC regardless of their name or camera angle. Targeting NPC by name is not supported atm. You can use waypointPrecise() to step closer to the barracks. Or you can insert holdKey(w, 0.4) before teleportNpc(). Should be enough to push your character closer to entrance.

[LyfoxParticipant]

Looks like youre using a cross hotbar. Miqo doesnt know how to work with that she needs a normal hotbar with keyboard shortcuts.

[LyfoxParticipant]

Do you have a cast icon on hotbar and keybind assigned? Could you show a screenshot of your hotbar?

[LyfoxParticipant]

Try entering the dungeon name as it appears in Miqo. Like dungeon(Garuda Extreme).

[LyfoxParticipant]

Miqo doesnt have a feature to count your items directly but you can calculate the number of nodes to gather and use it as count. Take the number of items you need divide by 4 then round up. If you need 10 copper ore then tell Miqo to gather 3 nodes: gather(3)

[LyfoxParticipant]

Ah i see. Then its probably because its not being registered without holding. Some actions must be held for at least one frame to trigger and sendKey() doesnt do any holding. Try holdKey() instead: holdKey(num4, 0.2)

[LyfoxParticipant]

From Miqo documentation:

Function does not explicitly detect scrip limits. However after 4 ingame errors are displayed, function will stop and break scenario flow. If you want to continue delivery regardless of scrip limits, specify “ERR_IGNORE” as parameter.

So in your case it should be deliverCollectables(ERR_IGNORE)

Yuki wrote:

Also for buying step of a scenario, just using key sends right now, but it feels so buggy, sometimes it works fine. Sometime it goes to wrong item, it is just all over the place. I think it has something to do with cursor awakening or not from what I read, but even when I do not touch anything at all it will do different things with the same step and key input. So idea is there a good way to bypass this issue.

This is one of the things that Miqo team is planning to fix in scenario update. Basically any sendKey() sequence is guaranteed to be unstable because there is no feedback loop to correct mistakes on the fly. Thats why new scenario functions made by devs are so much better. They have a feedback loop and so they are very stable. Until then the best solution is to buy items by hand. You have to do it only once in 2-3 hours so its not so bad. And besides its not a good idea to keep Miqo running all day without supervision. So if you check up on her anyway why not handle the buying step along the way.

[Author]

Posts