This topic contains 15 replies, has 3 voices, and was last updated by 
Miqobot 7 years, 12 months ago.
-
Posts
-
We are glad to let you know that we have released a new version of Miqobot.
Thanks to all your suggestions and bug reports, we’ve managed to implement even more features and fixes than we anticipated. And that’s great!We are extremely grateful to all of you! 🙂
New Features
- Fishing: Fish Eyes is implemented.
- Chocobo Racing: Chocobo Abilities can now be executed later in the race.
- Chocobo Racing: Deceleration has been implemented. Precise control over Acceleration and Deceleration rules is now available.
- Chocobo Racing: Advanced parameter to adjust Steer Power is implemented.
- Gathering: Gather by Name is implemented.
- Gathering: Advanced configuration that allows executing gathering skills only for specific items is now available. No more wasting GP on shards or crystals when you don’t need them.
- Both Gathering and Crafting Macros now accept F1-F12 keys, as well as Numpad 0 – Numpad 9 keys. This is described under Crafting Macros, but this feature applies to Gathering as well.
- Crafting Macros can be stored in the Crafting Presets list.
- Crafting Solver has been implemented. Stability has been significantly increased from what was in Beta version.
- Crafting Solver: Actions are now verified for availability. Verification is performed by job, by level, and by cross skills panel.
- Crafting Solver: New actions are implemented. Read full list: Solver Skills.
- Crafting Solver: Formulas are upgraded for 51+. It is now possible to craft any recipe up to level 60.
(With a few exceptions that require Elementally Aspected actions or specialist actions. Please refer to the Advices section on Crafting Solver.) - Crafting Solver: Stability on formula errors is significantly increased. Miqobot now learns on the fly by analyzing each synthesis action result and readjusting when necessary.
- Crafting Solver: A small reference monitor, which predicts the required time and memory, is added to the Solver options.
- Crafting Solver: It is now possible to speed up the solving algorithm up to 8 times by sacrificing a small fraction of CP accuracy. Read about this option under CP Chunks of Crafting Solver.
- Crafting: It is now possible to enable crafting logs and collect data in the process.
- Crafting Monitor is implemented on Monitor tab.
- Multibox Support is implemented.
- Bennu Mount (added in patch 3.25) is now recognized by Miqobot.
- Keystrokes emulation algorithm has been reimplemented from scratch. It works about 100 times faster than the previous one.
Fixed Issues
- An issue wherein Miqobot would get broken in case of a global DNS servers outage.
An issue wherein some keys would accidentally interfere with the foreground window, when Miqobot is in the Background mode.(This issue is confirmed to reoccur with diacritic keys.)- An issue wherein letter case would accidentally change in the foreground window, when Miqobot is in the Background mode.
- An issue wherein Ctrl/Alt/Shift would accidentally alter the keystrokes in the foreground window, when Miqobot is in the Background mode.
- An issue wherein a page in the web browser would accidentally scale itself during mouse wheel scroll, when Miqobot is in the Background mode.
- An issue wherein a double click would not fire, when Miqobot is in the Background mode.
- An issue wherein Miqobot would accidentally steal focus from the foreground window, when she’s in the Background mode.
- An issue wherein Miqobot would stop sending keystrokes, when Miqobot window is minimized.
- An issue wherein Miqobot would not send keystokes at all, when default keyboard layout is not English.
- An issue with Crafting Solver, wherein it would crash under certain conditions.
- An issue with Crafting Solver, wherein it would not reset before crafting a new recipe.
- An issue with Crafting Solver, wherein it would spam Observe-ToT rotation in attempt to regain 92 CP for Master’s Mend with less than 0.1% probability.
- An issue with Crafting Solver, wherein it would try to increase Quality bar even when it’s already full.
- A lot of speed optimizations are implemented for Crafting Solver.
- An issue with Fishing, wherein Miqobot would accidentally keep a Low Collectability fish under extensive mouse movement.
(If you want to prevent any consequences of mouse movement completely, please refer to Known Issues section below.)
- An issue with French, German, and Japanese versions of the game, wherein Miqobot would recognize Collectability rating as 0.
- An issue with French, German, and Japanese versions of the game, wherein Filter by Name feature of 3D Radar would not work with certain Unicode characters.
- An issue with French, German, and Japanese versions of the game, wherein fish name would appear incorrectly in the Output Area.
- An issue with 3D Radar, wherein text labels would appear completely transparent on certain hardware.
- An issue with Gathering, wherein King’s Yield 2/Blessed Harvest 2 would accidentally fire after several hits on the gathering node, wasting GP in the process.
- An issue with Gathering, wherein Miqobot would select a slot too late, after applying a skill rotation, thus making some rotations impossible to setup. From now on, Miqobot selects a slot first, and applies skills second.
- An issue with Gathering, wherein Miqobot would close the gathering window, if it was opened before pressing Start in Miqobot. This could potentially lead to losing an Unspoiled node.
Minor Changes
- Removed instructions from Navigation tab in order to give more space to navigation grid names and description area. Detailed instructions are available in the Navigation guide.
- Removed macro example from Crafting tab in order to give more space to new Crafting features. Macro example is available in the Crafting guide.
Known Issues
- An issue wherein Miqobot would fail to move a game cursor, under extensive mouse movement.
Unfortunately, this can not be fixed without code injections, and we have no plans for implementing code injections.
Miqobot is aware of this situation, and she will patiently wait for mouse to stop moving before making another attempt. She needs a small fraction of a second (about 0.25 sec) in order to recover from this issue. Under normal circumstances you wouldn’t even notice this behaviour.
If you want to prevent this behaviour completely, please consider switching the game to Windowed mode and minimizing it, when you run Miqobot in the background. Thus, mouse cursor will not be able to run over the game’s window and will not interfere.
- An issue with Crafting Solver, wherein it would accidentally try to recommend ‘Nothing’, when there is no Synthesis window at all.
In this case, crafting step would be identified as step #0, and no actions would be available.
This is a minor issue, and it doesn’t affect the normal flow of Crafting in any way.
- An issue with Crafting Solver, wherein in some rare cases it would fail a craft due to Synthesis action launched too late, and analysis not being available early enough to recover from the formula error.
Please refer to Advices section on Crafting Solver for more details.
In order to prevent this behaviour when crafting expensive recipes, we recommend making a single Synthesis step manually first, and pressing Start in Miqobot second. This way, Miqobot will analyze the Synthesis result in the beginning and prevent any formula errors from affecting the crafting solution.
- An issue with Crafting Solver, wherein a level up during the crafting process would cause the current solution to become incorrect, due to significant changes in the formulae.
This is most likely to happen when a level up takes you from 50 to 51. According to game mechanics, the effective character level changes from 50 to 120.
This may significantly alter the rotation, and Miqobot would not notice this until the next Synthesis action. As soon as the next Synthesis action is fired and analyzed, Miqobot will recover and make the Solver to recalculate the solution.
- An issue wherein a diacritic key would accidentally interfere with the foreground window, when Miqobot is in the Background mode.
A diacritic key (or dead key) is different from the others in that it alters the keyboard state on a system level, thus making it harder to emulate. This issue seems to occur only when both the game and the foreground window are set to non-English keyboard layout.
A temporary workaround would be switching the game to English layout, when you leave Miqobot in the Background mode.
Another workaround is to reassign any actions from diacritic shortcuts to some other shortcuts.
Is there a way to tell miqo “use all the power you can find” while prossesing she used “only” 25% of my cpu.
As im writing this I had some problems with the “´” (its used for hasty toutch). Im not shure but according to the patchnotes you just fixed that or am I wrong?Additionaly in the help section I read about starting the solver mid craft. Do I have to get to this point everytime or dose miqo recognize what I did and do it by here self? If not is it possible to tell miqo during the Macro function go and hit the solver now?
Im looking next into chocobo.
Didnt know this topic was free to write in^^
Yes, this topic is free of course 🙂
It is created specifically to discuss new issues and feedback.- There is no way to utilize 100% of CPU as there is no need to 🙂
Miqobot requires only a single CPU core to solve crafting in the most efficient way. The algorithm traverses all states in a strictly determined order, and each subsequent state depends on the previous calculations. Parallel processing would only make things worse and slow algorithm down 100-200 times.
- As for the issue with Hasty Touch – is this Acute Accent key? We didn’t have a keyboard with this key on our hands, so yes, it’s possible that we missed out some keycodes. We are going to add this one right away.
Could you please tell us, is this issue reproducable when typing a Macro, or does Miqobot fail to emulate this key with Solver as well?
- A combination of Macro and Solver together is a very interesting idea. We didn’t think about this yet.
No, at the moment Miqobot does not recognize what you did before. When you start the Solver mid craft, Miqobot will finish it from that point, but the next craft will be different from you did before.
Could you please describe the example, which led you to this idea?
What exactly do you want to achieve with Macro part? Are these some crafting actions that Solver doesn’t know yet?This information can give us some valuable insights into how to implement the rest of the solving algrithm.
Thank you for your feedback very much!
Ok lets move from top to bottom
1. Didnt know that, but tbh what are 1 min if you would craft stacks and stacks and.. .
2. Yes thats the Accent key.
Ok thats funny, I had a Macro that I used to do all the time and now it stops at the “shift+´,” part. So uhm i guess im not abel to reproduce it as a Macro. Still funny tho.3. The plan was to craft some 3* Potions and I was interestet what Miqo would figure out but since she cant use Makers Mark atm I was planing to do the MaMa rotation and then kick in the solver since it reacts on everything witch is awesome. I cant make a whole macro out of it since it relies on the succsess of MaMa how many Carefull Synthesis you have to do. So the perfect thing for a smart miqo.
Ok now to the new stuff I discoverd with the new Patch.
Easy to hard:
Fisher works perfect and fish eyes works fine.
Gathering
I dont had any problems in the past with “late Blessed Harvest”, and I still dont have any issues with it. 🙂
Gathering by name+spend gp only on {} items works. YEA!^^Now Chocobo-Races
The best is now I win 8/10 races so YEA.
Choco Cure at 50% of the race was a succsess.
My settings for accelerate/decelerate:
A>99%
d<10%
Works with one exeption
On Sangolii-R300: starting on 33% (Stamina 60%) the chocobo dont accelerate. Arround 45% there is a green field so stamina back to 60% and the chocobo accelerate. So according to my phone 33+60 is not 10^^. I dont know what that is and how I can support more data. :/Else in my opinion a HUUUUUUGE improvement and Im impresst how Miqo grows.
We have sent you a diagnostics build of Miqobot with potential fix for the Accent Key (and most likely, for all similar keys as well, which seem to derive from extended ASCII-codes).
It should arrive into your forum registration email.Please check it out and let us know if the issue has been fixed. If it is, we’ll push a minor release with this fix into production.
My settings for accelerate/decelerate:
A>99%
d<10%
Works with one exeption
On Sangolii-R300: starting on 33% (Stamina 60%) the chocobo dont accelerate. Arround 45% there is a green field so stamina back to 60% and the chocobo accelerate. So according to my phone 33+60 is not 10^^. I dont know what that is and how I can support more data. :/In order for Miqobot to use Deceleration (if that’s what you mean here), the value should be slightly less than for Acceleration.
To clarify things:
- Acceleration = pressing W key.
- Deceleration = pressing S key.
- Running by inertia = nothing is pressed.
In your example, when chocobo is at 33% with Stamina 60%, the equation is:
33% + 60% = 93%
93% is between 10% and 99%, so Miqobot will default to running by inertia. No acceleration and no deceleration here.When you run over a green pad, the equation becomes:
45% + 60% = 105%
105% is above 99%, so Miqobot accelerates.To be honest, the threshold of 10% can never be achieved. It would require being at 10% Stamina in the very beginning of the race. This is very unlikely to happen, so Deceleration will never be used.
What kind of behaviour are you trying to achieve exactly?
I agree that these settings might be confusing a little, but we couldn’t find a better way to express them.
The mechanics are described in details under Acceleration and Deceleration guide.If there’s anything that can be improved, we would be glad to know 🙂
3. The plan was to craft some 3* Potions and I was interestet what Miqo would figure out but since she cant use Makers Mark atm I was planing to do the MaMa rotation and then kick in the solver since it reacts on everything witch is awesome. I cant make a whole macro out of it since it relies on the succsess of MaMa how many Carefull Synthesis you have to do. So the perfect thing for a smart miqo.
This is actually a very good idea. It’s a pity we didn’t think about it before release.
Indeed, Maker’s Mark is easy to setup with macro. We would have to implement a special command, which can be typed in the macro box, and would indicate the point at which Miqobot should switch to Solver.We will think whether merging a Macro with Solver could be possible (in the current state of Crafting module), and we’ll post more information after research.
Thank you for this idea very much!And thank you for your kind review of the new features.
It’s a great pleasure 🙂The Fix works ´but ás you migh´t see I still have the prob´lem with ´the keý showing u´p. But still thx for the quick respond.
For chocobo races I get it now and my choci runs all the time (thats what I wannet^^). It helped that I had an other example so what would be nice if you put a seconde on down in the guid.
For crafting I hope you can make this. It would be the best. (I mean you guys are the best but still^^)
Okay, I see that you still have an issue with the Accent Key.
This turns out to be a little harder to fix than we assumed earlier. It might take more time to find a solution.So previously the Accent Key was not emulated at all, making Miqobot stuck.
After the fix, the Accent Key is emulated correctly, but instead you get an issue with interference.
Am I right?First of all, I would like to thank you for your assistance and recommend downloading the latest Miqobot version from our website. We have integrated the fix we sent you earlier and pushed a minor release into production.
This release does not trigger a ‘New version available’ message. But if you right click on EXE-file -> Properties -> Details tab, you can see the full version number. The latest version is v1.2.4.3 (the previous one was v1.2.4.2).Second, we have moved the problem you encountered from Fixed Issues to Known Issues.
According to our preliminary research, the Accent Key interferes only when you have both the game and the foreground window set to non-English keyboard layout. If you set the game to English layout, the Accent Key will stop interfering.
Could you please confirm this?We understand that it’s not a solution to your problem, and we will investigate this issue further.
For Chocobo Racing, we will add more examples into the Acceleration and Deceleration section, as you suggested.
Thank you for taking the time to report the issues you found, and for making a review of the new version.
We really appreciate it! 🙂Ok so I did some testing.
You are right if I change my game to English it works fine.
The problem is that every time I press ´ Windows it self w8 for a nother key for example é. Miqo works fine with all other keys.
So I just need to change my keysettings and everything is fine. 🙂Thanks again for the help and support you guys do.
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.
You must be logged in to reply to this topic.