Forum Replies Created
-
Posts
-
I am specifically trying to cook “Miso soup with tofu”. The loop occurs when:
-Durability reaches 10
-Progress is very little to none (because of failed “Rapid Synthesis” attempts)
-There is more than enough CP to use “Master’s Mend” (200+)My character’s level is 59 (AVG ilvl:77)
Craftmanship: 490
Control: 465
The recipe level is 64.Thank you for reporting.
Yes, Miqobot may indeed fail to craft a recipe with extremely low stats. We are aware of this issue. The problem is that Crafting Solver relies on certain optimizations that might break if we include adjustments for such cases, and this could increase the solving time tenfold. We will make no promises yet, but we will try to implement additional algorithms for this issue in the future versions.In the meantime, the only workarounds we can suggest have been already mentioned in this thread:
- Remove Rapid Synthesis from the hotbar.
- Enable “Ignore Quality” setting.
I might suggest that when crafting a recipe with extreme level discrepancy, the bot calculate the minimum number of steps it would take to finish the recipe using only basic synthesis and partition the remaining CP to apply buffs and use “Masters Mend”.
Yes, the Crafting Solver already follows this general idea, albeit on a deeper level. It considers not only Basic Synthesis and Master’s Mend, but all available crafting abilities, and includes potential loops created by Tricks of the Trade.
This is the reason behind the loop behavior you encountered.According to our logging system, you have launched Miqobot on a different computer.
It appears that you also copied the catnip.license file which is the main reason behind your issue. This file stores your license code in ecnrypted format and it’s not possible to decrypt it on another computer. In order to resolve your issue, please follow these steps:- Delete catnip.license.
- Restart Miqobot.
- Enter your license code on Catnip tab.
You can find more information in this thread: Question regarding license
Depends how much work that require to be honest, maybe it just the IT developer in me.
If there is not much work to fix gatherering I would rather them to knock that out since it will be plenty value.frankly unless they are just a few days (7 or less) away from finishing the revamp i say drop it to work on something more important
Yes, Collectable Gathering was almost complete when Patch 5.41 arrived.
Shadowbringers – Miqobot StatusNOTE: also miqobot should think about letting us do some kind of Forum Polls for accurate tallying of what the community wants
Yes, we consider implementing forum polls in the future.
But since Miqobot community is very small, we think that listening to everyone’s personal opinion in the discussion format will give us better understanding of the community demand. In addition, sometimes these discussions give us alternative ideas and solutions that we would never think of.We read all forum topics and take all feedback into account.
Even if we don’t have time to answer everyone personally, you can be sure that your opinion and your requests will be heard by the development team and will affect Miqobot’s further evolution.Thank you for your kind and constructive reviews very much.
The combat system of Miqobot is not competitive in endgame and never will be.
At the moment we aim to reach 90% of optimal performance, but the cost of every additional improvement after that grows exponentially. We will continue working on them if there is enough demand.Please keep in mind, however, this is not the purpose of the Assist Mode.
Miqobot can help you progress new encounters and show decent performance in highly repetitive content, but she will never be able to surpass a human player in the raiding environment.Assist Mode is not designed for automatic activities, therefore it is not available in Scenario Engine.
The feature you ask about belongs to Custom fights and Monster grind feature pack. The combat system is still in early beta and there are several critical updates that must be implemented before this feature becomes possible.In addition, Miqobot will not be able to perform raid mechanics until we manually implement each of them in Miqobot source code. So this feature will not allow you to farm Alexander raids out of the box.
But of course, our development plans are driven by the community demand.
If the majority of users supports your suggestion, we can start working on it.Here is the current view of the roadmap for the next few months: Upcoming Features
The standard development cycle of each feature pack is 4-8 weeks.
If you would like Alexander Raid support to become a priority, please let us know which of these features we should postpone.Standard/Technical step, I’m not sure if it does it with tech step, but with standard step I’ve seen it a couple times if it starts to cast as an enemy dies it doesn’t continue hitting steps. It should continue to hit the next steps and then the finish soon as it gets to the next enemy, even if no enemies are present it should run through the steps and then hit standard/technical finish with 1 second left to go so that the buff has a chance to keep rolling into the next enemy/trash pack since the skill is now already on cooldown anyway to not let buffs potential go to waste entirely.
This behavior is already implemented for Assist Mode.
In order to activate it, please enable “Heals and Buffs” setting.The crafting system right now has an option for you to put how many crafts it will do before it stops and repairs. I think if you add a similar system for Materia extract it would be nice.
This is already possible by the means of Scenario Engine.
But all right, we will consider adding more QoL options on Crafting tab as well.since the update miqobot only goes to the general vicinity of the waypoint
Yes, this is the default Miqobot behavior.
The algorithm was never designed to arrive at the exact XYZ point every time, because without code injections this is impossible. At low FPS, your character would be constantly spinning back and forth without ever stopping at the requested waypoint. In addition, the movement pattern would become extremely unnatural, because common players never arrive at the same XYZ coordinates.
Miqobot always targets the vicinity of the destination, but never the destination itself.Before the update my Miqobot went to exact Waypoint destinations (ALWAYS stopped right on top of the waypoint)
The most logical explanation is that this behavior was caused by a third-party interference, such as antivirus or firewall, which reduced Miqobot’s performance. Such interference may sometimes introduce a lag between Miqobot’s decision and the actual outcome in the game. For example, when she decided to release the movement button, your character would continue to run forward for a fraction of a second, which in turn would lead to stopping closer to the destination.
If your antivirus decided not to interefere with the new Miqobot version, the movement behavior is back to normal.is there anything i can do to bring my miqobot back to going to the exact waypoint location’s?
We are not sure that there is a way, besides forcing the external cause to interfere again or intentionally reducing FPS.
But even if you find one, other users will still experience the same issue with your scenarios.so far away that it won’t interact with the GC delivery NPC ( sometimes its close enough to work ) and i have the waypoint as close as possible
This, however, is a different problem entirely that indeed requires attention.
We can not change the default movement behavior due to reasons explained above, but we can introduce new tools for precise positioning that will be used only when they are required, like in the case you described. We will consider the possible solutions and will try to address this issue in one of the future versions.In the meantime, the only workaround we can suggest is the one you already mentioned – specifiying XYZ coordinates manually with respect to destination vicinity.
Please note that there is no need for text editors, because Scenario Engine can send Miqobot to any arbitrary location via xyz() function. You can select the NPC, look at his coordinates on Monitor tab, and use them as a guidance to what should be put in xyz() function.also on another note in “Sohm Al” when doing the dungeon with miqobot (squadron) i get stuck on this wall
This issue usually indicates that there is a keybind conflict in your game settings.
You can find the detailed explanation of this problem in our Keybinds and Icons Recognition guide.Our Tech Support can analyze your keybind mappings and identify the exact cause.
If you require technical assistance, please contact us directly: https://miqobot.com/#supportPlease contact our Tech Support and we will do our best to help you: https://miqobot.com/#support
Yes, Triple Triad support is planned, but at the moment it is not a priority.
There hasn’t been a lot of requests to increase its priority in the past few years.But of course, our development plans are driven by the community demand.
If the majority of users supports your suggestion, we can start working on it.Here is the current view of the roadmap for the next few months: Upcoming Features
The standard development cycle of each feature pack is 4-8 weeks.
If you would like Triple Triad support to become a priority, please let us know which of these features we should postpone.Jumping in AoE omens indicates that Miqobot tries to activate movement actions but the character does not move. Miqobot identifies this case as a potential obstacle and activates jump in attempt to overcome it.
But if there is no obstacle, then this problem is most likely caused by a keybind conflict.
Our Tech Support can analyze your keybind and hotbar setup and identify the exact cause.Yes, Identical Cast support is already planned for implementation.
It will be a part of the upcoming Gathering updates:Thank you for your request.
