Forum Replies Created
-
Posts
-
Of course, we will consider your feedback.
The main problem is that implementing even a single perfect rotation may easily occupy two years of development, due to unlimited optimization potential provided by the combat system of Final Fantasy XIV. This is why complex theorycrafting guides exist in the first place.
However, we believe that this system was not designed for an AI to beat it. It was designed for human players who enjoy optimizing and adapting their rotation for each raid encounter. And if we go too far down this path, we risk drawing unwanted attention and decreasing the value of the game itself.If our users decide that it must be done, we will of course follow the demand.
But we sincerely hope that this will never become a common use case for Assist Mode in Miqobot community.In any case, we appreciate the detailed analysis and constructive feedback.
Thank you very much!Mob Farming feature is not supported at the moment.
Our community assigned a low priority to this feature due to inherent danger posed by open-world combat. Therefore we focus on implementing private instance activities and Assist Mode instead.
For additional information about open-world combat, please read this thread:
Asking the community: Thoughts on Open World Combat and User ProtectionWe will consider your voice in our development plans.
Thank you for your request!Ruin II, III or IV are not oGCD abilities, neither are the Egi Assaults.
Of course they are not. The question was what GCD spell to use to weave oGCD abilities.
During Dreadwyrm stance, Ruin III becomes an instant cast ability allowing for 2 oGCD weaves. Meaning you can use Summon Bahamut as an oGCD right after a Ruin III while Dreadwyrm stance is up.
Now if we had saved up 4x Ruin IV, we can get those used as instant casts during Bahamut without need to ever use Ruin II. Ideally we also use the final Ruin IV at the end of Bahamut phase to get our 8th Wyrmweave in, but this might be too min-max than really needed.
All right, these suggestions are more specific and this is indeed something we can work with.
Thank you for providing the detailed feedback.While working on Summoner rotation we already tried implementing it in a similar way, but we encountered multiple issues such as Summon Bahamut not triggering in time for second weave, GCD clipping, overcharging Egi Assaults, Egi Assaults going to waste due to Bahamut erasing pets, and several others. According to the preliminary development report, it could take 1-2 weeks to fix these issues and the overall gain from implementing the perfect rotation would be +1% DPS. This is the exponential cost that was mentioned earlier.
We can try implementing them again, but first we have to understand whether this is indeed what the community needs. We have recently discussed a similar problem with Machinist imperfection and Drill drift. So now we have to ask this question again.
Should we delay the release of next version for 2 weeks for Summoner optimizations?
And if we go this way with Summoner, why shouldn’t we do the same for other jobs?Yes, this is one of the guides we have been using when implementing Summoner rotation.
Miqobot tries to follow it as best as she can while keeping the algorithm reactive and adjusting on the fly. It is impossible to follow it with 100% accuracy due to multiple factors, that’s why our goal was 90% which is currently achieved.Miqo currently uses ruin II during bahamut phase, not causing a wyrmweave. Previously you could cause wyrmweave with ruin II but this has been changed since early shadowbringers and never adjusted.
We have just verified this information and we can see Bahamut reacting to Ruin II with Wyrmwave correctly.
Would you please clarify, are there any additional steps to reproduce this issue?Without consuming too much development time perhaps it’s prudent to just fix the use of ruin II during bahamut. And for future optimization if the expansion does not change it saving up as many charges of ruin IV’s as possible pre-bahamut trigger (without overcapping).
Thank you for your request.
However, it is not very different from the previous formulation. We still have to understand how to handle the contradiction described earlier.
If not Ruin II, what should Miqobot cast for oGCD weaving while both Egi Assaults are on cooldown?
If using Ruin IV before Bahamut phase is not allowed, what spell should be used to weave Summon Bahamut?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, so it’s not an easy thing to do.
We believe that dividing the number of materials by 4 and dealing with a little surplus is a minor inconvenience when compared to 4-8 weeks of new module development, therefore it is classified as QoL improvement.Thank you for your request!
Of course, we can implement additional adjustments.
But please keep in mind that rotations are already optimized to achieve 90% performance and the cost of every additional improvement after this grows exponentially. As presently formulated, the request is too broad and might take up to a week of optimization. So we will need some more specifics in order to implement your task in a timely manner.At the moment Miqobot uses Ruin IV when there is a danger of overcapping or when an off-GCD is required, regardless of Bahamut phase.
Your request is for Ruin IV to be delayed until Bahamut is summoned and at the same time for Ruin II to never be used. In this case, what should Miqobot cast for oGCD weaving while both Egi Assaults are on cooldown?Thank you for reporting.
We have verified the links and we couldn’t identify a mismatch.The entry for Brashgold Ore links to this thread:
ShB 5.2 Mats Scenario
Among other things, it contains a navigation grid for Fireheart Cobalt which appears in the same gathering node as Brashgold Ore. So we believe the entry is correct.Miqobot attempts to start the craft 30 times in a row before showing the error message. So if you see it, then she has already tried delaying and reattempting many times.
This issue usually happens under extensive mouse movement, due to the fact that Miqobot does not use code injections.
In order to prevent this behaviour, please switch your game to Windowed mode and minimize it.You can find detailed explanation of the problem in the Known Issues section:
- An issue wherein Miqobot would fail to move a game cursor, under extensive mouse movement.
Unfortunately, this can not be fixed without code injections, and we have no plans for implementing code injections.
Miqobot is aware of this situation, and she will patiently wait for mouse to stop moving before making another attempt. She needs a small fraction of a second (about 0.25 sec) in order to recover from this issue. Under normal circumstances you wouldn’t even notice this behaviour.
If you want to prevent this behaviour completely, please consider switching the game to Windowed mode and minimizing it, when you run Miqobot in the background. Thus, mouse cursor will not be able to run over the game’s window and will not interfere.
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/#supportDisplaying possible traps and detecting mimics are two different features. They are based on different algorithms and are not related.
- “Show known trap locations” displays coordinates which may or may not contain a trap.
- “Detect mimics” displays coffers which are 100% guaranteed to contain a mimic.
WHile the radar for the traps works amazing so far, i noticed that the radar for mimics stop relatively early in the run.
Miqobot stops detecting mimics after a certain point, because they are no longer detectable.
There are 3 types of mimics in Palace of the Dead:
– Bronze
– Silver
– Gold
Bronze mimics are evaluated client-side, while Silver and Gold mimics are evaluated server-side. Miqobot can detect client-side mimics only.
Early floors spawn mimics in Bronze coffers, so they are detectable.
Late floors spawn mimics in Silver and Gold coffers, therefore they are not detectable.My guess is that not that many mimics were recorded and sent to the database on higher floors. Is that correct?
No, there is no database for mimics.
They are displayed only when they are detected client-side.If i encounter these mimics. Will they get send to the database automatically?
Even if a database for mimics existed, it would not be very useful.
Unlike traps, mimics are not linked to certain locations. Instead, every coffer in PotD has a chance to become a mimic. So even if we recorded every mimic encounter, it means that eventually every possible coffer would be marked as mimic.In the past, Silver and Gold mimics were evaluated client-side, so they were detectable as well.
Unfortunately this feature was abused and used indiscreetly and because of this Square Enix fixed PotD more than two years ago:
Mimics and exploding coffers are removed from game client (May 24, 2018)We assume that you were trying to ask whether the Patience algorithm was updated.
Yes, in accordance to Patch 5.2 changes, this ability is now triggered at lower GP which allows several consecutive uses of Patience.You can find this information in the corresponding patch notes:
Miqobot v1.3.34 – Patch NotesHealer rotations are almost ready for release. It will take 3-5 days to finish them.
However, the community has been asking us to prioritize several minor adjustments and QoL improvements. This will be the last opportunity to implement them within the current development cycle, so we’ve been hoping to make time for them.
The improvements in question are:- (Tanks) Arm’s Length support.
- (DNC) Flourish / Saber Dance adjustments.
- (Melee) Hotkey for Blind Positionals setting.
- (Crafting) Resplendent Component C adjustments.
- (Crafting) Automatic pause for chat.
- (Scenario Engine) Random afkFor().
It will take about 7 days more to include these adjustments into the next release.
- An issue wherein Miqobot would fail to move a game cursor, under extensive mouse movement.
