Forum Replies Created
-
Posts
-
Might it be possible to add a parameter to diademBoom so we only target certain monsters? For example diademBoom(Diadem Coblyn) or maybe a list of monsters [diademBoom(Diadem Coblyn, Diadem Golem, Cloudtrap)]?
Yes, this is one of the features planned for the next Gathering update.
That said, even if we’re not going to get any new functionality for diademBoom in the next update, and even if gathering issues are put on the backburner, i’d like to see at least a band aid fix for the targeting problem – like excluding any target that doesn’t have a name string, or an empty one.
Yes, this feature is critical and it will be fixed in the next update.
No, there has been no changes to Miqobot source code besides the standard procedures following every game patch. The current Miqobot version uses the same game interaction methods as before.
This issue is indeed unique. We haven’t received any reports that would describe a similar behavior.
We sincerely apologize that we can not resolve your problem.I do my best to disable the combat assist function any time I’m not in combat, however, mistakes have happened and eventually will happen again. I believe this could be circumvented by having a option to disable the usage of healing actions outside of combat, or maybe by featuring a more natural delay before using such abilities. My apologies if this issue has been posted up before, but I couldn’t find it with a quick search through the forums.
Introducing a delay for healing abilities will result in a higher chance of someone dying, so we will not do this. But a setting to disable healing outside of combat could be a viable solution. We will add your suggestion to the improvements list. Thank you for your feedback.
If you experience this issue often, we would recommend to assign a hotkey for Assist Mode and enable “Show pause status” in Miqobot. This way, you will see a green / red indicator in the top right corner of the game which can be used as a reminder that Assist Mode is active.
When she’s full on Lilies she should use one for an AOE heal to keep feeding the Blood Lilly. But on the Blood Lilly, I noticed that if it pops during a time when she needs to do heavy healing, she will use her Lillies without using Misery. This I feel is a big DPS loss as she could be continuing to feed the Blood Lilly during these parts. 🙂
Would you please clarify your request? You wish that Miqobot would DPS instead of healing when Blood Lily is in full bloom, even when heavy healing is required. Is this correct?
I have also noticed that she will sit on a fully bloomed blood lily even while dpsing, preferring to just spam glare instead of using afflatus misery for some reason. End up having to force the usage of afflatus misery even when there’s nothing to heal.
Yes, this is a known issue but it’s unrelated to healing.
Afflatus Misery is triggered only when all targets from the enmity list are within the range of the spell. The AoE detection module, however, is not perfect and may sometimes yield inaccurate results which prevents Afflatus Misery from triggering properly. We are aware of this issue and it will be addressed in the future.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/#supportThis feature is a part of 3D Radar for Chocobo Racing.
In order to turn it off, please disable the following:Gold Saucer tab -> Racing -> Show -> Rails / Mid-rail / Progress / Waypoints
You can find additional information in our Help section: Chocobo Racing – Race Recording
Our hosting provider has reported that they implemented a fix for the networking issue.
Widespread Issues due to Major Upstream Provider OutageHowever, the outage at CenturyLink is not fully resolved.
Downdetector – CenturyLink
You may still experience issues depending on the location and ISP route.Our Tech Support can analyze your keybinds and hotbar configuration in order to identify the problem.
Please contact us directly and we will do our best to help you:
https://miqobot.com/#supportYes, our hosting provider DigitalOcean is indeed having problems:
https://twitter.com/DOStatus/with_replies
You may experience problems depending on which ISP route you are using.
This issue is occuring on a global scale and there is nothing we can do but wait.However, Miqobot server is currently online and functioning correctly.
All you have to do is connect via a stable ISP route.
If you still experience this problem, please try accessing Miqobot via VPN services.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.
