[MiqobotKeymaster]

Curly braces {} in Gather by Name force Miqobot to apply gathering rotations to this and this item only. If there’s no specified item or you don’t have enough GP for a rotation, Miqobot skips it completely.

It was implemented this way in anticipation of Collectable rotations.
For example, with Eventide Jade you are interested only in collectable version of this item since it has no use otherwise. So while your GP is regenerating, it’s best to skip Eventide Jade and collect Crystals or maybe some hidden item instead.

Since you’ve enabled Blessed Harvest 2, Miqobot will collect Dark Chestnut only when you have at least 500 GP. If you have less, she will skip it.
In order to collect the same item with and without a rotation, you should specify it twice:

{[dark chestnut]}
[dark chestnut]
crystal

[MiqobotKeymaster]

chapolincolorado wrote:

I’ve been farming unspoilded nodes and I noticed that sometimes miqobot doesn’t move and stays still. Ît scans the area every 5min and the hour in the game is only -+2 min (real life time)… Then, That’s why sometimes it misses farming properly. Any solutions?

Miqobot scans the area around you 10 times per second 🙂
It’s only the text message that is printed once every 5 minutes – to avoid cluttering the Output Area.

As @optiblast and @ai noted correctly, Miqobot detects gathering nodes which are within the ingame visibility radius.
Positioning your beacon in the center is one option, but sometimes it’s not possible due to nodes located too far from each other. In this case, we recommend to enable use truth option, which will allow Miqobot to utilize Truth of Forests / Truth of Mountains abilities.

Navigation grid for Dravanian Mistletoe and Porcini has been added to the Index.
Thank you very much 🙂

[MiqobotKeymaster]

No exact ETA yet, but rest assured that it’s one our top priorities.

Since Palace of the Dead has very little variety, it becomes a perfect task for Miqobot.
Grinding always makes her happy 🙂

We are planning to release Palace support in the next version of Miqobot (as the current one is already technically overloaded and long overdue).

[MiqobotKeymaster]

New Unspoiled and Legendary grids!
It’s great, thank you very much 🙂

[MiqobotKeymaster]

We have сonducted an extended investigation regarding your issue.
A second diagnostics build of Miqobot has been sent to you by email.

Unfortunately, we haven’t found a 100% solution to your problem.
Instead, we would like to offer you an alternative implementation of 3D Radar and we would like to know your opinion about this.

In this build, Miqobot makes 3D Radar to behave as ‘Always On Top’ window.
This method prevents problems which usually arise when working with overlay windows.
But at the same time it may not be very comfortable to use, because 3D Radar will be shown on top of your browser and other programs when running Miqobot in background.

In order to hide 3D Radar artefacts, you can do one of the following:

• Disable all Radar options as described in previous post.
• Switch the game to Windowed mode and minimize it completely.

When you try it out, please answer these questions:

1. Does ingame cursor work properly now with Razer mouse and 3D Radar enabled?
2. Does this new behaviour of 3D Radar make it very uncomfortable to use?
3. Which solution would you prefer: using this diagnostics build or keeping your Dell mouse plugged in?

Thank you very much!

[MiqobotKeymaster]

It’s great!
Thank you very much, your grid is added to the index 🙂

[MiqobotKeymaster]

We have sent you a diagnostics build by email.
Could you please try it out and check whether the ingame cursor works properly when using your Razer mouse?

Please follow these steps:

1. Unplug your Dell mouse.
2. Start Miqobot v1.2.47 – Diagnostics: Razer Cursor.
3. On 3D Radar tab:
   – select ‘Show’ -> Nothing
   – disable ‘Show FATEs’ -> List
   – disable ‘Show FATEs’ -> World
4. On Navigation tab:
   – disable ‘Show on Radar’
5. On Gold Saucer tab (under Racing):
   – disable ‘Show’ -> Rails
   – disable ‘Show’ -> Mid-rail
   – disable ‘Show’ -> Progress
   – disable ‘Show’ -> Waypoints
6. Switch to the game and try rotating camera.

Does ingame cursor work properly now?

In normal build of Miqobot, 3D Radar usually goes into dormant state (when all of the above options disabled).
In diagnostics build of Miqobot, we have changed its behaviour and now it is turned off completely.
Without an overlay window on top of the game your cursor should behave the same way as usual.

This is of course not a complete solution to your problem, as without 3D Radar you won’t be able to use 3D Editor.
But first we have to confirm that 3D Radar is indeed the root of conflict with your Razer mouse.
And we will be able to continue working on alternative solutions based on the results of this experiment.

Thank you for your assistance!

[MiqobotKeymaster]

Thank you very much for diligent answers to all our questions and for testing all cases 🙂
We now have enough information to create a diagnostics build of Miqobot for you.

It is great that you found a temporary fix by plugging in a second mouse.
We will still try to fix the issue programmatically, so you won’t have to worry about it anymore. But please keep your Dell mouse plugged for now 🙂

Oue developers will prepare a diagnostics build which should be ready by tomorrow.
Thank you very much!

[MiqobotKeymaster]

Understood.

We couldn’t reproduce your issue in our labs as it seems to be caused by specific mouse hardware in your possession, which unfortunately is not available to us at the moment.
But we will still try to help.

Please follow these steps:

1. With Miqobot active:
   – Switch the game to Windowed mode. Does cursor work as expected?
   – Switch the game to Borderless Windowed mode. Does cursor work as expected?
   – Switch the game to Fullscreen mode. Does cursor work as expected?
   – Switch the game to Borderless Windowed again. Is the issue fixed?
2. Now close Miqobot and do the same actions once again.
   Switch the game to Windowed -> Borderless Windowed -> Fullscreen -> Borderless Windowed.
   Does any of these modes work as expected or do you still have to restart the game to fix your cursor?
3. Close Miqobot and close the game.
   Now start the game only and do not start Miqobot. At this moment the cursor works as expected, right?
   From here on, do the same actions again and switch to different modes.
   Does the issue appear without Miqobot being active?
4. In the game, open settings: System -> System Configuration -> Mouse Settings.
   Enable option ‘Limit mouse operation to game window’.
   Does this fix the issue?
5. Have you installed any third-party drivers coming with your Razer Deathadder?
   Under firther investigation, we have found a similar report on official game forums. They are stating that third-party drivers don’t mix well with the game.
   Second post in this thread seems to describe the same behaviour: FFXIV and Mouse Buttons/Operations after patch
6. Would you please try to temporarily uninstall Razer drivers if they are in use?
   This is not a solution, but we want to verify whether drivers are causing this problem.
   Does the issue still appear after uninstalling them?
   You may reinstall them once again after this test.

It is not very clear why Miqobot becomes a trigger of this bug.
But depending on the information you provide, we will try enabling certain diagnostics features in Miqobot which hopefully will prevent this annoying behaviour.

Thank you very much!

[MiqobotKeymaster]

Index entries for Lumythrite Ore and Camphorwood have been updated 🙂
Thank you very much!

[MiqobotKeymaster]

As with any other issue, we would ask to provide as much information as you can.

Most likely, there is a program installed on your machine that interferes with shortcuts on a system level.
Applications like Photoshop, Monosnap, and many others are known to register their keybinds in the system whenever they are active.

As @ramen suggested, could you try reproducing this issue with other Miqobot features?

• Do Fishing abilities work correctly?
• Does Miqobot use skills in Chocobo Racing correctly?
• Do Macros work correctly?
  For example, if you input ctrl + alt + shift + 1 in macro box (instead of using Crafting Solver), does it fire every time?

Also, please answer these questions in order to provide more information about your issue:

• Do you have any applications running that may interfere with keyboard shortcuts?
• Does this issue happen only when Miqobot is running in background?
• What happens when you press the corresponding shortcut yourself?
  Not with a mouse, but pressing the exact Ctrl-Alt-Shift- combination by hand.
  Is it recognized by the game correctly?
• What is your FPS?
  If game performance drops below 10 FPS, it may lead to unexpected behaviour.
• Do you run the game in Fullscreen or in Windowed mode? Have you tried switching between them and see if it helps?
• Have you tried minimizing your game window completely?
• Which method do you use for switching between windows?
  Do you use Alt-Tab, Win-Tab, or mouse click on taskbar? Have you tried using each of them separately and see if it causes the issue?
• On the 2nd screenshot we see that you use Cross Hotbars. Have you tried disabling them temporarily?
• What Windows version do you use?
• Have you installed any Windows updates recently?

Thank you very much!

[MiqobotKeymaster]

Lorealy wrote:

It seems that whenever I alt tab and more specifically, move my mouse around, Miqobot will refuse to do anything until I stop moving my mouse.

1) Yes, this is a known issue 🙂

This is how the game handles mouse and keyboard events, and there is nothing we can do about it.
In theory it would be possible to fix this by implementing code injections, but it would make Miqobot much more detectable and unstable with lots of other issues arising.
Therefore, we have no plans on implementing code injections.

You can read about it in this thread:
Miqobot v1.2.4 – Known Issues

Miqobot wrote:

An issue wherein Miqobot would fail to move a game cursor, under extensive mouse movement.
Unfortunately, this can not be fixed without code injections, and we have no plans for implementing code injections.
Miqobot is aware of this situation, and she will patiently wait for mouse to stop moving before making another attempt. She needs a small fraction of a second (about 0.25 sec) in order to recover from this issue. Under normal circumstances you wouldn’t even notice this behaviour.

If you want to prevent this behaviour completely, please consider switching the game to Windowed mode and minimizing it, when you run Miqobot in the background. Thus, mouse cursor will not be able to run over the game’s window and will not interfere.

However, please note that Miqobot requires at least 60 FPS to show good performance in Minigames.
For this, you will have to remove the Frame Rate limiter in game settings (as described in Miqobot v1.2.45 – Patch Notes).

Lorealy wrote:

I’ve also noticed that whenever I start Miqobot my mouse will no longer lock itself when holding down right click and moving the camera and it requires a FFXIV restart to restore it.

2) As for your second issue, the one that makes your mouse unable to move camera, this is unexpected.

We haven’t received reports of behaviour you describe, so we would ask for additional information to understand what’s happening.

• Does this happen only to Right Click? Or does Left Click become affected too?
• What exactly do you mean by ‘second screen’? Is this a second monitor or do you mean that another window gains focus?
• Does the issue go away right after closing Miqobot or do you have to restart the game after that?
• Do you play in Windowed mode or in Fullscreen?
• Have you tried switching between modes and see whether the issue is fixed (instead of completely restarting the game)?

We have a few ideas of what might be causing this behaviour, but any additional information you can provide is highly appreciated.

Thank you very much!

[MiqobotKeymaster]

Miqobot doesn’t interfere with your internet connection in any way.
It’s very unlikely that she is the problem.

We plan to address this kind of issues in the future by implementing an automatic relogger whenever a disconnection occurs.
But this is just a QoL feature which might or might not help you, depending on how severe your disconnections are (for example, a Lobby Server error usually causes the game client to close completely).

We recommend opening Cmd window (Win-R -> type cmd -> Enter) and starting ping utility to verify your connection to the game server.
You can find the IP Address of your server on this website: FFXIV Server Status
For example, on Balmung you would type in Cmd window:
ping -t 199.91.189.30

• If your connection is stable, you will see response lines printed approximately once per second.
• If your connection is unstable, you will see delays and/or timeout messages.

You can leave Cmd window opened and continue playing the game.
When the next disconnection happens, simply switch to the Cmd window and look what’s happening.

Additionally, there is a tracert utility that can help you detect a weak spot in your connection’s route.
tracert 199.91.189.30 – will output a detailed description of every node between you and Balmung server.

[MiqobotKeymaster]

Questing is planned for release in v1.3.x series of Miqobot.
Questing bot will rely heavily on Combat support, so we are planning to implement it in several stages.
This way, we can make incremental releases in order to let our users enjoy new features as soon as possible.

You can find more information in this thread:
Progress updates on unreleased features

Since this feature will depend on many others, we cannot give any ETA at the moment.
But rest assured, we will be making additional announcements as we get closer to release.

Thank you for your patience 🙂

[MiqobotKeymaster]

Yes, we are planning to implement this behaviour 🙂
Most likely, it will be available with the release of Scenario Engine.

However, please note that this method will render compass abilities useless ( Lay of the Land and Arbor Call ). If you make Miqobot skip a gathering node and the next one is not in the immediate vicinity, she will be unable to find it and will get stuck.
You can of course use Beacons instead of compass abilities, but this will probably make your Navigation Grids unnecessary complicated.

We recommend allowing Miqobot to gather shards and crystals by default, specifying them as the lowest priority item in Gather by Name. This way, gathering nodes will be always removed out of sight, and compasses will function properly 🙂

[Author]

Posts