Forum Replies Created
-
Posts
-
Indeed, according to your KEYBINDS.DAT, there are arrow keys assigned to Move Cursor actions and Ctrl+arrow keys assigned to Point Camera actions. This is the keybind conflict and is the cause of your first issue.
Thank you for confirming that the first issue is resolved.As for your second issue, you have to enable one of two solutions that will allow Miqobot to detect far away nodes:
- Use compass. It requires Lay of the Land / Arbor Call on your hotbar.
- Use grid with beacons. Beacons are placed by grid creators manually.
Both methods are described in our Gathering Guide.
Yes, we are planning to implement a smart food consumption algorithm, which will verify the current buff status and prevent consumables going to waste.
You can see it in this section: Planned Functions.In the meantime, as @gregye suggested, you can use sendIcon() function to imitate this feature.
Please be careful when using it this way and precalculate the expected repeat count accordingly.Thank you for reporting.
Your issue seems to be caused by a keybind conflict. Keybind conflicts are not detected by Miqobot as this would result in a significant performance penalty. Please read our guide on Keybinds and Icons Recognition.
Recently our community has found a very good way to address this kind of issues.
You can read about it here: Gathering Issue.As Lyfox suggested, you have to locate your KEYBIND.DAT in the game configuration folder and upload it here. (Don’t forget to archive it as direct .DAT attachments are not allowed.)
Config File Names and Descriptions (reddit guide)
One of us will take a look by replacing his own KEYBIND.DAT and will help you resolve the issue.Yes, there is a new navigation system already in development which will look more organic and similar to what you describe.
Though we can not promise to eliminate the concept of waypoints and lines entirely, the new system will be more flexible and provide more navigation freedom.You can find more information in the following threads:
– Make movement smoother
– Suggestions to make miqo more human
– Feature Request: softer gridsThank you for your request!
The main obstacle we mentioned a long time ago still stands – unlike crafting, there is no absolute solution in gathering.
Depending on the item or the indended usage of the item, you may want to maximize yield, HQ rate, collectability rating, EXP per hour, scrips per hour, or several factors at once in a certain ratio. In addition, you may want to gather different items and apply different goals for each of them.Implementing a Gathering Solver similar to crafting would result in extremely complex UI which would be very hard to setup.
We think that the current toolset of Gathering Rotations Designer combined with Scenario Engine provides a reasonable trade-off between complexity and flexibility.Therefore instead of creating an entirely different system, we will focus on improving the current one by introducing new functions to Scenario Engine (such as conditional rotation selection, smart consumables usage, smart NPC interactions, and many others).
There is no option in the current toolset to break the scenario when a crafting activity fails.
However we are planning to implement a smart food consumption algorithm, which will verify the current buff status and prevent consumables going to waste. You can find it here: Planned Functions.In the meantime, please be careful when imitating this feature and precalculate the expected repeat count accordingly.
Thank you for your feedback very much!
I dont know if this is linked to an update, but my bot recently cant craft. it keeps searching for the crafting log, opening it and closing it over and over again.
We have finally managed to reproduce your issue. It is confirmed that it was caused by intervention into game memory by an external program, such as antivirus or firewall.
The hotfix is already implemented. Just restart Miqobot and she will upgrade automatically.
We have confirmed that this error is caused by the same issue from here:
Error: Array maximum size exceeded.The hotfix is already implemented. Just restart Miqobot and she will upgrade automatically.
Thank you for reporting very much.Thank you for your answer very much!
We have managed to perfectly reproduce your issue. It is caused by a combination of two factors:- Slightly incorrect memory reading.
- Intervention into game memory by external program, such as antivirus or firewall.
The hotfix is already on the way and will not require any redownload.
Would you please give us more information about your issue?
Please answer these questions:- If you switch to Monitor tab, does Miqobot crash as well?
- If you restart the game, is the issue still present?
- If you restart PC, is the issue still present?
We are currently investigating several reports which seem to be caused by the same problem. But we need more information in order to identify and solve this issue correctly.
Thank you for your assistance very much!
guys I know that you are toooooo busy to answer this but can you tell us how far have you done in stage 2
We are sorry, but as we already said earlier it is impossible to provide any kind of numeric progress, because literally every feature requires additional research and implementing new mechanics.
We will make announcements as soon as we are ready to share new information.
Thank you for your patience and understanding!
