Forum Replies Created
-
Posts
-
BLU support is one of the least commonly requested features, therefore its priority is low at the moment. For some reason, it’s not popular among the community.
Even with the arrival of Patch 5.45 its popularity did not increase.We have a dedicated thread regarding Blue Mage support.
Our development plans are driven by the community demand, so if you would like this feature to become a priority, please voice your opinion here: Blue Mage SupportWe are very sorry to hear about your issue, but unfortunately we can not fix it.
False Positive is a bug in antivirus and it’s entirely up to antivirus vendors to address it. Since we have no access to their source code, we can not help them fix it.Miqobot Team is already doing everything possible to alleviate the issue with antiviruses.
We always inform antivirus vendors about False Positives, and Miqobot project is also subscribed to premium VirusTotal services that send automatic notifications to them.
If you upload Miqobot to VirusTotal, you may notice that our executables are published in the VirusTotal Monitor collection:
https://www.virustotal.com/gui/file/137f9ae9da8345cfb5a6f84026eb2eacd841b80e6c0157764a642f8f4b0f0519/detectionAs you can see, the current installation of Windows Defender at VirusTotal does not detect Miqobot. So perhaps an update will alleviate your issue. If it doesn’t help, we highly recommend to report this behavior to your antivirus vendor.
We sincerely apologize that we can not resolve your problem.Can I make a request to not have the trap guess locations in the 3D radar for POTD/HOH disappear from the screen if you use one of the pomanders to reveal exactly where they are? Am going for the ‘find 100 undiscovered horde’ achievement and if I use that pomander then I can’t try standing on the places where I know a trap COULD be but definitely isn’t because they got revealed.
All right, we will see what we can do. However, please keep in mind that Accursed Hoards may spawn inside traps, therefore Pomanders of Sight are not the best choice of action. If your primary goal is to earn the achievement, then it’s much easier to accomplish with Pomanders of Safety.
Please refer to this post for detailed explanation:
Recommended method to earn “Of the Sixth Sense” achievementSuggestion: An option to disable the use of certain or all OGCD abilities when in Assist mode.
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.
Suggestion: Better detection when transformed using a Pomander of Rage/Lust/Resolution, so it doesn’t replace the pet hotbar with hotbar 1 because it’s trying to use abilities that are no longer available.
We will try to research and implement the necessary adjustments. But due to certain delays within the game client it may not be possible.
Please note that you can easily disable Assist Mode via hotkey in order to prevent it from doing anything when you don’t need it.Suggestion: “Prioritize Healing Self” option in Assist mode. Red Mages are squishy, doubly so in higher PotD floors. With this option on, it will heal you at 75% health instead of 50% health.
All right, we will see what we can do.
Suggestion: Vault or Fractal support, PLEASE! I don’t want to be stuck in Sohm Al Hell for 18 levels.
We haven’t discovered any viable alternatives to (Lv53) Sohm Al.
- (Lv60) dungeons give -32% of Sohm Al experience and thus are not efficient.
- (Lv57) The Vault gives +3.6% experience boost, but the wipe rate becomes extremely high due to many mechanics hitting your character for 90% HP.
If you have any other ideas, we are open to suggestions.
I’ll happily take reduced exp per hour over the monotony of running Sohm Al over and over and over and over again.
We are sorry, but we don’t understand the reason behind this request.
Monotony is irrelevant for Miqobot. Her efficiency does not decrease after performing the task multiple times in a row.1)
The waypoint-accurancy threshold is sometimes strange because it is to high.
For example if i place a waypoint on X20 Y20 Z20 miqo moves to X18 Y16 Z4.Yes, this is correct.
The algorithm was never designed to arrive at the exact XYZ point every time, because without code injections this is impossible. At low FPS, your character would be constantly spinning back and forth without ever stopping at the requested waypoint. In addition, the movement pattern would become extremely unnatural, because common players never arrive at the same XYZ coordinates.
Miqobot always targets the vicinity of the destination, but never the destination itself.My question is: is miqo using an accurancy threshold?
Yes, the accuracy threshold is approximately 2.0 meters.
Your example, however, does not fit this threshold. If you instruct Miqobot to arrive at (20; 20; 20) then the worst possible arrival would be (18.75; 18.75; 18.75) but not (18; 16; 4).If yes you may can add a way to modify it in the settings? (e.g. “normal, “most accurate”)
At the moment the only way to adjust it is via goToWaypointPrecise() function. It reduces the accuracy threshold to 0.5 meters, but only for the duration of the function. This is a scenario function, therefore its usage is rather limited.
Of course, we can implement an additional setting to adjust it globally as well. But this may result in extremely unnatural motion as described above.
Are you sure this is the only solution to your problem?2)
Miqo’s pathfinding for shortest way seams only to include the number of nodes to move by.
I dosen’t include the length of individual connections.Miqobot always calculates the length of path by the distance traveled. The number of waypoints is irrelevant.
If you experience a different behavior, then it’s a bug.Would you be able to create a navigation grid that reproduces the case in your example and export it for analysis?
Would be nice, and other form of beacon check would be nice. That the bot travels to nearest beacon and i wish a function that the bot only go to a higher Waypoint Beacon. When the bot is on waypoint 5 and there is beacon waypoint 4 and beacon waypoint 6 the bot will travel to beacon 6 everytime ^^
The beacon navigation algorithm is already implemented this way.
Miqobot traverses beacons in increasing order of their waypoint numbers.
For example, if beacon A is #3, beacon B is #7, beacon C is #11, the order will always be:A -> B -> CThis way you are always in control how you want Miqobot to visit beacons, regardless of linear distances, navigation path distances, or unidirectional connections. If you wish to change the traversal order, all you have to do is delete beacons and recreate them in the preferred order.
The only time distance calculation takes place is the moment you click “Start”.
At this time Miqobot detects the closest beacon and rotates the sequence to make it the first to visit. But the order remains unchanged:B -> C -> AIn addition, if Miqobot visits a beacon implicitly while navigating from one gathering node to another, it still triggers a sequence rotation. This rule is designed to prevent occasional backtracking when the next gathering node is visible directly on minimap and the beacon is not used.
If you have any other ideas for AI improvement, please let us know.
Two weeks have passed since the date of the previous release.
You can see this information in the main development thread: Patch NotesYes, this adjustment was specifically requested by the community:
Quick Question about WHM Regen
If you believe it is not an improvement, please join the discussion and voice your opinion.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.
