Forum Replies Created
-
Posts
-
so my questions : are those assumptions correct?
Yes, of course.
The development of new features in Miqobot can not happen before they are released in the game. We are common players, just like everyone else. So in order to implement a new game feature, we have to research and thoroughly analyze it first.will sage be considered a core upgrade or an extra?
Core upgrades do not include any new game features. Reimplementation of broken core modules is a heavy undertaking in itself. Overloading this process with new job rotations would be inefficient.
did the same thing happen when Shadowbringer, GNB and DNC first launched?
Yes, it was exactly the same in all previous expansions.
New features take several weeks and sometimes months to implement.also if youre wondering why am asking this, its coz i need to make some planning ahead
including whether or not i’ll be buying endwalker, playing sage, or even playing the game during miqo’s downtime
so its kinda important for me :3Please do not expect Miqobot to be functional during the first weeks of Endwalker expansion.
Since we are common players and do not have access to Square Enix development servers, it is physically impossible to implement Endwalker features beforehand.Would you please clarify your request?
Sage job does not exist in the game yet, it will be added in the Endwalker expansion. When it is released, the community demand will change and the development roadmap will be overhauled to match the demand.Is this the kind of information you wanted to receive?
If not, please clarify question.Miqobot knows the following Blue Mage spells:
– Blood Drain
– Water Cannon
– Plaincracker
– Mind Blast
– Bomb Toss (requires placement macro setup)
– Off-guard
– Bristle
– Toad Oil
– White Wind
– Lucid DreamingSelf-destruct combo (9+ enemies):
– Acorn Bomb + Toad Oil + Bristle + Peculiar Light + remove Mighty Guard + Self-destruct1000 Needles combo (under the effect of Mighty Guard):
– Swiftcast (when available) + 1000 Needles
– Sticky Tongue (when out of range) + Faze + 1000 NeedlesIf a spell from the combo is not present on hotbar, it will be omitted.
This list may be viable for leveling Blue Mage until about level 40, but it stops being useful after 50+.Thank you for your feedback very much.
When you vote in favor of Blue Mage support (or any other feature), please don’t forget to mention the location on the roadmap you would prefer. We have to understand the demand in comparison to other features in order to adjust the development plans accordingly.The voting period is now complete.
The results are as follows:- 16% – Moogle Treasure Trove support.
- 84% – Continue without it.
In accordance to the community demand, the development roadmap remains unchanged.
Moogle Treasure Trove will not be supported. We sincerely apologize to everyone who voted in favor of this feature.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.
