Forum Replies Created
-
Posts
-
Thank you for initiating this topic.
It should probably be mentioned that the start of the discussion is located here: New features coming?
So it wouldn’t get lost in the archives.We will keep an eye on this thread and will adjust our development priorities according to the community demand.
Thank you for your kind words very much. It really means a lot to us.Also, as a sidenote, is it possible to have a sort of polling system for this kind of thing? Sure they can be abused but it might add a little clarity as to what people desire more/less!
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.
ah, bottom of the list. got it.
ight, imma head out.
We are very sorry about your decision.
But regardless, we wish you all the best in your future adventures.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.
