Forum Replies Created
-
Posts
-
Thank you for providing the requested information.
According to our logging system, there have been several irregular downtimes in your Miqobot application activity. This pattern usually indicates a problem in the connection route. When connection to the license server is lost, Miqobot automatically tries to reestablish it after 5 minutes. And this may indeed cause temporary freezes.We haven’t tried using miqo in there since, figured it just doesn’t support that raid yet.
Assist Mode does not have any specific zone requirements. All instances are supported.
I seem to encounter odd behavior after a few minutes of using combat assist in Delubrum Reginae. If I have miqo running with combat assist before I enter, things work fine for about 3-5 minutes. Then miqo starts to go into an odd loop where it hangs for 20 or 30 seconds over and over. Forcing it closed and reopening it, miqo no longer will allow combat assist to start (it says that some targeting keybinds are missing even though they’re set up). After exiting Delubrum Reginae, things work normally again. Anyone else experience this?
Thank you for reporting.
Would you please clarify, have you encountered this issue only once or do you experience it every time when entering Delubrum Reginae?We have already answered these questions many times, but all right, for the sake of new users we will repeat the answers once again.
I thought it was said that collectibles would be fixed within a few or several weeks after the change? It’s been how long now, and we’re still not seeing this capability?
As it was stated in the main status thread, Collectable Gathering is completely revamped and is technically a new game feature. Implementing new features takes a very long time.
It was also stated that the announced schedule was only an approximate plan and would change depending on the arrival of further patches and additional information discovered during development.
In addition, Collectable Gathering is not the only feature in development. Since then, we have released several Miqobot versions with core upgrades for new patches, Level 80 Trust Dungeon support, Grade 4 Expert recipes support, and multiple hotfixes.You can find the detailed information about the ongoing development in the main status thread:
Shadowbringers – Miqobot StatusIt just seems that we get a lot of promises, and many of them just don’t come through
We are sorry, but we do not agree.
We have fulfilled many promises and we are trying to make the development process as clear as possible, so everyone would understand why certain features require more time to implement.and now the Miqobot team is on vacation?
Miqobot Team has been working non-stop for the past 5 years without days off. If you don’t think we deserve a vacation, then all right, you are free to have an opinion. We understand that no matter how much we work and no matter how many features we implement, there will be users who are not satisfied.
But the burnout problem is real and may destroy Miqobot project if we do not allow our developers to rest.So, we’re still paying for this bot, and there’s no development being made on it?
It appears there is a misunderstanding about the kind of service we sell.
We sell features that have been already implemented, not the features that are currently in development. Please note that we do not increase the subscription price and we do not sell addons. With every new Miqobot version you have more functionality for the same price.
If you are not satisfied with the current feature pack, then of course, please don’t pay. We do not impose recurring payments, so you don’t have to make any effort to stop the subscription.I saw a post from back in 2016 that said that Miqobot would be implementing a whole questing automation, where it would do all MSQ and sidequests from lvl 1-70, but… where is that?
Our development process and feature priorities are driven by the community demand.
Since we can not implement all features at once, we implement them one by one.
Our community assigned a low priority to MSQ and Questing features due to inherent danger posed by open-world combat. Therefore we focus on implementing private instance activities and Assist Mode instead.Here is the current view of the roadmap for the next few months: Upcoming Features
These are the most often requested features, therefore they are in priority.If you have any other questions, please let us know.
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/#support
