Forum Replies Created
-
Posts
-
Korean version is on a different patch schedule. At the time of writing Korea plays Patch 4.3 versus the international version has seen updates for Patch 4.4.
Therefore the reason is the same as to why Miqobot breaks after every game patch.
The memory layout is significantly different, and we would have to reimplement several critical modules from scratch. This also implies that we would have to support two versions of Miqobot and keep track of two patch schedules, which would drastically affect the development of core features.As much as we would love to help Korean and Chinese players with the tedious grind, we simply don’t have enough resources to make it happen at the moment.
Please accept our apologies.Thank you for asking!
From the technical point of view, Korean version is an entirely different game. Therefore it will take twice more work to adapt Miqobot for Korea.
At the moment we focus on implementing core features and polishing the AI.
After we catch up with the core development, we will be ready to talk about a new project.Thank you for your interest in Miqobot very much! But right now we can not give any ETA on KR version support.
We sincerely apologize for inconvenience.The event zone is unknown to Miqobot because it did not exist prior to the release of the current version.
By default, all unknown locations are locked for automation.While we can unlock it for the current event, the problem is that it’s an area of high player congestion and therefore is extremely dangerous for any kind of automation. We would highly recommend to avoid using Miqobot in this location.
We are sorry, we don’t have an ETA.
Due to the arrival of Patch 4.4 we are being overwhelmed with tech support questions and new feature requests. The amount of work in this department is unpredictable.We implement dungeons for each level tier as we make progress on combat rotations.
Next tier is level 40-50.Yes of course, custom fights are already planned. You can read about upcoming combat features in the latest beta thread.
If you wish to vote for a feature request, please reply to the corresponding topic.
We review all threads and remember all feature requests. So a new reply in a request thread is an indication for us that the request is still relevant and depending on the current state of development we may be able to increase its priority.Thank you very much!
Miqobot is fixed for Patch 4.41 Maintenance!
Please restart your Miqobot if you had it running.
Important Note.
Previous versions of Miqobot are no longer supported.
If you are still using any version below v1.3.15, please download the latest one from our website.Thank you for your understanding!
As we already explained many times, Miqobot is not a virus. Please report this behavior to your antivirus vendor.
We kindly ask you to avoid creating duplicate threads.
If you wish to continue the discussion, please use the existing one: miqradar.exe showing as virus (a follow up)Thank you for providing the requested information!
We have converted your message log into an attachment for convenince.The cause of your issue is now obvious.
(9:12:19 AM) Yes, crafting SUCCESS! (15/36) (9:12:21 AM) Meow, repair time! ^_^ (9:12:30 AM) I want to craft! Where is your Crafting Log?You enabled automatic repair feature after every 15 crafts. To perform this action, Miqobot has to close the Crafting Log and it causes reset of selected HQ materials.
In order to fix this issue, please use one of the following solutions:
- Either disable repair feature when using custom HQ material selection.
- Or use Scenario Engine to set the desired NQ:HQ ratio.
You can read the documentation of setCraftNQHQRatio() function directly in Miqobot by pressing?button.
An example would be:nqhq(0:1) craft(99)
Would you please give us more information about your issue?
- Show us a complete message log starting from “Hello! I am your Miqobot!”
- Show us a screenshot of the settings you selected on the Crafting tab.
Even if you do not see anything unusual in the log, our developers still need it to be able to investigate your issue.
Sometimes the problem can be identified not by the messages shown in the log, but by the ones that are missing. Since we know Miqobot logic flow, we can analyze the actions that were expected to happen but for some reason failed.Please do not neglect saving the message log, it’s extremely important if you want us to be able to help you faster.
