Forum Replies Created
-
Posts
-
So if i get it right it will delay level 80 rotations by extra 2 weeks which basically puts them after 5.5 right?
Yes, this is correct.
Is there anything else we should know?
This should be the complete list of things to keep in mind:
- Implementation of the dungeon will take 2 weeks after the event starts.
- Working hours will be doubled. We will burn through the available resources twice faster.
- Level 80 rotations will not be released until several weeks after Patch 5.5.
- The dungeon layout and boss mechanics will not be fully optimized.
- Wipes will be more often than usual.
- Melee roles will perform poorly and may have problems with navigation.
- High mastery of squadron tactics will be required.
- Low gear level will not be supported.
Please let us know if you agree to these conditions.
We have to make the final decision by the beginning of Moogle Treasure Trove. The voting period will last for 3 days.I think you need to give the community tools, and not do everything yourself (there are many of us and it is not difficult for us).
As an option:
1) create combat profiles for classes.
2) create dungeons
3) create normal scripts.
and much more.Yes, this is one of the things that we have tried to explain many times.
Tools like these are on a different level of complexity. Creating an API to run arbitrary instances requires a lot more work than implementing a single dungeon. We are talking about 6-8 months of development for a beta version.Of course, if this is what the community requires most of all, we can postpone other features and start working on it.
But so far, our users have not agreed for such sacrifice.In general, here you can paint everything for a long time, I think the most effective communication now is in discord, voting, announcements, questions and answers, everything can be done there and it is much better than a forum.
Yes, we agree.
However, we don’t have human resources to host an additional community channel.We would suggest to return to the main question of the topic.
Would the community prefer Moogle Treasure Trove support to be released sooner or not released at all?The standard development cycle of each feature pack is 4-8 weeks. so how long has this been in motion for meow?
It has been this way since the day of Miqobot creation.
Also am I understanding that you do every class easiest moves up to harder moves, instead of just focusing on one whole class first?
Yes, this is correct.
Personally, I also wouldn’t mind have a “force single weave” as while playing WHM every single time it tries to weave out of Dia or any of the two lilies, it’s going to clip and sometimes it wants to double weave between Glares, which is just nuts and leads to 6seconds of GCD rolling dropped for no reason.
WHM rotation does not include any kind of weaving algorithm.
When Miqobot plays a healer job, she prioritizes healing regardless of the GCD cycle. Weaving optimization is not implemented for healers, because it would interfere with keeping the party members alive and somebody would die.I would say, either add an option to limit weaving to one oGCD, or to have conditions for only weaving on WHM while using instacasts that allow you to effectively heal. Let’s say the bot really feels like now’s the appropriate time for Asylum or Lucid Dreaming (or as it sometimes happens to me, both at the same time), have it think upon the Dia counter, would it be more effective to early refresh Dia so you can weave those two in perfectly? Would it be okay to spend one Lily to create a weaving instance? (If you have two lilies this is acceptable imo)
While we could implement these rules, it would be too risky to include them in a default rotation algorithm.
These adjustments will require new tools for precise rotation customization, which are planned in a separate development cycle. Other features have higher priority at the moment, but if the majority of users request similar adjustments, then of course we will implement them sooner.
Thank you for your request.At the moment Miqobot does not support any dungeons included in the upcoming Moogle Treasure Trove event. And it’s currently not possible to create a custom scenario due to the complexity of mechanics.
In order for such option to appear in Miqobot, we will have to implement all dungeon and boss mechanics in the form of new algorithms during a standard development cycle.Usually this process takes about 4-8 weeks.
However, since the event will be completed by that time, there will be no value in this feature this way. Therefore we will have to rearrange our development resources in order to fit this amount of work in 2 weeks.Unfortunately, our community does not understand how complex this process is and what sacrifices will be required.
At the very least, it will postpone all other feature packs currently on the roadmap: Upcoming Features
We have a history of extremely negative feedback from every time when time-sensitive features were involved, so we are not sure if there’s a reason to do it again. If the community reacts the same way as it was during Grade 4 Expert Recipes release, then we would prefer to make a statement that this feature is simply impossible.For now, we are open to suggestions.
I noticed you’re now moving onto lvl 80 rotations! which ones you plan on doing first?
We implement rotations in the order of algorithmic complexity. The easiest abilities get implemented first, and those that require complex decision making are implemented later.
How long will it take to implement them all?
The standard development cycle of each feature pack is 4-8 weeks.
is there a way to make miqo not weave so many skills in between GCD?
At the moment there is no way to adjust the number of oGCD being weaved.
Double Weaving appears to be a generally accepted standard, and this is the first time we have received such request. Would you be able to clarify the reason behind it?Will the new class Sage be done as well?
Yes, of course. When Endwalker expansion is released, new classes will be analyzed and implemented as well. But we can not implement them before their appearance in the game, if that’s what the question was about.
and finally keep doing the work you’re doing it’s great!
Thank you for your support very much.
Also! is there a way to make it so Auto assist gets turned off while in game instead of having to bring her menu up???
Yes, you can use a hotkey feature to toggle Assist Mode on and off, as it was described above.
You can also find additional information in our guide: Assist Mode – SettingsIn order to select a game instance, please switch to Monitor tab and click
Attach Tobutton.
You can find additional information in our Help section: Monitor – Attach ToMiqobot saves your license code in catnip.license file in encrypted format.
If you wish to enter a different license code, please follow these steps:- Delete catnip.license.
- Restart Miqobot.
- Enter your license code on Catnip tab.
This file will always be used by default for the first Miqobot instance you launch.
If you launch a second instance and enter a second license code, it will be saved in catnip.license2 file. This file will always be used for the second Miqobot instance.There is no public list at the moment, because the number of QoL requests is quite large and keeps increasing. It has already passed the count of 200, therefore it’s rather problematic to list them all.
To name a few, QoL updates include a status bar, an automatic pause for chat, an ability to rearrange presets with drag-and-drop, presets search, UI customization, additional hotkey customization, and multiple other tweaks and adjustments. You can perform a forum search with this keyword to see all posts mentioning it.
We also include several QoL improvements in each Miqobot release, but since it will take a lot of time to implement them all, they have a dedicated development cycle on the roadmap.
Yes, these features are already planned for implementation.
They will be a part of the upcoming Scenario Engine updates:Thank you for your request.
Thank you for reporting.
We have managed to reproduce your issue based on this description.Indeed, there is a bug that prevents certain Summoner abilities from being triggered under these conditions. Your assumption is correct. The algorithm of SMN rotation identifies Aetherpact as ready for activation and prioritizes it before everything else.
Unfortunately this issue does not have an easy fix, because the logic is rooted deeply in the rotation algorithm. At the moment Summoner oGCD abilities are not compatible with Ignore Hotbar feature.We will reimplement the algorithm in the next version.
Until then there are only two workarounds:- Hide Aetherpact behind a macro with a different icon. In this case you will not be able to see the coooldown.
- Place Aetherpact on a Cross Hotbar. In this case you will be able to see the cooldown, but there will be additional transparent artifacts on the screen from Cross Hotbar itself.
We apologize for inconvenience.
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.Please create a new thread and we will discuss it.
Here are examples of the previous community voting threads:
– Level 80 Trust Dungeon
– 61 Dungeon SupportYour bot is popular and this plays a role in this, judge for yourself the interval between resources 2h et, i.e. 0: 01, 0:02… total 120, and when the resource is collected by 130 people, there is already an overlap.
Thank you for your high opinion of our product.
But unfortunately this is not true, Miqobot is not as popular. According to the data from our logging system, there are simply not enough simultaneously running Miqobot accounts to create a problem of this kind.There is no such bullying in this game, but simple tools like RandomAfkFor (6:00et/0:10) should be, chaos is needed, people are not perfect.
I doubt that for the sake of a random time delay, you will need to change all the development plans, this is only 1 command.
All right, if a single scenario function will resolve this issue, then it’s not a problem indeed. It will be implemented it in the next version.
Thank you for your request!Would you please clarify your request?
Do you ask us to postpone all other feature packs and rearrange the development plans in favor of Scenario Engine updates?We can do this, of course, if this is what community requires most of all.
But we need a little bit of constructive feedback to make this adjustment.Our server sends the license code to you automatically after purchase. Please make sure that it doesn’t end up in your Spam or Junk folders.
And of course, our Tech Support can easily resend it to you.Please contact us directly and we will help you: https://miqobot.com/#support
According to your screenshot, your settings for Gather by Name are effectively blocking the rotation.
Using curly braces {} in Gather by Name prevents spending GP on anything other than items inside the braces. If your intent is to use rotation on all possible items, please remove curly braces {} from items in the list.
You can find more information in the Help section: Gathering – Gather by Name
