[MiqobotKeymaster]

Yes, these features are already planned for implementation.
They will be a part of the upcoming Scenario Engine updates:

Upcoming Features

Thank you for your request.

[MiqobotKeymaster]

Thank you for reporting.
We have managed to reproduce your issue based on this description.

Indeed, there is a bug that prevents certain Summoner abilities from being triggered under these conditions. Your assumption is correct. The algorithm of SMN rotation identifies Aetherpact as ready for activation and prioritizes it before everything else.
Unfortunately this issue does not have an easy fix, because the logic is rooted deeply in the rotation algorithm. At the moment Summoner oGCD abilities are not compatible with Ignore Hotbar feature.

We will reimplement the algorithm in the next version.
Until then there are only two workarounds:

1. Hide Aetherpact behind a macro with a different icon. In this case you will not be able to see the coooldown.
2. Place Aetherpact on a Cross Hotbar. In this case you will be able to see the cooldown, but there will be additional transparent artifacts on the screen from Cross Hotbar itself.

We apologize for inconvenience.

[MiqobotKeymaster]

Of course, our development plans are driven by the community demand.
If the majority of users supports your suggestion, we can start working on it.

Please create a new thread and we will discuss it.

Here are examples of the previous community voting threads:
– Level 80 Trust Dungeon
– 61 Dungeon Support

[MiqobotKeymaster]

grindeall wrote:

Your bot is popular and this plays a role in this, judge for yourself the interval between resources 2h et, i.e. 0: 01, 0:02… total 120, and when the resource is collected by 130 people, there is already an overlap.

Thank you for your high opinion of our product.
But unfortunately this is not true, Miqobot is not as popular. According to the data from our logging system, there are simply not enough simultaneously running Miqobot accounts to create a problem of this kind.

grindeall wrote:

There is no such bullying in this game, but simple tools like RandomAfkFor (6:00et/0:10) should be, chaos is needed, people are not perfect.

grindeall wrote:

I doubt that for the sake of a random time delay, you will need to change all the development plans, this is only 1 command.

All right, if a single scenario function will resolve this issue, then it’s not a problem indeed. It will be implemented it in the next version.
Thank you for your request!

[MiqobotKeymaster]

Would you please clarify your request?
Do you ask us to postpone all other feature packs and rearrange the development plans in favor of Scenario Engine updates?

We can do this, of course, if this is what community requires most of all.
But we need a little bit of constructive feedback to make this adjustment.

[MiqobotKeymaster]

Our server sends the license code to you automatically after purchase. Please make sure that it doesn’t end up in your Spam or Junk folders.
And of course, our Tech Support can easily resend it to you.

Please contact us directly and we will help you: https://miqobot.com/#support

[MiqobotKeymaster]

According to your screenshot, your settings for Gather by Name are effectively blocking the rotation.

Using curly braces {} in Gather by Name prevents spending GP on anything other than items inside the braces. If your intent is to use rotation on all possible items, please remove curly braces {} from items in the list.

You can find more information in the Help section: Gathering – Gather by Name

[MiqobotKeymaster]

This issue usually indicates that you haven’t removed keybind conflicts from chat actions.
You can find instructions on how to avoid this problem in the [Beta] Combat thread.

Miqobot wrote:

Important Note!
Please remove any keybinds from “Reply” and “Switch Chat” actions.

If you use the common WASD style for navigation, there’s a very high chance that a keybind collision will occur if Miqobot sends key input at the same time.
For example, if you assign Alt+1 – Alt+= to a hotbar Miqobot uses at the moment and press S at the same time, the resulting keybind will become Alt+S which by default triggers “Temporarily Switch Chat Mode to Say”. This will activate the chat mode in the middle of the fight and break your movement completely.
In order to avoid this problem, we recommend to fully clear the Keybind -> Chat tab.

(You can leave the first two actions intact: “Ready Chat Log” and “Ready Text Command”.
Assuming they contain no Ctrl / Alt / Shift modifiers.)

In addition, please make sure that “Keybind” -> “Enable direct chat” setting is disabled.

If this information doesn’t help, please contact our Tech Support for further investigation:
https://miqobot.com/#support

[MiqobotKeymaster]

iNight wrote:

Does WHM really performs better now since miqo only use it on tank? I agree that spamming regen is bad, but now she’s often spamming cure instead, which in my opinion is worse because of casting time and can’t heal people while moving.

This adjustment was specifically requested by the community:
Quick Question about WHM Regen
WHM Regen (feedback)
If you believe it is not an improvement, please join the discussion and voice your opinion.

iNight wrote:

For SCH and AST, in full party it will cast shield outside battle. Can you disable it and make it like how she behave in light party? It’s a bit bot-like and I prefer to cast it manually outside battle but still let miqo use it on battle. I don’t want to disable the heal and buff option.

All right, we will see what we can do.
However, this is not the only thing that Miqobot will do if you leave Assist Mode active. If you don’t wish Miqobot to perform outside battle, please use a hotkey and disable Assist Mode when you don’t need it. It was not designed to be active at all times.

iNight wrote:

And for AST, is it possible to use diurnal sect instead of nocturnal as default?

Of course, but we have to understand the reason behind this adjustment first.

iNight wrote:

As for miqo being slow, I found that she’s slow when using r51093’s Diadem stuff a few weeks ago. It became normal after I removed it, not sure why.

Yes, large navigation presets may indeed cause performance issues.
That’s why we recommend splitting grids into smaller chunks and combine them via Scenario Engine where possible.

[MiqobotKeymaster]

Thank you for providing the requested information.

This issue usually indicates that there is a third-party application interfering with Miqobot application.
Miqobot algorithms work exactly the same way as before. It happens with new versions when your antivirus or firewall prevents Miqobot from performing normally by constantly interrupting and verifying each action that Miqobot is trying to take.

Please follow the guidelines described in the main status thread:

Miqobot wrote:

A reminder about antiviruses.

Since this is a new version of Miqobot, it may be flagged by your antivirus as False Positive because its signatute is not yet known. As it is stated in our FAQ section, Miqobot is not a virus but antiviruses are usually trained to sic at anything that tries to interact with other programs. Miqobot will make no attempt to fight your antivirus.

Please remember to whitelist your Miqobot application after download. Thank you!

[MiqobotKeymaster]

Random wrote:

Is it just me or is Miqobot executing skills slower?

Would you please clarify, what skills exactly are being executed slower and what do you compare it to? Does it happen during gathering or crafting?

SirVG wrote:

Thank you for your hard work, Miqobot team. 🙂

eve wrote:

Wanted to hop in real quick and thank the devs for their hardwork. Having Miqobot has made crafting and gathering significantly easier (I craft for 2 statics) and reduced my workload. <3

Thank you for your feedback very much.

Talith wrote:

I’ve been running miqo on some expert crafts and a couple of times she’s gotten stuck on reflect (she tries to use it not on the first step and gets stuck spamming it). Hasn’t been a huge issue as I can just remove it from my bars for those crafts but I did want to notify you guys as I’m running 1.3.42 and I know it was an issue that was fixed in a previous patch but it appears broken again.

Thank you for reporting.
Yes, a similar issue was fixed in the past, but it doesn’t mean there are no bugs left.

Just like before, we need to know the exact sequence of steps that led to this moment in order to analyze it.
Would you please enable logs under Crafting Solver settings? This will generate two files next to Miqobot application: miqo_crafting.log and miqo_crafting_solver.log. Please put them both in ZIP or RAR archive and attach here or send to our Tech Support email. Our developers have the necessary tools to analyze the log files, so they will be able to find the matching log entries.

M0ist wrote:

Webroot folks, miqobot for some reason this version, is highly disliked by webroot haha. Make sure to whitelist asap (if you’re willing to trust it *i do*) otherwise webroot will make it very difficult to reach whitelist without completely disabling after a couple removals. This is the only version so far that it’s attacked miqo so harshly, so not sure what’s changed so drastically here.

There have been no significant changes besides those described in the Patch Notes.
Unfortunately we haven’t yet encountered an antivirus that would not trigger a False Positive while analyzing Miqobot. Even if there was no problem before, it creates one sooner or later. So even if you did not experience this issue in the past, it doesn’t mean that you never will.

We always inform antivirus vendors about false positives, and Miqobot project is also subscribed to premium VirusTotal services that send automatic notifications to them.
Indeed, the current version of Webroot has problems with Miqoradar application:
https://www.virustotal.com/gui/file/f9db51722906c4b753c72ff02cee5ddbe4800ab43240cac7a4b3a806fa8454e8/detection
Since it has been detected by VirusTotal installation, they will receive a notification. However, we don’t know how long it will take them to fix it. We would recommend to report this behavior to your antivirus vendor as well, as it might help them to address the issue faster.

[MiqobotKeymaster]

This issue usually indicates that your antivirus has interfered with Miqobot application and terminated it.
Miqobot does not contain any algorithms that would close the application without user consent. And if there is a crash, she always displays an error message before closing. If the application simply shuts down, it means there was no crash, and this problem can only be caused by third party interference.

Please make sure that you have whitelisted all Miqobot files in your antivirus.
If it still doesn’t help, then there could be another security application installed. You can use a special tool called Process Monitor to identify what applications are interacting with Miqobot.

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

Process Monitor helped one of our users in the past. He managed to discover an unwanted antivirus installation on his PC which was causing problems, so it might help you as well.
Please read the following thread for more information and for instructions on how to use it: Slight Problem

[MiqobotKeymaster]

(Floors 21-30) Heaven-on-High Solo takes more than 30 minutes to accomplish and has a varying wipe rate of around 5-40%, depending on aetherpool levels.

We have calculated the average time it would take to level a single job from 60 to 70.
This data includes Armoury Bonus (+100%) and Aetheryte Earring (+30%).
Rested EXP is not included.

- (Lv53) Sohm Al:                23.2 hours
- (Lv57) The Vault:              22.4 hours
- (Lv60) Pharos Sirius (Hard):   34.0 hours
- (Floors 21-30) Heaven-on-High: 20.2 hours

As you can see, Heaven-on-High is indeed faster for leveling, though only by 15%.
And of course, it is planned for implementation in the future. But it will not change a lot.

If you do not mind playing manually at least 20 minutes per day, we would recommend to complete Duty Roulette: Leveling to boost the process. With Assist Mode, Miqobot can help you alleviate the stress of repetitive gameplay.
If you are looking for purely automatic methods of leveling, then (Lv53) Sohm Al is the best solution we can offer at the moment.

[MiqobotKeymaster]

Green wrote:

i keep having issues with a message that keeps popping up about antivirus and firewalls and corrupted files and i cant not figure out the problem. i have cleared all i can find and downloaded new miqobot but still is not working , help me please

Our Tech Support has replied to you by email with detailed instructions.
Please check your inbox and let us know if you require additional assistance.

r51093 wrote:

anyways i came to say thank you miqobot for adding in the waypointPrecise() feature i greatly appreciate it 😀

Thank you for your feedback very much.

Nucode wrote:

I’m having a problem with the new collectable gathering. I’m using the 1000 collectability preset. It will stop working if there isn’t enough gp and it gives this error:

(1:17:38 PM) Not enough GP for this rotation: 339 of 400 required.
(1:17:38 PM) Hitting that poor node. :3
(1:17:39 PM) Hey, I can't collect with 0 rarity :/

It then just sits there at the collectable interface and stops working

Yes, this is the correct behavior.
If you don’t have enough GP for 1000 collectability, Miqobot will make no assumptions about how much collectability is acceptable. While we could implement a default Scour hit to prevent getting stuck at 0 value, this decision may result in cluttering your inventory with useless 200 collectability items.

If you wish to collect items regardless of collectability, please select a rotation that requires 0 GP.
If you wish Miqobot to choose a rotation automatically based on current GP, please use rotationIfGP() function. Here is an example:

rotationIfGP(1000 Collectability)
rotationIfGP(Ephemeral 0GP)
gather()

[MiqobotKeymaster]

Powerful Hookset is used under the following conditions:

• “Powerful Hook” setting is enabled.
• Tug animation is either medium or large.
• If tug animation is large, “Inverse Hook” setting is not enabled.
• Patience buff is active.
• There is enough GP.
• Powerful Hookset icon is on hotbar.
• Powerful Hookset icon is reachable by keyboard.

If this information doesn’t help, please contact our Tech Support and we will do our best to help you:
https://miqobot.com/#support

[Author]

Posts