Forum Replies Created
-
Posts
-
When crafting stops – for any reason – the craft() and repairNpc() functions (as I understand the documentation) will not abort the scenario, so once all materials are consumed the scenario will endlessly attempt to repair my zero damaged items.
The function craft() detects the moment when no materials left and skips the synthesis.
The function repairNpc() takes a few seconds to verify that repair is not required. So Miqobot would spend 15-20 extra seconds to repeat this process 5 times.Related to that, would there be any notification to me when that happens?
Not at the moment, but this is a known bug. There should be. We are planning to address this issue soon.
If I were to use a scenario like this, as best I can tell I would need to change the crafting recipe manually when it’s done, since there’s no way to say “once this cannot be crafted, move on to this”.
The function recipe() allows switching to another crafting recipe when necessary.
But that works because I have a predetermined fixed-size list of steps to follow without needing to make any decisions
A scenario does not have to be a script set in stone.
We designed Scenario Engine with simplicity being a priority in order to allow easy modification. For simple tasks like crafting and repairing, modifying a scenario takes only a few seconds. You can calculate the number of iterations you need today and put this value in repeatChapter().What I’m getting at, I suppose, is that scenarios are powerful and absolutely do solve a lot of custom situations. But they don’t, and possibly can’t, solve all of them, at least not without the devs putting in a whole lot of work to make them a lot more complicated… which would also then make them harder for a lot of people to use.
Yes, you are correct.
Scenarios can not solve all possible situations. But neither can UI settings.
Implementing your suggestions would require the same amount of work as implementing new scenario functions. Scenario functions, however, do not impose additional overhead in the UI layout. Hence our interest in the reasons you wish to avoid scenarios.We are sorry, but we can not identify your issue based on this description. We would require additional details.
Please contact our Tech Support and we will do our best to help you:
https://miqobot.com/#supportWould you please clarify, why do you wish to avoid using scenarios?
Scenario Engine was created in order to satisfy an extreme variety of custom requests, such as this one. It is physically impossible to implement an additional UI setting for every minor QoL request, therefore we created a simple scripting engine that would offer a flexible way to customize Miqobot behavior.
A simple scenario would be able to do exactly what you ask for:
craft(200) repairNpc() repeatChapter(5)Finally, would it be possible to make Miqo detect the durability of equipped gear in order to repair when items are getting low? Rather than “repair every X crafts”, a damage threshold to say “repair when any equipped item is at or below X% durability” wouldn’t even need to be adjusted as you improve your gear.
Yes, this is something we have planned for the future.
It will require an inventory management module, which a significant investment of development time on its own. We will try to make it possible.
Thank you for your request.I absolutely love Miqobot, and I hope to keep using her (and see her grow!) for a long time! To the devs, thank you for all the time you’re putting into this, and for such a user-friendly licensing arrangement at a relatively low price. Miqobot is best bot!
Thank you for your kind words very much.
Yes, it is a known issue stated in the main status thread.
Known Issues
- Stack Desynthesis is not supported.
New algorithms are in development and will be available in the next version.
We apologize for inconvenience.This issue usually indicates that there is a third-party driver installed, which is common for specific mouse or keyboard hardware.
It’s not related to Miqobot directly, but it is known to behave differently with certain overlay windows such as 3D Radar.In order to avoid this issue, please open Advanced Settings and set the following:
3D Radar -> Draw Method -> Always on Top.
This method is selected in Miqobot by default.Thank you for providing the requested information. We should be able to reproduce the problem now. It appears to be the result of a rare combination of expert crafting conditions which occurs once every 100,000 crafts. It will be addressed in the next version.
Thank you for your assistance very much.This is good.
No, they do not overwrite.
There should be two files next to Miqobot application: miqo_crafting.log and miqo_crafting_solver.log. Please put them both in ZIP or RAR archive and attach here or send to our Tech Support email. Our developers have the necessary tools to analyze the log files, so they will be able to find the matching log entries.Yes, Crafting Solver has been recently upgraded and is compatible with Patch 5.3.
You can find the most relevant information in the main status thread: Miqobot v1.3.34 – Patch NotesHowever, please note that Patch 5.31 will introduce new recipes and we don’t know how complex they will be. It is impossible to predict whether Crafting Solver will be able to solve them.
Yes, we are aware of this issue.
This debug message was present in all previous versions as well. It occurs when the confirmation window takes too much time to load and Miqobot starts analyzing it before it loads completely.This is just a minor debug message which does not affect Miqobot’s performance.
We apologize for inconvenience.
