[nyancatParticipant]

Ai also means love in many Asian languages. :p
<3

[nyancatParticipant]

Hey I randomly decided to check back in here after months and saw this.

I have zero complaints about Miqobot. Miqobot features are thoughtfully designed for a good user experience. It appears they’ve intentionally taken on the burden of automating complicated tasks so all the user is presented with is a single button.

Combat. You just select a dungeon, hit start, and off it goes. Compare this with competing bots that offload all that complexity to the users by exposing every minute option and having them create complex combat scenarios for every dungeon.

Crafting. The options here are sparse. Normally, you input how many items you want, hit start, and Miqobot takes care of the rest. You don’t really have to do any low-level setting tweaking.

Scenarios are primarily used to string together multiple high-level tasks like the above.

I assume this design approach is what might be contributing to the slower feature implementations that some users are lamenting about. I don’t mind it because the core features do work, they’re powerful, and the effective simplicity gives me peace of mind.

[nyancatParticipant]

Hey Trotski, will try to help clarify here.

In the navigation tab, try enabling “show on radar.” Miqo tries to navigate to the nearest waypoint (the colored squares). When you spawn at an aetheryte, it will be at a random point around the aetheryte. High quality navigation grids have a ring of waypoints around the aetheryte which are interconnected with lines. The lines commonly converge with a single fly/mount waypoint that leads a path to the gathering area.

For grids that don’t have this available, you can use the editor to manually add waypoints and connecting lines to that existing grid. Details are in the link Lyfox provided.

It might seem intimidating at first. Once I got used to it, I found it easy and intuitive.

[nyancatParticipant]

Hi snooch, taking a shot at your questions.

1. Yes. You can use the scenario feature which will run a series of steps for you. Food and potions are used by telling Miqobot which icons to press (ex. icon(5,12,3) translates to hotbar 5, button 12, wait 3 sec after). Then you can tell her to craft and then use repair() and materiaExtract() afterwards. See script example down below.

2. Also can be done via scenario. Don’t use any pre-5.4 ones since they’re outdated… I’ll update this post later when I can find the good scenario that can be imported. You basically tell it what to target, where to dismount, then how many times to execute boom. Also see script example down below.

3. Miqobot takes your stats into account to intelligently decide which is more preferable. That specific change in Miqo’s recent patch notes is more of an algorithm tweak I think (mods, please correct me if needed).

4. I personally use control syrup. For 4 star recipes, Miqobot’s initial steps are spamming rapid synth to get to within 1 step completion. CP syrup would help there but control syrup helps the more important control steps.

5. The last FFXIV patch broke Miqo’s collectible gathering and it’s still in progress on getting fixed. During prior FFXIV patch, it would work as part of a scenario by changing to a job and turning them in. Example below. I don’t think kupo of fortune is supported.

Example scenario chapter script:

job(CUL)
icon(5, 12, 3) // use food
icon(5, 11, 3) // use tea

solverPreset(hq)
nqhq(balanced)

// Chili Crab [Crafted] - CUL - Level 80
setCraftCollect(off)
job(CUL)
recipe(Chili Crab)
craft(10)

icon(5, 11, 3) // use tea

// Chili Crab [Crafted] - CUL - Level 80
setCraftCollect(off)
job(CUL)
recipe(Chili Crab)
craft(10)

repair()
materiaExtract()

repeatChapter(2)

Example diadem script:

boomTarget(Arch-Noctilae)
boomTarget(Cloudtrap)
boomTarget(Dryad)
boomTarget(Sapling)
boomTarget(Wood Golem)
boomTarget(Diadem Plantoid)

waypoint(426)
dismount()

diademBoom()
diademBoom()
diademBoom()

Example collectible turn in script:

goToWaypoint(12)
changeJob(Miner)
deliverCollectables()
changeJob(Botanist)
deliverCollectables()

• This reply was modified 3 years, 3 months ago by  nyancat.

[nyancatParticipant]

I’m in a similar situation as flamesbob.

Adding to his response… I mostly use her while I’m at my PC but alt-tabbed or during remote work. Most of the use is for a relatively short 30 min gather-craft scenario. Each mat gathered is for only 5-20 turns. Prior to the craft chapter, she teleports to and enters my locked estate.

When going to sleep and not using that scenario, I set limits so she’ll work for up to 30 min max to minimize the risk window.

Miqobot really frees up my time to take care of other things (work, family, other hobbies) while staying productive in-game. I can also enjoy the game more because the burnout grindy parts (gathering, crafting, alt job leveling, MGP farming) are smartly automated at the press of a button.

[nyancatParticipant]

Looks like we just got a New Years gift with a minor Miqobot update. 🙂

Back to topic… IMO the current roadmap looks well-prioritized. https://miqobot.com/forum/forums/topic/patch-notes/
I’m looking forward to when the existing features that were broken due to patch are reimplemented. Specifically collectable gathering.

Idea #5 with the cleanup on removing the default outdated gathering grids is a good point. It’s irrelevant for existing users. But these minor changes can help retain new users. A community-maintained wiki would help keep documentation up-to-date.

mrzepher67’s on point about combat and vendor interactions (maybe this is part of scenario engine updates?). Boss mechanics might be complicated though.

[nyancatParticipant]

Very insightful!! Thanks for the quick and detailed response. It’s definitely not practical given the solution sizes unless that RAM cache is significantly increased or adjustable… but then Miqobot wouldn’t be a relatively lightweight app anymore and that risks degrading the user experience. I’d rather have a lightweight app.

My specific issue might be related to minor stat changes from crafting job changes during the long scenario then. It would be a dream to have that all cached but the benefit isn’t worth the cost.

[nyancatParticipant]

I see what you mean now. I didn’t realize her existing fishing feature could pick up the macro icon. I don’t have to rely on a repeated scenario. Works perfectly! Thanks!!

[nyancatParticipant]

I use the Scenario Maker’s “Nb item per node” to conservatively approximate how many nodes to gather.

[Author]

Posts