[MiqobotKeymaster]

In order to use Miqobot, you have to start the game in DirectX 11 mode.
Please follow these steps:

1. Exit the game, if it is running.
2. Start the Final Fantasy XIV Launcher.
3. In the bottom of the Launcher, press Config.
4. Toggle the DirectX 11 switch to On.

It should look like this:

After that, login and start the game as usual.

[MiqobotKeymaster]

Thank you for informing us that you’ve managed to identify the first part of your issue.

Pain wrote:

*Note: removed timestamps because i am paranoid they can be used to identify me.

We are very sorry, but timestamps are a vital part of the message log. Without them we can not analyze the time periods it took Miqobot to perform certain tasks.

We would recommend to contact our Tech Support directly: https://miqobot.com/#support
Email support is completely private and confidential.

For now, we can only give general recommendations that might or might not help you, because we can not fully investigate the problem.
Please try the following solutions:

1. Do you move the mouse cursor when this issue occurs?
   If so, then please try to let it stay still for 10-15 seconds. Mouse cursor interferes with the ingame keyboard evaluation module and prevents Miqobot from aiming correctly. If it helps, then please consider switching the game to Windowed mode and minimizing it.
   This issue is described in our basic tutorial on Minigames:

   Miqobot wrote:

   Also, if you are going to move your mouse in the foreground (for example scrolling through browser), we recommend that you switch Screen Mode to Windowed and minimize your game window.

   Otherwise your mouse cursor will interfere, and Miqobot will not be able to push the minigame button. Unfortunately, there is nothing that can be done to prevent this behaviour on our side, except for code injections (and we have no plans for implementing code injections).

2. What FPS do you run the game at?
   To get consistent results in Minigames we recommend having at least 60 FPS. At lower FPS, it is much harder for Miqobot to aim, and at certain marker speeds she might not be able to align the marker at all which may seem like she stopped playing.
   This issue is also described in the tutorial on Minigames:

   Miqobot wrote:

   Minigames AI utilizes a special aiming algorithm, which relies heavily on your ingame FPS.
   It tracks the marker movement and predicts its position at the next frame in order to detect the best moment to push the button. In other words, Miqobot aims very much like a human player does.
   So the lower your FPS is – the harder it is to aim.

   To get consistent results we recommend having at least 60 FPS. Miqobot can perform at lower FPS, but your win rate will decrease.

You can read the full tutorial on Minion Square Minigames here: Miqobot v1.2.45 – Patch Notes

If neither of the above solutions helped, then please contact our Tech Support directly: https://miqobot.com/#support
Thank you very much!

[MiqobotKeymaster]

Thank you for informing us that you’ve managed to resolve your issue!
If you encounter any other problems, don’t hesitate to let us know 🙂

Please note that you can also contact our Tech Support via website: https://miqobot.com/#support

We might not be able to provide support on forums in a timely manner, but Tech Support inbox is monitored regularly.

[MiqobotKeymaster]

Thank you for reporting!
We have tried to reproduce your issue in our labs, but unfortunately we couldn’t identify the problem.
Would you please give us more information?

1. Please show us the complete message log from the Output Area. (Starting from “Hello! I am your Miqobot!”.)
2. What exactly doesn’t function properly in “Out on a Limb” minigame after the issue occurs?

Thank you for your assistance very much!

[MiqobotKeymaster]

Thank you for reporting!

We have tried to reproduce your issue in our labs, but we couldn’t identify the problem.
Would you please give us more information?

1. What settings have you enabled on 3D Radar tab?
2. What value is “Max branch distance” set to?
3. Could you please show us a screenshot of Miqobot settings and 3D Radar in the game?
   You can disable ingame UI to hide personal information as it’s not required.

“Show possible branches” is a simple algorithm which calculates distances between grid waypoints and game world objects currently displayed on 3D Radar. It hasn’t been changed in the past year, so the issue must have been present before.
However, this is the first time we received a report about this feature, so we would kindly ask you to provide as much information as possible.

Thank you for your assistance very much!

[MiqobotKeymaster]

When the game launcher installs a new patch, it has to be elevated into the Administrator mode.
If you do not restart the game launcher after that, the game will be launched in the Administrator mode as well. It occurs on every patch installation.

If you wish to avoid this issue, you can simply restart the game.

[MiqobotKeymaster]

Miqobot is fixed for Patch 4.5 Maintenance!

Please restart your Miqobot and she will update automatically.
Thank you very much!

[MiqobotKeymaster]

We are already fixing Miqobot for Patch 4.5 Maintenance.
The changes are minor and should only take a few hours.

Thank you for your patience very much!

[MiqobotKeymaster]

Yes, it would be possible.
However, Miqobot makes approximately 20 decisions per second, so displaying them in the message log would probably make it extremely cluttered and not very comfortable to read.

In addition, as @Nott mentioned correctly, there are several other options:

1. You can take notice of the icons highlighting on the hotbar.
2. You can setup the ingame battle log to display abilities used by your character and filter out irrelevant information.
3. There are third-party tools that can analyze the ingame battle log for you and display this information in any form via plugins which you can customize to your liking.

We haven’t found a better way to do this with Miqobot, but if you have a good idea, we are open to suggestions 🙂
Thank you for your request!

[MiqobotKeymaster]

Yes, Foe Requiem caused a lot of harm by pulling mosnters from inaccessible areas and potentially causing a logic deadlock.
You can read about it in the thread linked by @kontu.

Of course, it will be reimplemented for endgame raids. When we start working on raids optimization, we will create a special UI that will allow you to customize every ability in accordance to raid phases and party synergy, including Foe Requiem.

In the meantime, you can use it manually whenever you like by pressing it a few milliseconds before Miqobot makes the next decision. Your choice of GCD will not be overwritten.

[MiqobotKeymaster]

Yes, Quick Synthesis usage is planned in the future updates.
However, please note that Scenario Engine already has an alternative:

solverPreset(fastest)
ignoreQuality(on)
craft(max)

This will make Miqobot synthesize an item of your choice as fast as possible.
It’s not as fast as Quick Synthesis, but it has several advantages:

1. Crafting Solver is not limited in count. (Quick Synthesis is limited by 99 crafts.)
2. Crafting Solver can synthesize any recipe. (Quick Synthesis is not allowed for certain master book recipes.)
3. Crafting Solver can synthesize reliably with minimum stat requirements. (Quick Synthesis has a fail rate which depends on your average item level.)

So if you don’t mind the extra time spent, we recommend using this method instead.
Thank you for your request!

[MiqobotKeymaster]

Yes, this is exactly what happens when Miqobot detects malicious activity. She simply destroys several vital modules in the source code and game connection becomes impossible.

We have several trial accounts which we use during testing phases to verify performance on different levels.
But thank you for your suggestion very much!

[MiqobotKeymaster]

There is no technical difference between a trial and normal FFXIV clients that we know of.
Miqobot should perform correctly on both versions.

However, we can see that you’ve been trying to crack Miqobot for the past week, which is probably the reason why it is not working. Our server does not tolerate attempts to abuse the licensing system very well.

We are pleased to know that Miqobot project is interesting enough to motivate somebody to go this far, but we would kindly ask you to avoid such behavior. Investigating malicious user activity takes time and affects the development of new features.

Univ893473492325 wrote:

Here is a possible Solution for this:
Add a Option to decide which saved Waypoint will be used depending on the next two or more incoming Items and your current place.

This is a nice suggestion. We will definitely look into it when we start working on Chocobo Racing improvements.
Thank you for your request!

Univ893473492325 wrote:

Btw, is the Chocobo Racing Bot using the Duty Finder or do i need to stand near the Chocobo NPC?

Yes, Miqobot uses the Duty Finder to enter Chocobo Races.

[MiqobotKeymaster]

Raritea wrote:

Not sure if this has been addressed before but in the scenario scripting if you were to set it to afk till say 3:00et it will only work for 3am and not 3pm, I’m trying to set up to gather nodes that spawn every 12 in game hours but I can’t seem to figure out how?

Miqobot uses 24-hour clock format. An example of 3:00 p.m. would be:

afkUntil(15:00et)

Please note that full documentation is available directly in Miqobot. Press ? button to open it.

[MiqobotKeymaster]

SefirosuKuraudo wrote:

So I don’t know if it’s the same for everybody, but I’m finding that Miqo will not use Dark Arts during a DRK rotation, despite it being a Lv.45 skill, and so a Lv.50 rotation would still make use of it.

Thank you for reporting!
We have identified the bug that prevented Miqobot from using Dark Arts. It will be fixed in the next beta version.

mreleanor wrote:

Any ETA on any of these next features?

There is no ETA, but we will try to implement and release as many features as possible until the Shadowbringers expansion.
We are making incremental upgrades, so please keep an eye on this thread.

mreleanor wrote:

Would really love a focus on a new squadron dungeon above level 50, a full 70 rotation for every class on Assist Mode, PoTD or HoH integration/automation, Eureka automated farming or Custom fights added.

Yes, this is pretty much our priority list.
First we have to release adjustments and hotfixes for Assist Mode based on the feedback we received from our users. And then we will continue making incremental updates until all planned features are implemented.

infuriated wrote:

I believe the focus is on combat system at the moment due to high demand, personally i would like to see some classes have a full level 70 rotation with the next squadron dungeon release, however if the Rotations Customization comes first i would be very happy.

We are sorry to disappoint, but Rotations Customization is planned after we complete level 70 support.
The source code is currently undergoing constant modifications and implementing UI bindings at this stage would impose additional strain and significantly slow down the development process.

[Author]

Posts