Forum Replies Created
-
Posts
-
Can you fix BLM’s AoE rotation? Miqo keeps using Blizz3 instead of Freeze and wasting GCDs on Fire II even at level 80.
Yes, Freeze and Enhanced Umbral Heart trait will be implemented in the next update.
hate to ask but any possible way to know an eta when it will be released? a week? 2 weeks? a month? 2 months? I’d like to manage my expectations. thank you.
Same, at least for combat rotations.
Approximately 2-3 weeks.
Thank you for your kind feedback very much.
Perhaps you’re right.
But from what we see at the moment, users expect that Crafting Solver will be able to synthesize 80** recipes in the most optimal way by utilizing the least possible number of steps with minimal stats from zero starting quality and without any CPU intensive settings. This is not correct.Number of steps will never be a part of the algorithm, because it would result in combinatorial explosion of the solving time.
And CPU intensive settings will always be required to perform high-level synthesis efficiently.If the next upgrade of the Crafting Solver turns out not perfect enough, the majority of users will keep using macros and the time we invested into its development would be essentially wasted.
So before we decide to accept this risk, we would like to see more opinions on the matter and understand the community demand.In the meantime, we will focus our efforts on more popular features such as Combat Assist and Trust Dungeons support.
i was so elated when i saw the miqobot status thread updated only to fine it was just for compatibility for the patch.
Please do not underestimate the amount of work required to upgrade Miqobot for new patches.
We don’t think that leaving Miqobot broken after each patch would be a reasonable solution.i just want the solver to use 70+ skills. with no eta ive lost hope itll drop this before end of year. Keep seeing ‘in a couple weeks’ since july.
Based on the feedback we received in Stormblood, upgrading the Crafting Solver for level 80 tier is now at the bottom of our priority list.
Most players who are interested in crafting consider it a challenge rather than a grind. This activity gives unimaginable freedom for theorycrafting, so much that it generates the whole communities focused on designing macros and breaking down requirements for all recipe tiers. That’s why when the Crafting Solver was finally updated for level 70 tier, it was received as a threat to human intelligence rather than a helpful assistant in eliminating the tedious grind.
The game community was constantly competing with Crafting Solver, attempting to prove that human is superior in solving this problem, either in speed or in quality. And only 30% of our users accepted this feature for its original purpose.We are not interested in initiating another series of emotional debates related to Crafting Solver performance. If we do not update the solver for 80** recipes, players will not feel threatened anymore and will not try to compete with it.
Here is an example of discussions that discourages us from making further progress:
– Useless Crafting Actions
– tips for facet gearIf you wish to change our impression on this matter, we would like to see more constructive feedback. Thank you!
Yes, Combat system is the topmost priority.
It has already been delayed in favor of DoL/DoH update during the first two weeks of Shadowbringers.
But our development plans are flexible and we may adjust them even further depending on the community demand.As of this time, more than 80% of requests are combat related.
If you wish for a certain feature to arrive sooner than others, please voice your opinion in a corresponding thread. Thank you!The Shadowbringers expansion has introduced an immense amount of changes and completely revamped the combat system. Please do not underestimate the amount of work required to upgrade Miqobot for new patches.
We have already invested 1,000 development hours into new combat rotations and the next version requires 500 more.
It will arrive approximately in 2-3 weeks.Please refer to the main status thread for updates: Shadowbringers – Miqobot Status
When farming Squadron Dungeons, Miqobot uses navigation meshes instead of grids.
You can find visual examples here: Combat | DevelopmentFirst, we have to upgrade the navigation system and release a new 3D Editor for navigation meshes.
And then yes, it will be possible to implement additional scenario functions for custom fights.Thank you for your request!
Is there any way you can allow us to us the Holminster Trust Zone ID? It’s super simple to make a scenario that farms the first 4 or 5 mob pulls before the boss and it’s better EXP than doing Sohm Al. Send Key scenarios work if started in the trust, but if you use the scenario to enter the trust it does a Blackout Error upon entering the instance.
Please contact our Tech Support and we will try to find a solution: https://miqobot.com/#support
I would LOVE to see a Pause button for the Scenario tab.
Yes, this feature is already planned.
But first we have to upgrade the navigation module to be compatible with pause. It will take a few more updates.Well duh! I just realized this group of nodes has its ephemeral node, just nobody cares to harvest it, so I didn’t even notice it before. So basically this is the same “backtrack here and there while ephemeral node is spawned” bug I reported before %) sorry!
Thank you for clarifying very much.
New mounts don’t seem to be incorporated. The Skyslipper mount doesn’t seem to register. Not a big issue and the obvious workaround is to use old mounts but it’d be sweet if it can be implemented.
Yes, Miqobot can not recognize new mounts because they did not exist when we released the previous version.
If you want Miqobot to utilize them now, please use the workaround described here: Regalia and MiqoI don’t know if this has already been brought up but Miqobot Assist just completely stops working on the last stage of Amaurot. This is with Bard btw.
Yes, this is a known issue, but it’s extremely hard to reproduce and it will take some time to design a proper solution.
This post contains additional information and a temporary workaround: #15675It seems that miqo isn’t using Shadow Fang for ROG/NIN at all. I read that its usage was updated on the status page, so maybe I’m just not meeting the conditions to trigger its usage? Any chance we can get a quick explain as to how it works? Thanks.
Shadow Fang was implemented in a rushed update on July 7 when Miqobot was completely broken. It is used when the DoT is currently absent or falling off, and when Huton duration has more than 30 seconds left. But as it always happens with rushed updates, we did not consider the case when Huton is not unlocked or when there is no Armor Crush to refresh it.
At the moment we are reimplementing all job rotations, and this issue will be addressed in the next version.I’m fully aware the current state of assist is absolutely not optimised, and don’t take into account new abilities, or if it does, it’s only through some temp fix. So, it is in full knowledge of those facts that I’m doing those feedbacks, and I know that most of the things (if not all) I’m gonna bring up are known to you developers, I’m still doing it in the rare case I would actually have found something relevant.
Indeed, the combat system is not even remotely optimized for endgame raiding. It’s quite surprising that you found it useful in the current state, considering that job rotations were significantly downgraded by the arrival of 5.0. Thank you for the detailed feedback very much!
There’s one thing I would really love we get, it is an ON/OFF green/red “light” on Miqobot window itself, just for those who don’t want to use the overlay Pause Status feature, and prefer watching Miqobot on a secondary monitor.
All right, this should be possible. Thank you for your request!
The reason I’m bringing this, despite knowing it happens now just because Assist is not finished yet, is because I want to know if you’re going to allow her to triple weave, or never, or in rare occasions by taking into account the extra delay it would add before the next Iron Jaw GCD, so that she’s sure she won’t attempt it if she sees she will fail refreshing the DoTs.
To my knowledge, there’s still only one very rare case where triple weaving is not a DPS loss with BRD, but I’m trusting you fully when it comes to numbers, and if you find other cases.In the most optimal setting, triple weaving should never occur.
The general rule that Miqobot follows is to allow oGCD if there’s more than 50% of GCD timer left. However, some abilities do not follow this rule:
– Pitch Perfect. Because clipping was the easiest solution to ensure that procs are not wasted. It must be optimized and aligned with GCD.
– Empyreal Arrow. Because Miqobot still considers it a weaponskill and tries to fire it immediately after Barrage.
With these two issues addressed, there should be no more triple weaving. If you encounter any other cases, please let us know.One other reason I’m bringing this, is that for example I pentamelded two thirds of my set to lower my skill speed a lot, and I was wondering if it was something Miqo was taking into account when she calculates the time she have left before she needs to apply the next DoTs refresh, especially when into Minuet we get now the 10 sec Skill Speed buff of Pean, making suddenly the most busy song for procs a hard place for double weave with high ping, and this is precisely where right now she misses most of the DoTs refreshes.
Varying skill speed should not be a problem, because we use the same system for Ninja and Monk. Clipping issues will be extremely noticeable on those jobs, so they will be addressed accordingly in the endgame optimization stage.
I remember you told me that for now, since she wasn’t finished, she was going to miss some DoTs refresh, that it was expected, but my concern is gear wise (skill speed) and ping wise. Should I be worried with a 165-175ms ping? I have a datacenter close to me, 20ms, but unfortunately this is not the one on which I play, most of the times though, I don’t clip when I double weave.
In general, high ping environment should not cause any significant issues, as long as there are no occasional lag spikes of 220+ milliseconds.
We will be researching this question once again when we start working on endgame optimizations.When I switched to manual for the clear, I noticed I ended up doing 8 GCD more than her, the amount I believe she lost with clipping on a 13min45sec fight.
We believe that this problem is caused by GCD not being queued by Miqobot.
The queueing algorithm is still not implemented and Miqobot activates an icon only when it is fully charged. This results in additional delay of 20-30ms on each GCD. With 250+ GCDs in total this indeed accumulates to the number of lost GCDs you mentioned.So, I believe you already planned this, but just to be sure, for those, it would be useful to have individual boxes we can check to tell Miqo if we want her to handle them or not, instead of removing their keybinds.
Of course, this is the first customization we will implement when we start working on endgame support.
You will be able to enable or disable any weaponskill or ability directly in Miqobot, without any hotbar or keybind manipulations.And this bring me to a following question, about Nature’s Minne, when we feel it’s okay to let Miqo handle it on cooldown. How is it going to be handled in the end when set on auto, will we have an option in Miqo to set which number of the party member we want it to be used on? Or Miqo will be able to recognise a Nature’s Minne macro, in which we would already have set up the party member number? Or can she sees who’s currently tanking within the party, and distribute Minne accordingly?
Miqo is quite fantastic when it comes to switching to party members as healer, it would be great if she could not rely on a macro for Minne, as those are really awful to trigger.Yes, Miqobot is capable of detecting the current main tank. And yes, it won’t be a problem to utilize the same targeting system as healers do.
Precise customization of Nature’s Minne will be also implemented in the final cooldown planning toolkit.Subsidiary question, would it be possible to manually queue some oGCD we set up to use manually? If we don’t want to fight with Miqo, and avoid making her clip when we use something manually, could we tell her we want her to use a specific oGCD as soon as she sees she has a safe window for it, either by having her recognise we pressed it with the game keybinds (and it didn’t triggered), or being able to set keybinds for those directly in Miqobot?
I really don’t want you to have to create such a system if it turns out to be a lot of work, I’m just putting in there in the case you would find the idea useful and not time consuming.This is one of the problems we don’t have a definite solution for at the moment.
As we constantly test Miqobot in different environments, we fully understand the issue you describe. Detecting a manually attempted ability and queuing it for the next GCD cycle could be possible, but we have to research it further.Miqobot saves your license code in catnip.license file in encrypted format.
Do you see this file being created next to your Miqobot application? If not, then something is blocking Miqobot from creating and managing her files.Please try the following solutions:
- Verify that the folder that Miqobot resides in is not restricted for write access.
- Move Miqobot to a different folder.
- Run Miqobot as administrator.
- Verify that your antivirus does not prevent Miqobot from creating files.
