[MiqobotKeymaster]

Is the bug still present?
Please let us know if it is. We would like to find and eliminate it.

[MiqobotKeymaster]

Thank you for the idea on achievements!

I will add your list of achievements to the index of Gathering Grids.

[MiqobotKeymaster]

Pause is implemented only for Fishing, because for all other activities Stop is equivalent to Pause.
With some rare exceptions, you can start Miqobot at any moment, and she will easily catch up to what’s going on.

For example:

• With Gathering, you can Start with Gathering window opened.
• With Chocobo Racing, you can Start after registering or even in the middle of the race.
• With Crafting, you can Start half way through the synthesis. The only drawback with Stop is that Crafting Solver forgets the solution and recalculates it again. It still performs correctly, but it wastes time and CPU power.
  It will be fixed.

We aim to implement all the upcoming features in the same way.
Quick start, quick stop, quick continue.

[MiqobotKeymaster]

At the moment, we are considering three possible solutions for Chocobo Racing Editor.
From simple to complex:

1. Text Editor.
   Will eliminate the need to restart Miqobot after each edit.
   But it is also the least intuitive method. It won’t be able to reflect changes on 3D Radar (at least not immediately). And it’s error prone.
2. 3D Editor.
   Will allow to simply re-record a specific section of the track. Will eliminate the possibility of typo by maintaining the correct order of waypoints.
   On the bad side, it will require teleporting to race location to make even a simple edit (Southern Thanalan, Eastern La Noscea, or South Shroud).
3. 3D Editor + Displaying Race Data.
   Will be able to show all possible chests, monsters, traps, and bonus pads outside of the race. Will eliminate the need to make screenshots to remember positions of the objects.
   This is the hardest option to implement, because it will require collecting a lot of data (for each possible Class, Course, and Challenge). And it will still require teleporting to race location.

We are implementing editors in this order, because each implementation is based on the previous one.

As for recording jumps with gamepad – sorry, Miqobot does not support gamepad. She recognizes only keyboard activity.
We apologize for the inconvenience.

Thank you for your review very much!
It led us to several new ideas as to how to implement the Chocobo Racing Editor 🙂

[MiqobotKeymaster]

Please, assign something to Switch to Hotbar 6.
Miqobot requires all Switch-To actions in order to perform efficiently.

If you are afraid to hit this action by mistake, you can use a shortcut you would never use yourself.
For example, Ctrl-Alt-Shift-6.

Did it fix the issue?

[MiqobotKeymaster]

Unfortunately no, it won’t reduce work for Miqobot.

Implementing Sprint waypoints will only make the AI more complicated, because Miqobot will have to deal with two types of Sprint at the same time – manual and automatic. Sprint waypoints will also make it harder to combine path segments together, because different types of waypoints imply different behaviour. So Miqobot will have to do more calculations to behave properly.

Disabling Auto-Sprint doesn’t change anything, because Miqobot has to consider all possible cases at each moment.
If you enable or disable Auto-Sprint on the fly, Miqobot must adapt to your commands immediately. She doesn’t stop the navigation algorithm only to restart it with new settings, but she accepts whatever you ask on the fly.

But I don’t think that you have to be worried about technical details 🙂
If you want this feature, we will look into this and will do our best to find the proper solution.

[MiqobotKeymaster]

Would you please provide more information about your issue?

1. What keybind do you have assigned to ‘Switch to Hotbar 6’?
2. Where exactly is Mooch located on your hotbar? Is it on Hotbar 6?
3. What happens if you move Mooch to Hotbar 1 instead?
4. Is ‘mooch’ enabled in Fishing settings in Miqobot?
5. What happens if you disable ‘mooch’ in Miqobot?

Thank you!

The answer that @captainblunt gave you may also be helpful.
But it doesn’t seem that you want Miqobot to click Mooch with mouse, as requested by @theghettochipmunk in his thread.

If you want to know more about why Miqobot needs ‘Switch to Hotbar 6’, please refer to the Keybinds and Icons Recognition guide.

[MiqobotKeymaster]

@captainblunt is right.
Miqobot is a keyboard-only bot. She doesn’t use mouse to click anything on your hotbar, because otherwise it would be impossible for you to run Miqobot in the background.

That’s why you need to make sure that everything on your hotbar is reachable by keyboard.
An icon can be reachable in two ways:

• Either by assigning a shortcut directly.
• Or by switching to another hotbar and pressing that icon like it was on first hotbar.

Please refer to the Keybinds and Icons Recognition guide for details.

In order to eliminate the issue with being unable to mount, please follow these steps:

1. Make sure that you have a key assigned to each icon on Hotbar 1.
2. Make sure that you have a key assigned to each action ‘Switch to Hotbar 1-10’.
   The way @captainblunt described it is correct.
3. Make sure that you have a key assigned to ‘Switch to Pet Hotbar’.

Does the issue still persist?

[MiqobotKeymaster]

This is a good idea 🙂

At the moment, Miqobot uses the distance to next waypoint as indicator whether to enable or disable Sprint. The distance threshold is set too low because of the nature of the pathfinding algorithm. It splits the entire path into segments, and each of them is evaluated separately.

If we set the distance threshold higher, it may eliminate the issue you have noticed – Sprinting right in front of a gathering node. But if somebody creates a very detailed navigation grid with short segments, Miqobot might never use Sprint at all.

The new navigation AI will be able to combine different segments together, and we will be able to increase the Sprint threshold after that. We are also planning to make the threshold available in Advanced settings of Miqobot.
This is the current plan to address the issue you have described.

Sprint waypoints will be a nice addition, because they will let you define the exact moments when Miqobot is allowed to Sprint. We are going to look into implementing them, when the new navigation AI is ready.

Thank you for the request!

[MiqobotKeymaster]

Sorry, we can’t give you any ETA yet 🙂

Our developers are focusing on implementing new features at the moment, and this navigation enhancement will require much more of their time than a bug fix.

We are planning to release it in public in one of the upcoming Betas. And we will be very grateful, if you find some time to test the navigation AI when it becomes available.

Thank you for your patience very much!

[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.

[Author]

Posts