[MiqobotKeymaster]

Thank you for your kind review 🙂

Much of the credit for Miqobot being bug-free goes to our users.
Thanks to amazingly detailed bugreports and feedback provided by our users, we’ve managed to fix lots of issues during the past few weeks. There’s still a lot to be done and improved, but we are always open to new suggestions and feature requests. We believe that with the help of our community, Miqobot will become the most advanced tool for FFXIV.

Indeed, we aim to keep Miqobot as lightweight as possible. Thank you for noticing!
And we also understand that Miqobot’s UI will inevitably get cluttered with all the features currently in development. So we already have several UI layouts in design for future versions, and we intend to keep it easy to use in the future too.

Yes, we agree that our pricing strategy is not flexible at the moment.
Our main focus is implementing the core AI and adding more unique features. In the meantime, our marketing team is analyzing the data in order to determine the best price for Miqobot. As soon as we catch up with the development, we’ll definitely reconsider our pricing policy, and there will be more subscription options available.

Thank you very much for supporting Miqobot!

We are very glad that you’ve joined us.
Welcome 🙂

[MiqobotKeymaster]

This feature is already there 🙂

Miqobot has an integrated kill switch, which is triggered whenever there’s any sign of danger nearby:
– When your character accidentally teleports to another location.
– When your character accidentally teleports over a huge distance.
– When Miqobot finds herself in an unknown location.
– When Miqobot does not manage to reach the destination within the alotted time.
– When Miqobot detects that your character is running into a wall.
There are other conditions that trigger a kill switch. It prevents Miqobot from doing bad things and arousing suspicion.

When it is triggered, nothing will make Miqobot go on. The kill switch is global and permanent.
The only way to reset it is to completely restart Miqobot.

This is done to prevent advanced features (such as Scenarios) from accidentally resetting Miqobot by switching to another activity.
By forcing a restart process, Miqobot verifies that you (as a legitimate owner of your character) are aware of what happened, have eliminated any dangerous circumstances, and allow Miqobot to proceed normally.

And yes, detecting a character with ‘GM’ name and triggering an alarm is also a great idea. We are working on it.
There are also other improvements in development, such as detecting GM messages in the chat.

Thank you for reminding us all that we always have to be on guard 🙂

[MiqobotKeymaster]

Accepted 🙂

We already have a new navigation AI prototype that analyzes the geometric patterns and smoothes them on the fly. It also eliminates the barely visible micro stops at waypoints. With this new AI, Miqobot will be able to behave more organically.
It is still unstable and requires time for testing and tuning the details.

Aside from this, we also have plans to implement Standard Movement Type support.
Legacy Movement is used mostly on PS3/PS4 game controllers, while Standard Movement is more familiar to PC players.

Thank you for the request!

[MiqobotKeymaster]

Accepted 🙂

Indeed, this improvement will be very useful for Scenarios. We are planning to implement gathering presets along with Gathering Rotations Designer, or shortly after that.
And of course, you will be able to share these presets just like any others.

Thank you for the request!

[MiqobotKeymaster]

Already there 🙂

Back Quote key (`), Minus key (-), and Equals key (=) are recognized by Miqobot as is.
Miqobot supports the following punctuation keys:

• Minus (-)
• Equals (=)
• Comma (,)
• Period (.)
• Semicolon (;)
• Apostrophe (‘)
• Back Quote (`)
• Slash (/)
• Backslash (\) – not to be confused with another backslash key which is named OEM 102
• Left Bracket ([)
• Right Bracket (])

Also, if your keyboard has other punctuation keys, it is possible that the game uses similar key codes for them, and thus they are also supported.

But please be careful with dead keys (diacritics). They alter the keyboard state on a system level and will interfere with your typing. More about this in the Known Issues section of Miqobot v1.2.4.
Appreciation to @gregye for discovering and reporting this issue.

To use Backspace, type {bs} in the macro box. You can use it with Ctrl/Alt/Shift as usual: ctrl+alt+{bs}
To use other cursor control and special keys, please follow this reference:

• Backspace - {bs}
• Tab - {tab}
• Enter - {enter}
• Esc - {esc}
• Spacebar - {space}
• Insert - {ins}
• Delete - {del}
• Home - {home}
• End - {end}
• Page Up - {pgup}
• Page Down - {pgdn}
• Left Arrow - {left}
• Up Arrow - {up}
• Right Arrow - {right}
• Down Arrow - {down}
• Print Screen - {printscreen}
• Pause - {pause}
• OEM 102 - {oem_102}

Case is irrelevant, you may type either in lowercase, in uppercase, or in combination of both.

[MiqobotKeymaster]

Accepted 🙂

And to be honest, we’ve already done the preliminary research some time ago.
At first, we were going to implement Desynthesis through the dedicated Desynthesis window – an alternative to inventory navigation. But that window doesn’t allow any advanced grouping modes and would require specifying all items by name. It could be suitable for desynthing fish, but no more than that.

We are researching the inventory navigation method now, and we’ll be making announcements soon.

And yes, your idea to quickly select an inventory quadrant looks very promising.
It seems to be the most convenient way to implement Desynthesis settings.
Thank you very much!

[MiqobotKeymaster]

Thank you both for raising the question and finding the truth together.
Now we have one less thing to worry about 🙂

[MiqobotKeymaster]

A new section for Grids and Presets has been added. As you suggested, it is intended for additional presets for Miqobot made by our community.

We have also prepared two index threads:

• Index of all Gathering Items.
• Index of Chocobo Racing Classes.

We will keep these threads up-to-date, so you don’t have to worry about it.
We are very grateful for your dedication 🙂

[MiqobotKeymaster]

Lyfox wrote:

The what just happened..?

(10:50:19) Step 20. Recommended skill: (Hasty Touch)
(10:50:22) Step 21. Recommended skill: (Steady Hand II)
(10:50:23) Step 22. Recommended skill: (Careful Synthesis II)
(10:50:25) Step 23. Recommended skill: (Great Strides)
(10:50:27) Step 24. Recommended skill: (Observe)
Excellent pops ———!
(10:50:29) Step 25. Recommended skill: (Byregot’s Blessing)
(10:50:32) Step 26. Recommended skill: (Careful Synthesis II)

Observe? Really? I forgot that thing even existed lol. and I ended up with 0 CP so there was no other way to bait it.
Im in love with this release already. Miqo youre a smart badass.

Thank you for your review 🙂
Please enjoy!

[MiqobotKeymaster]

Accepted 🙂

This logic will fit best into advanced Gathering Rotations. We’ll consider this enhancement when Rotations get ready for release.
Thank you very much!

[MiqobotKeymaster]

Thank you for letting us know!

Yes, changing your keybind settings seems to be the only way to avoid this behaviour permanently. We apologize for the inconvenience.
We’ll keep searching for a better solution, and we will let you know when we find it 🙂

[MiqobotKeymaster]

Thank you very much for this information!
We haven’t considered this scenario yet.

The main issue was that the previous keystrokes emulation algorithm altered the global keyboard state on a system level (specifically for Ctrl/Alt/Shift keys). But the game doesn’t read the global keyboard state, a simple WinAPI message is enough. Altering the keyboard state was an overkill, so we removed it.
Along with multiple other adjustments and optimizations, this resulted in a more stable algorithm.

Do you actually experience this behaviour in Miqobot v1.2.4 on Windows 10?
Please let us know if you do. If the issue is still not fixed completely, we might have to add it to Known Issues section, along with your recommendations on how to avoid it.

[MiqobotKeymaster]

That would be great!
I will add a link to your R-300 thread, if you do 🙂

[MiqobotKeymaster]

There is an indicator of tracks within a waypoint set, but it’s invisible.
You can identify what tracks you have by following these steps:

1. Select a waypoints preset in question.
2. Select a track in question.
3. Press Start.

• If there is no track in the selected waypoints preset, you will see a warning Message box about this.
• If there is a track already, you will see no Message box, and Miqobot will try to look for Chocobo Race NPC. Press Stop right after that to prevent her from doing anything weird.

This check can be easily performed in any location, no need to go to Chocobo Square.

And you can also use letters S C T as additional, more visible indicator, of course 🙂

[MiqobotKeymaster]

Accepted 🙂

Retainer Bot is actually already planned, but not announced yet. We are researching the ingame messages and the list of available ventures for all Retainer jobs. Since they appear differently in each language, we are looking for an easy way to identify them independently from the language of the game client.
We’ll be making announcements after we finish the research and get more data.

Thank you for your request!

[Author]

Posts