[MiqobotKeymaster]

Breather ability has been fixed.

[Update Details]
FINAL FANTASY XIV Hotfixes (Apr. 5)
・An issue with Chocobo Racing wherein the “Breather” effect would be applied while accelerating under certain conditions.

FINAL FANTASY XIV Updated (Apr. 5)

We are going to research the current state of Breather mechanics and see whether it’s still of any value.

[MiqobotKeymaster]

Miqobot is unaffected by patch 3.25 hotfixes (Apr 05).
There were no changes in the game client, fixes were mainly server side.

[MiqobotKeymaster]

We could do that, but it would require additional research. Like Gregye and Lyfox said, Chocobo Challenges have very different navigation layouts and unlikely to win easily.

Would you please describe your request in details so we could understand it better? In particular, what would you like Miqobot to do when she tried a challenge and couldn’t win?

• Try over and over until she wins.
• Try several times and leave it for later.
• Try once and forget it.
• Try once at every chocobo rank up.
• Any other behaviour?

This information would help us analyze this feature and find the most appropriate solution.
Thank you! 🙂

[MiqobotKeymaster]

Both requests accepted 🙂
We’ve been looking into new mechanics of Chocobo Racing for some time, and yes, both decelerating and choosing the ability moment feel like necessary additions. Also they are easy to implement.

As for Breather ability, it will become clear whether it’s a bug or not after patch 3.25 hotfixes coming tomorrow. If this mechanic doesn’t change after maintenance, we will consider implementing it for Miqobot.

[MiqobotKeymaster]

Oh by accelerator I meant that slui.exe affected how fast your issue emerged, by forcing the game and Miqobot into background mode. But the true cause of it lies elsewhere 🙂

We have made a lot of technical adjustments during the past few days, including how Miqobot emulates keystrokes and performs in background. So there’s a possibility that your screen freezes have already been fixed. It is not guaranteed though, because we couldn’t reproduce your issue at our labs.

We have sent you a download link to a special build by email.
Would you please check it out and verify whether the issue still exists?

Thank you!

[MiqobotKeymaster]

venoivixx wrote:

I’m having troubles with Miqobot selecting the Gathering nodes with ‘Confirm’.
She senses the node, goes up to it and then says “Ummm. I don’t see any sparkles here :(“, seems like she doesn’t wanna use any of the “senses” either.

The behaviour you encountered is a part of Gathering AI, which tries to prevent being stuck when it detects mistakes in navigation. You can more about in Gathering Help section. (Scroll down to Gathering Nodes Blacklist.)

Would you please give us more information so we could help you?

1. What happens on a screen when you encounter this behaviour? Does Miqobot try to focus the node by rotating camera left and right?
2. What happens if you don’t stop Miqobot after encountering this behaviour? Does she stop trying to focus the node at some point?
3. Does this happen with every gathering node or just one of them?
4. What keybind do you have for “Target NPC” action? You can check this in the game: System -> Keybind -> Targeting tab -> Target Nearest NPC or Object.
5. If you could upload the navigation grid you use for gathering, we would help you detect the cause of this issue.

As for senses, they come into play only when there are no gathering nodes seen on the minimap. And you also need Lay of the Land/Arbor Call to be on your hotbar. There are cases when Miqobot will refuse following the activated sense, for example, when it’s trying to lead her into the wall.
This is described in details in Gathering Help section as well. (Scroll down to Senses and Beacons.)

The easiest way to verify whether senses work internally is to switch to Monitor tab and press Lay of the Land/Arbor Call manually. If it works, you should see coordinates in the right lower corner next to “Compass” line. (Please use v1.2.3 for this, not v1.2.4 Beta because its monitor is replaced with Crafting State.)

Would you please confirm this to give us more details?
Thank you!

[MiqobotKeymaster]

Carl Arbogast wrote:

Hi,

Thanks a lot for those 2 really quick updates, I found a little issue, Miqobot doesn’t recognise the new mount, the one sold on Mog Station only, Bennu http://xivdb.com/mount/74/.

When this mount has an Hot Bar shortcut, Miqobot can’t use it.

Thank you for reporting!
Bennu mount will be added in the upcoming version of Miqobot.

[MiqobotKeymaster]

Of course 🙂
FATE Bot is already planned for release in one of the upcoming versions of Miqobot. We’ll be posting status updates in our FATE Development section.

[MiqobotKeymaster]

Miqobot has been fixed, and we are performing final testing.
Both v1.2.3 and v1.2.4 Beta are fixed.
No need to redownload anything, just start Miqobot and play 🙂

If you encounter any issues, please let us know!

[MiqobotKeymaster]

Okay, got it.
So basically the issue didn’t go anywhere, and slui.exe was just an accelerator, right?
We will make a special diagnostics build of Miqobot for you, which will perform tests and create a log file with results. All you will have to do is launch it, do some Chocobo Racing as usual, and send us the log file 🙂

This will be done after the maintenance for patch 3.25 coming in a few hours, since Miqobot will most likely be broken. After we fix it again, we’ll make a diagnostics build.

If you read this message before the servers go down, we would like to ask you to try Fishing bot or Gathering bot. We need to know whether this issue is specific to Chocobo Racing only or this is a bug somewhere in basic logics.
Thank you!

[MiqobotKeymaster]

So slui.exe was the root of this issue? It’s great you figured this out!
Thank you for letting us know 🙂
It will help our users to diagnose and fix similar issues in the future.

As I understand correctly, now you have another issue when running Miqobot in background mode.
Your PC specs you posted earlier are totally enough to run Miqobot with several instances of the game, so this seems like a bug. We are working on improvements for keystrokes emulation, and most likely this bug is also connected. If we have more information, we’ll be able to detect it faster.

Would you please answer two questions to clarify this:

1. Is this the same “Miqobot freezes” issue we were talking about, i.e. the same 5-15 seconds lag? Or do you mean that Miqobot stops sending keys while the game itself is unaffected?
2. Do you minimize Miqobot window when switching to another game client or watching videos? Or do you press Alt-Tab? Please check both ways and let us know if the issue persists.

Thank you very much!

[MiqobotKeymaster]

We have managed to reproduce the bug.
And we’re already working on a solution. No injections needed, it will be fixed by using a slightly different approach to sending keys.

Thank you for reporting very much! 🙂

[MiqobotKeymaster]

Thank you for the feedback!
Please don’t worry. Of course we are not going to implement any injections 🙂

You are right that Miqobot is emulating keystrokes instead of injecting them. And it is true that in some rare cases this method may interfere with a foreground window. But we aim to implement Miqobot’s AI in the most graceful way possible, and that’s why we are always looking for ways to improve Miqobot.

At the moment we are investigating the issue, and we can’t say exactly whether it will or will not be fixed.
We’ll let you know as soon as we have more data.

[MiqobotKeymaster]

Thank you very much!
We will be performing tests using the most similar equipment we can get, and I’m sure we’ll find the reason behind this.

[MiqobotKeymaster]

Hi Jony.

First of all, we have moved your post into a separate topic, because this issue requires special attention. Hope you don’t mind 🙂

Second, let us isolate the issue. Chocobo Racing is one of the most CPU-intensive feature we have at the moment, so there may be a lot of factors involved. We would ask you to follow these steps and tell us what’s happening at each of them.

1. Restart your PC and start a DX11 version of the game. Does it perform normally?
2. Launch Miqobot and let it auto-detect the game. Does screen lag or freeze already at this point?
3. Copy everything that Miqobot says in the output area and post here (starting from “Hello! I am your Miqobot!”).
4. Switch to Monitor tab and observe the data it shows. Does it show correct values?
5. Disable 3D Radar completely. In order to do that, switch off all of these options:
   – 3D Radar tab -> show -> choose nothing;
   – 3D Radar tab -> show FATEs -> list;
   – 3D Radar tab -> show FATEs -> world;
   – Navigation tab -> show on radar;
   – Gold Saucer tab -> show -> rails;
   – Gold Saucer tab -> show -> mid-rail;
   – Gold Saucer tab -> show -> progress;
   – Gold Saucer tab -> show -> waypoint.
   With all of these options disabled, does the issue persist?
6. If the issue doesn’t persist after step #5, then try switching them on and observe the results. Switch only one option at a time and see whether it changes anything. After you test each of the options, enable them all and tell us what happens.
7. Instead of Chocobo Racing, try a Fishing bot. It has the most basic mechanics, so it’s better to start here.
8. If Fishing bot works, try a Gathering bot next. Follow the steps written in the beginning of Gathering Guide.
9. When you finally detect the issue, stop at that point and just close Miqobot. Does the issue go away immediately?

Let us know the results and we’ll think what to do next 🙂

[Author]

Posts