[MiqobotKeymaster]

In order to minimize overhead cost, the latest beta is merged into the full release of Miqobot.
After the update is fully tested and stabilized, new combat features will be branched off into beta again.

[MiqobotKeymaster]

Yes, we can make special presets for jumping puzzles, but we are still not sure whether it would be worth the time investment.

At the moment we are working on the combat system, which seems to be more popular than the new jumping puzzle in Gold Saucer. Please give us more details about your vision so we can understand the interest in this activity.

• For how long would you use this feature?
• Would this feature justify the subscription price?
• Is there anything unique about this feature that yields different rewards not obtainable by other means?

Thank you very much!

[MiqobotKeymaster]

In order to emulate mouse input, we would have to disable your actual mouse and you would lose control over Miqobot and the game client. In addition, this would make background mode completely impossible.
We apologize, but at the moment we have no plans to implement mouse emulation.

In order to avoid unnecessary stress when playing with Miqobot, please follow our recommendations in this guide:
Technical and Social Safety

[MiqobotKeymaster]

Thank you for letting us know very much!

We will plan an additional review of the navigation module and research the possibility of supporting higher Camera Speed values.
In the meantime, please try to avoid extreme FPS and Camera Speed settings.

[MiqobotKeymaster]

This is an interesting suggestion.

These files are stored in the Windows Temp folder because their purpose is indeed temporary. They are required only when Miqobot is active and can be safely deleted later.
What would be the benefit of placing them in the current directory instead?

[MiqobotKeymaster]

Yes, there are two detection systems in place:

1. Miqobot will automatically scan the available ingredients and deactivate when any of them is missing.
2. Miqobot will hit the Synthesize button only for a limited time and deactivate if synthesis doesn’t start after several attempts.

The second system is designed to trigger regardless of the reason and should avoid deadlock scenarios when you are AFK.
But of course, if you are not AFK you can stop Miqobot manually before it is triggered.

[MiqobotKeymaster]

Yes, there are many QoL improvements planned, including auto-detection and inverted camera support.
Thank you for your request very much!

[MiqobotKeymaster]

Yes, that’s pretty much our plan.

It will take the same amount of time to implement level 60 rotations with or without Squadron Dungeons. So we are adding new dungeons support as a bonus as we make progress towards Palace of the Dead.

[MiqobotKeymaster]

We are implementing battle rotations for all jobs and Squadron Dungeons are well suited for incremental updates to show our progress. Palace of the Dead requires full level 60 rotations support, considering that we do not plan to stop at Floors 1-10 only.

It will take a few weeks regardless of whether we release new dungeons or not.
So we think that releasing small updates on a weekly basis is better than releasing nothing at all until everything is ready.

[MiqobotKeymaster]

We do not expect any significant changes at 70**** crafting tier that would be worth another analysis post.
We designed Crafting Solver to be stable through the entire lifetime of Stormblood expansion.

For 70*** recipes, +10 CP equals roughly +25.3 Control or +39.4 Craftsmanship.
The stat distribution is approximately the same for all recipes at level 70.

We recommend melding as much CP as possible, with Control coming second in priority, and Craftsmanship third.
If you use Maker’s Mark with the Crafting Solver, you can safely leave Craftsmanship at minimum recipe requirement because it has no impact on Maker’s Mark.

For in-depth analysis on 70-star recipes please refer to this thread: Stormblood – Upgrade Stage 2

[MiqobotKeymaster]

Nott wrote:

Everything you said makes sense but I wonder why I sometimes see it putting CZ as the first step when I never disable progress first?

Comfort Zone is applied only when the estimated number of steps is more than 10 and neither of them will be blocked by the lack of CP.
In order to estimate number of steps, Miqobot looks into the future and evaluates the rotation under several luck scenarios:

• With a lot of Good / Excellent conditions.
• With some Good conditions.
• Without Good conditions at all.

In the dimension that has no knowledge about Inner Quiet and Great Strides, it may result in the number of steps being less than 10. For example, if you encounter several Excellent conditions CP will be burnt faster than usual.
But if all scenarios are safe in the “Progress First” dimension, Comfort Zone will be applied on the first step.

You are correct, recipe durability does affect the estimation algorithm but this is only one of the factors.

[MiqobotKeymaster]

Both of your questions are easy to answer.
Please note that they are not related to the original post about Stroke of Genius.

1. When there is no Inner Quiet active, using quality actions would be a waste of CP and Durability.
   So when an early Good condition pops at max CP, there are two options:

   – Ignore it and continue the opener normally.
   – Use Tricks of the Trade and continue the opener normally.

   Both options do not affect the opener, but the second one switches condition back to Normal and extends the total number of steps. This choice gives one more opportunity to encounter a Good condition later when we can actually utilize it.

2. Delay of Comfort Zone is a price we have to pay for certain optimizations.
   When you enable “Progress First” optimization, Miqobot splits internal logic in two dimensions:

   – The first dimension has no knowledge about Progress bar.
   – The second dimension has no knowledge about some CPU expensive actions like Inner Quiet, Great Strides, or Comfort Zone.

   Both dimensions are solved independently from each other and the final solution is constructed at the post-processing phase by merging different dimensions. The actions that were sacrificed in the second dimension must be weaved into the opener, but it is impossible to do so with 100% efficiency since neither dimension knows their true place.
   This method results in a significant computational boost at the cost of slightly suboptimal rotation.

   According to our calculations, this optimization reduces average HQ rate by 3%.
   Depending on recipe difficulty, it will result in x3-x20 computational boost.

   If you need the +3% HQ rate increase, please disable “Progress First” optimization.
   It will allow Comfort Zone to appear 1-2 steps earlier in the opener.

[MiqobotKeymaster]

In order to answer your question, we have to dive a little into the technical side of the game.

When you enable “Limit FPS when client is inactive”, the resulting value is 3-4 times lower than the maximum allowed FPS.

• If the game is capped at 60 FPS, it will be limited to 18 FPS when inactive.
• If the game is capped at 30 FPS, it will be limited to 11 FPS when inactive.
• if the game is capped at 15 FPS, it will be limited to 8 FPS when inactive.

Since Miqobot doesn’t use code injections and doesn’t take away your mouse, she can only control your character with keyboard.
Low FPS in combination with high camera speed result in fragmented movement which is very hard to control. It may cause some extreme behavior wherein Miqobot is unable to aim the camera at specific angle, because that particular angle is being skipped between frames. And if it happens several frames in a row, Miqobot will get stuck continuously jolting camera up and down.
This behavior falls under the definition of “something went very wrong”, and therefore must trigger a kill switch.

You can easily reproduce this problem in the following way:

1. Set Camera Speed (Keyboard) to 100.
2. Set FPS limit to 15.
3. Enable “Limit frame rate when client is inactive”.

Now create a new scenario in Miqobot and try this:

vangle(-0.8)
vangle(-0.4)
vangle(-0.2)
vangle(0)

Did Miqobot manage to align the camera correctly at each angle or did she get stuck at one of the functions?

The settings in this experiment are of course beyond the critical threshold and you would never use them during normal gameplay. However the problem is of random nature.
In other words the closer your settings are to the critical threshold, the more likely this problem will occur. Depending on FPS and camera speed it may indeed take many hours of uninterrupted performance before it finally happens.

We apologize for the long and technical explanation, but it’s the only way to answer your question about why it happens only sometimes 🙂

[MiqobotKeymaster]

Thank you for your answers.

Yes, the settings you use are dangerously close to critical values.
Miqobot can function at 10-15 FPS, but this is the bare minimum at which game performance starts to cause problems. In addition, your camera speed is set to 60, which is twice faster than the default value of 33. Was there any specific reason for this setting to take place?

We will give an explanation about why it happens in the next post, but first let us give you a solution.
In order to avoid this problem, please use the following settings:

• Frame Rate Limit: 60 FPS
• Camera Speed (Keyboard): 33

This will ensure that Miqobot gets at least 18 FPS when client is inactive.
You may also increase camera speed up to 40, because this is the default setting used by our developers.

[MiqobotKeymaster]

Thank you for reporting!

We have analyzed the message log you provided and managed to identify the problem.
There is only one function in the navigation module which triggers a kill switch after exactly 20 seconds. It’s the vertical camera alignment function.

After every navigation sequence Miqobot tries to restore the vertical camera angle to roughly 15 degrees above eye level. In your case she failed to do so for 20 seconds which is extremely long for a simple camera rotation, so she decided that something went very wrong and triggered a kill swtich.

Would you please answer the following questions:

1. What keybinds are assigned to actions “Point Camera Up” and “Point Camera Down”?
2. What value is assigned to camera speed in Character Configuration settings?
3. At what FPS do you usually run the game with Miqobot?
4. Do you experience game stuttering from time to time?

[Author]

Posts