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

[MiqobotKeymaster]

We are looking into your issue, but first we have to be able to reproduce the bug.
Could you please give us more specifics about your hardware and operating system? We will try to recreate your environment as close as possible and see what we can do 🙂

[MiqobotKeymaster]

Accepted 🙂
This is a newly added fish in 3.2 which requires a folklore book, right? We will look into the mechanics, should be easy enough.

[MiqobotKeymaster]

Of course!
We are aware of the issue and have already planned an upgrade 🙂
Take a look at our Gathering Development thread. This feature is being prepared next.

Miqobot wrote:

When rotations are implemented, you will be able to assign a rotation to all items at once or to each item separately. And Miqobot will apply a skill rotation only when an item is present in the node. If there’s no wanted item, she won’t waste any GP.

Thank you for your feedback!

[MiqobotKeymaster]

Sure.
Most likely Triple Triad will be coming after Scenario Scripting, since it’s already almost there and been planned since the day of public release. We’ll be making more announcements as we move further along the way and have more data. Please understand that it’s very hard to make an accurate estimate with all the features currently being in development.
We’re doing our best 🙂

Thank you for your patience!

[MiqobotKeymaster]

Lyfox wrote:

Niice I can finally finish my master IV books. thanks!
One question with gathering by name though, how do I input a name that is also a part of another name? I want to collect Dark Chestnut but it overlaps with Dark Chestnut Log and Dark Chestnut Branch.

Thank you for asking, we forgot to mention it 🙂
Put square brackets [] around Dark Chestnut, and it will prevent overlapping with other names. Square brackets [] disable a substring search, so only a full match will be considered. For example:

[dark chestnut]
log
*

This will make Miqobot collect Dark Chestnut if it’s there, and Dark Chestnut Log otherwise.

[MiqobotKeymaster]

dc0ke wrote:

“Crafting Solver” Feedback
– First attempt took 23 secs to calculate and since I’m assuming I didn’t have the abilities to create 100% Quality, resulted in a successful creation, but at 1% Quality. I’d love to see an algorithm that prioritizes highest HQ with successful craft.
– Second attempt I tried something low level and I kept getting a “Step 1. Recommended skill: (Nothing)” error
– Third attempt I re-tried attempt #2 (took 6 secs) and was successfully able to get a HQ item. However due to its very low level I capped out on Quality very early and I spent half the time doing Observe, Tricks of the Trade. If it’s possible to recognize and stop at 100% Quality, it would optimize the experience
– Surprised that some of the very basic cross-class crafting skills were not available (such as… Steady Hand II, Byregot’s Blessing, Manipulation, Careful Synthesis II, and Comfort Zone). Maybe a set of checkbox of what cross-skills you currently have would be useful.
– Overall good first attempt, but still some work to do, before I’d trust it over my basic set of crafting macros.

Very interesting. Could you please give us more details about what was happening in First and Second attempts?
The behaviour you describe is unexpected (unless it was at 51+, for which we have very little data so far).

1. What was your crafter’s level and what was the recipe’s level?
2. A screenshot from the Monitor tab would be extremely helpful (for First and Second attempts).
3. What was the exact sequence of actions in the First attempt? Miqobot always tries to maximize quality first, so how did it turn out to be 1% quality?
4. Did you press Stop between First and Second attempts? Or did you change recipes on the fly?
5. How long did it take Miqobot to solve the Second attempt? Was it the same 6 seconds as in Third attempt?

And of course, we’ll be definitely making improvements along the way. We are already working on changing strategy at 100% Quality.

As for adding more skills, the main issue here is that it takes a lot of time to adjust the mathematical model for each of them. For example, Comfort Zone will add a whole new dimension to solving algorithm, and it will result in x10 time required to solve (230 sec instead of 23 sec). Manipulation would make time x3, Steady Hand II would make time x5, and so on. We are working on optimizations to keep this reasonable, but it will take a while. And that’s why we are releasing early – to communicate and find the best solution together 🙂

[MiqobotKeymaster]

dc0ke wrote:

Fantastic beta. Loving the “Gather by Name” feature and I’m putting the other beta features through a gambit of tests. Keep up the great work!

“Gather By Name” Feedback

– Needs an easier way to change priority (like drag/drop or up/down buttons)
– Enhancement: Would love there to be a pre-populated list that you could pick from Search Filter + (Gathering Type > Name) or Search + (Zone > Name)
– Enhancement: Zone Detection to help narrow down what you can gather in a specific zone
– Enhancement: A count of what’s been gathered during a sesssion

Thank you for the feedback!
We’ll look into your suggestions and see whether they can be pushed into the full version without delaying it much 🙂

We also hope that adding a Gathering Presets list would help with quick population of Gather by Name list. And it would also allow sharing. But you’re right, a Search feature would be a great addition.

[MiqobotKeymaster]

Yes, it will be possible with the release of Scenario Scripting.
If you want to know more details, please read our Gathering Development section. Under Advanced Scenarios, you can see that we have planned Aethersand and Favor farming.

[MiqobotKeymaster]

Indeed, we have overlooked F1-F12 keys when we implemented macro feature. At the moment, only letters and numbers supported. But this is an easy adjustment, so we are going to implement it for the upcoming version of Miqobot.

When using icons from hotbars, there’s a different algorithm involved which takes keys directly from your ingame keybinds. So this is just an issue with macro parser.

Thank you for this detailed explanation 🙂
This is well described in terms of feature request, so we can easily implement it right away.

[MiqobotKeymaster]

This is exactly what we needed. Thank you very much!

We have reproduced the issue, it indeed happens when you run the game in background, and when the mouse cursor passes over the game window (even if covered by another window), it interrupts any keypresses. These lines were the key to understanding this issue.

(8:46:40 AM) Sorry, couldn't move cursor with key '[{NUMPAD6}, 0x00]' :(
(8:46:43 AM) Sorry, couldn't move cursor with key '[{NUMPAD6}, 0x00]' :(

We will make adjustments to Miqobot’s AI, and this issue will be fixed in the upcoming version. Thank you for providing such a detailed report 🙂

[MiqobotKeymaster]

Can you please confirm that Miqobot detects collectability rating correctly?
Collectability value appears in the Output Area each time Miqobot makes a decision whether to keep or discard the fish. Also, the Output Area is the first place we recommend to look for clues when something weird happens.

It seems like a rare bug caused by selecting a wrong button in Yes-No window, and we’ll be making adjustments based on your feedback. If there’s any other valuable information in the Output Area, please tell us 🙂

[MiqobotKeymaster]

Gather by Name is implemented and planned for release in Miqobot v1.2.4.

[Author]

Posts