Forum Replies Created
-
Posts
-
We are sorry, but this information is not enough to identify the problem. We will require some additional details.
Please contact our Tech Support and we will do our best to help you: https://miqobot.com/#supportMiqobot rotations are based on the guides created by The Balance Discord community.
In certain cases, however, we can not optimize them to match the guides with 100% accuracy, because the required algorithms become too complex. At the moment we have reached 90% of optimal performance, but the cost of every additional improvement after this grows exponentially.Drill drift on Machinist is an example of a problem that might require another 4 weeks to address with the potential outcome of +0.5% DPS. That is why the community requested an option to disable the GCD queueing algorithm on Machinist. The details have been discussed in the main feedback thread.
We don’t describe rotation rules in details for two simple reasons:
- It will take a few months to explain all of the decisions that Miqobot follows under different conditions.
- Every new version introduces new decisions and adjustments based on the community feedback, therefore this data will become outdated very fast.
However, when there is an issue with a certain ability of a certain job, we will do our best to provide all the necessary information.
In this case we have to investigate your issue further.
Please contact our Tech Support directly: https://miqobot.com/#supportdeliverCollectables() function does not detect scrip limits explicitly.
However, after 4 ingame errors are displayed, the function will stop and break scenario flow.
If you specify “ERR_IGNORE” as parameter, the function will stop but proceed to the next scenario line.Full documentation is available directly in Miqobot. Press
?button to open it.Since the “last” update most of my crafting macros doesn’t work anymore cause it seems like Miqobot doesn’t want to use keybinds like “ctrl+spacebar” or “shift+spacebar” anymore. It was working fine up to 1.3.42, but now in 1.3.43.1 it just stop in the middle of the macro without error message or anything. I didn’t try in 1.3.43.
Is there a way to fix this on my end?
There has been no changes to the Macro Crafting feature in the latest update. Everything works exactly as before.
Please note that “spacebar” is not the correct syntax for Space key. It has to be entered the following way:
{space}
And the keybinds you mentioned should look like this:
–ctrl+{space}
–shift+{space}If this information doesn’t help, please contact our Tech Support and we will investigate your issue further: https://miqobot.com/#support
miqo Resplendent tool Recipe Is it working properly?
We don’t know the answer to this question. Crafting Solver has not been tested with new Resplendent recipes:
Shadowbringers – Miqobot Status
If you attempt to craft them with Miqobot, please let us know how it goes.We don’t know the answer to this question.
As it is stated in the main status thread, Crafting Solver has not been tested with new Resplendent recipes.
Miqobot will correctly identify them and may attempt to craft them (as in she probably will not crash), but please do not expect anything. We don’t know how Crafting Solver will behave and what the outcome will be.
If you are planning to craft Resplendent recipes with Miqobot, please do it at your own risk.There is no active voting period at the moment.
We don’t know what new features the Endwalker expansion will bring and what the community demand will be. All we can say is that Level 81 Dungeon support has the highest priority, because it is a crucial feature that will unlock access to level 90 content for the development team. And this is not a thing to vote for or against, because any other choice will simply be inefficient.
The priority for other features will be decided by the community after Level 81 Dungeon is implemented.
By the time it will be ready, the community demand will most likely change several times, so any decision made today will be outdated.If possible. Have it hold Flourish if Technical is either available, or will be within… around 5 seconds?
Very well. This shouldn’t be hard to adjust.
That is fine. However, is it possible to have that change when your own Technical Finish is up? It can shoot to 100 incredibly fast if you let it get that high during technical when in a full party, leading to wasted Espirit. So having it be used highest priority when it reaches 80 or 71+ during technical should alleviate that.
All right. Shouldn’t be a problem either.
However, with very few macros/tweaks the Physical Ranged jobs were able to perform incredibly well in Savage with very little adjustment. They were the stars of assist mode, leading to rankings in the high 50s-70s on fflogs when in a BiS set of gear. It has been a great tool during progress, and nights where you need some extra help.
This is an interesting feedback.
While it is a pleasant thing to know, we would prefer if this wasn’t a common environment for Assist Mode in Miqobot community. It wasn’t designed to perform in Savage content and we can not make any promises that it will get better in the future. The arrival of Endwalker expansion might alter the way rotations work and we might not be able to achieve even the same level of performance.In any case, if you have managed to augment Assist Mode without 71+ abilities support, you can simply put them on a separate hotbar, instruct Miqobot to ignore it, and use the same macros and tweaks you used before.
Sometimes it looked like as much as 1/4th of the GCD was left when standard would come off cooldown, but Miqo would still choose another action.
Queueing is triggered at 96-100% of GCD cycle, which is approximately 100 ms before it becomes available. If there was 1/4th of the GCD left, it means that Miqobot would have to wait at least 500 ms more and clip the GCD on purpose.
It just feels like something is ‘wrong’ with or without GCD queueing enabled as compared to the previous patch.
The most likely explanation is the removal of GCD clipping that was previously occuring in Miqobot rotations.
Without GCD queueing, Miqobot waits for the icon to charge at full 100% before triggering the necessary keybind. There is a delay of 25-100 ms after every GCD cycle, which leads to an overall GCD drift.
With GCD queueing, this drift is removed and everything rotates slightly faster than before. Since the cooldown of Standard Step is not tied to skill speed, it may indeed arrive at different time within the GCD cycle. But this means that the cycle itself shortened, and the misalignment occurs due to increase in rotation speed.For example, if Miqobot triggered 11.75 GCDs within 30 seconds previously, now she fits 12.25 GCDs into the same period of time.
Another suggestion that I’m not sure is implemented or not would be to have Miqo focus on using a proc with the shortest remaining duration.
We can try making this adjustment as well, but it conflicts with another important rule. AoE procs have a higher priority than single-target procs, because they have a short range requirement. If we remove it, there might be cases when your character is forced to disengage from melee range and Miqobot misses an opportunity to trigger AoE procs.
This section was more of a potential bug report. Because there sometimes would be enough of the GCD recast left when Standard came up for Miqo to hit it. Instead choosing another regular GCD.
Of course, we can investigate this issue and try to find a solution, if you believe it’s really important.
However, please keep in mind that implementation of the GCD queueing system took more than 4 weeks and the result is +2% DPS on average. Addressing the issue with ability misalignment will probably take another 4 weeks with the potential outcome of +0.5% DPS. This is the exponential growth of improvement cost mentioned earlier.Recently the community has been asking us to shift the development focus on Scenario Engine, and new dungeons support, and perhaps even Triple Triad, and several other features. But unfortunately, our resources are limited and we can not work on everything at the same time. So we have to choose carefully what feature pack we are going to improve next.
Regardless, we are very grateful for the constructive feedback.
We will try our best to implement your suggestions.Now Miqobot will pop Flourish the second standard step goes off, but before using Technical. So It’ll Flourish, then start dancing, wasting precious seconds of the procs gained from Flourishing. This is a guaranteed loss of at least one proc.
Would you please clarify, what adjustment do you propose?
Should Miqobot replace Flourish with Devilment? Or should she delay both until Technical Step is complete?In the opener, you want to start your standard dance 15 seconds before pull.
There is no such concept as “opener” in Miqobot.
Assist Mode is based on a seamless list of rules that Miqobot follows regardless of the rotation phase. If you wish to optimize your DPS output, you have to perform the opener manually.I also am not sure when the bot is wanting to use Saber Dance.
Saber Dance is used when Espirit gauge is above or equal 81.
This is compounded even more in any endgame content.
The combat system of Miqobot is not competitive in endgame and never will be.
At the moment we have reached 90% of optimal performance, but the cost of every additional improvement after this grows exponentially.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.Regardless, we continue working on adjustments. Please clarify how the rotation can be improved and we will try to implement your suggestion.
There is also an issue with the new GCD queueing and timing of some moves.
If you don’t like the GCD queueing algorithm, please feel free to disable it in Assist Mode settings. This is exactly why the community asked us to implement this option.
I think the highest priority should be working on level 90 rotations
In order to implement level 90 rotations, we will have to level up all jobs to 90 first. And doing it without Trust Dungeons means an unnecessary large amount of manual work.
Unless you agree to spend the first few months of the expansion without any updates in Miqobot, we would like to avoid inefficient choices.Level 81 > 90 > 85.
Please keep in mind that if you select this order, then the community will most likely vote against implementing the level 85 dungeon when the time comes.
The release of new expansion will bring several weeks of complete Miqobot downtime. After that, each dungeon will require a full development cycle of 4-8 weeks. And if you wish to see level 90 rotations, it will take another development cycle. So by the time we finish the roadmap you propose, the game will be approaching Patch 6.2.
Yes, this feature has been requested, along with other improvements: Fishing wishlist
Some of them have already been implemented and additional options for advanced fishing are planned in the future.Thank you for your request!
- Nop, i don’t see errors in the log but i’ll try in few hours
- Less than 10 but i’m not full and i keep 5 empty slots to avoid the inventory full message cast from the game
Thank you very much. We now have an idea of what might be causing this problem. We will try to address it in the next version.
In the meantime, please use the workaround of activating deliverCollectables() twice in a row.
We apologize for temporary inconvenience.How do i avoid having miqobot using ley lines on black mage. I tried unselecting using heals and buffs and it still drops the ley lines.
At the moment there are four possible options:
- If you don’t wish Miqobot to use a certain ability, you can remove it from your hotbar.
- If you still wish to be able to use it yourself, you can put it in a macro and hide it behind a different icon.
- If you need to see the cooldown as well, you can put it on a separate hotbar and tell Miqobot to ignore it via Advanced Settings – Ignore Hotbar.
- Alternatively, you can place it on a Cross Hotbar. Cross Hotbars are not evaluated by Miqobot.
If neither of these methods work for you, then we don’t have any other suggestions.
New dungeons support is already at maximum priority in our development plans for Endwalker.
But these dungeons do not exist yet. It is physically impossible to start working on them before the expansion is released.
So we are not sure what you expect us to do with additional requests regarding this feature.
