Forum Replies Created
-
Posts
-
Assist Mode is not designed for automatic activities, therefore it is not available in Scenario Engine.
The feature you ask about belongs to Custom fights and Monster grind feature pack. The combat system is still in early beta and there are several critical updates that must be implemented before this feature becomes possible.In addition, Miqobot will not be able to perform raid mechanics until we manually implement each of them in Miqobot source code. So this feature will not allow you to farm Alexander raids out of the box.
But 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.Here is the current view of the roadmap for the next few months: Upcoming Features
The standard development cycle of each feature pack is 4-8 weeks.
If you would like Alexander Raid support to become a priority, please let us know which of these features we should postpone.Standard/Technical step, I’m not sure if it does it with tech step, but with standard step I’ve seen it a couple times if it starts to cast as an enemy dies it doesn’t continue hitting steps. It should continue to hit the next steps and then the finish soon as it gets to the next enemy, even if no enemies are present it should run through the steps and then hit standard/technical finish with 1 second left to go so that the buff has a chance to keep rolling into the next enemy/trash pack since the skill is now already on cooldown anyway to not let buffs potential go to waste entirely.
This behavior is already implemented for Assist Mode.
In order to activate it, please enable “Heals and Buffs” setting.The crafting system right now has an option for you to put how many crafts it will do before it stops and repairs. I think if you add a similar system for Materia extract it would be nice.
This is already possible by the means of Scenario Engine.
But all right, we will consider adding more QoL options on Crafting tab as well.since the update miqobot only goes to the general vicinity of the waypoint
Yes, this is the default Miqobot behavior.
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.Before the update my Miqobot went to exact Waypoint destinations (ALWAYS stopped right on top of the waypoint)
The most logical explanation is that this behavior was caused by a third-party interference, such as antivirus or firewall, which reduced Miqobot’s performance. Such interference may sometimes introduce a lag between Miqobot’s decision and the actual outcome in the game. For example, when she decided to release the movement button, your character would continue to run forward for a fraction of a second, which in turn would lead to stopping closer to the destination.
If your antivirus decided not to interefere with the new Miqobot version, the movement behavior is back to normal.is there anything i can do to bring my miqobot back to going to the exact waypoint location’s?
We are not sure that there is a way, besides forcing the external cause to interfere again or intentionally reducing FPS.
But even if you find one, other users will still experience the same issue with your scenarios.so far away that it won’t interact with the GC delivery NPC ( sometimes its close enough to work ) and i have the waypoint as close as possible
This, however, is a different problem entirely that indeed requires attention.
We can not change the default movement behavior due to reasons explained above, but we can introduce new tools for precise positioning that will be used only when they are required, like in the case you described. We will consider the possible solutions and will try to address this issue in one of the future versions.In the meantime, the only workaround we can suggest is the one you already mentioned – specifiying XYZ coordinates manually with respect to destination vicinity.
Please note that there is no need for text editors, because Scenario Engine can send Miqobot to any arbitrary location via xyz() function. You can select the NPC, look at his coordinates on Monitor tab, and use them as a guidance to what should be put in xyz() function.also on another note in “Sohm Al” when doing the dungeon with miqobot (squadron) i get stuck on this wall
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/#supportPlease contact our Tech Support and we will do our best to help you: https://miqobot.com/#support
Yes, Triple Triad support is planned, but at the moment it is not a priority.
There hasn’t been a lot of requests to increase its priority in the past few years.But 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.Here is the current view of the roadmap for the next few months: Upcoming Features
The standard development cycle of each feature pack is 4-8 weeks.
If you would like Triple Triad support to become a priority, please let us know which of these features we should postpone.Jumping in AoE omens indicates that Miqobot tries to activate movement actions but the character does not move. Miqobot identifies this case as a potential obstacle and activates jump in attempt to overcome it.
But if there is no obstacle, then this problem is most likely caused by a keybind conflict.
Our Tech Support can analyze your keybind and hotbar setup and identify the exact cause.Yes, Identical Cast support is already planned for implementation.
It will be a part of the upcoming Gathering updates:Thank you for your request.
We are sorry, but Miqobot does not support Guildhests.
The combat system of Miqobot is in early beta and currently offers only the following features:- Squadron Dungeons
- Trust Dungeons
- Assist Mode
You can find additional information in the main beta thread: [Beta] Combat
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!
No, we haven’t reached Scenario Engine updates yet. They are planned after Gathering updates.
You can see the roadmap in the development section: Upcoming FeaturesDue to extremely stressful environment during the last few patches, our developers are exhausted. The constant rush towards new version releases have led to a burnout.
For the next two weeks, Miqobot Team takes a leave of absence.
We will continue to answer questions and provide technical assistance, but there will be no progress in terms of development. We apologize to everyone who is looking forward to announced features, which are now going to be delayed.
Just want to say thank you about the small (yet big) change to WHM in this patch. You can now leave WHM to do everything on it’s own without ANY micromanaging while running dailies and such. Wonderful QoL update. Thank you!
Thank you for your feedback very much.
I would rather you guys not cease announcing ETAs. They are very useful and a great heads up. The community just needs to understand that ETAs are ESTIMATES and are bound to change. It’s not like giving a RELEASE DATE and then pushing back for more time to develop.
All right, we will do our best.
I would like to report the crafting solver does not take advantage of standard touch combo action. I watched it do two Basic Touches when comboing Basic to Standard is better. I’m not sure if its impossible to implement or you missed it since it’s a fairly new buff to the action. I just wanted to bring it to light.
Of course, we are aware of the Standard Touch combo bonus.
It was one of the improvements scheduled to be implemented in this version, but due to numerous user requests to release the update as soon as possible it had to be postponed. But thank you for reporting very much.There has been no changes to the combat navigation in the recent patches, but of course, we can investigate your issue further.
Please contact our Tech Support: https://miqobot.com/#support
We can perform a detailed analysis of your keybinds and send you the previous version of Miqobot to verify your suspicion.i would love if miqobot would do that but sadly i do belive that falls under the QoL (Quality of Life) updates and miqobot has alot to do before they get to that part of updates for Miqobot.
Another posible more simple option is to have miqobot prioritize “truth of mountains” / “truth of forest” over “Prospect” and “Arbor Call” a reprioritizing of skills used when gathering would all that would be needed as the special weather nodes use “Truth of Mountains” and “Truth of Forest” for detection on the minimap
NOTE: I seriously just sent this to the miqobot team as an official request to reprioritize the gathering skills used
Yes, better Diadem support will be a part of the future Gathering updates:
In fact, we were planning to work on this feature in Patch 5.31. However, our community has decided that Gathering improvements must be postponed in favor of (Lv80) Trust Dungeon support.
Please refer to this thread for details: Level 80 Trust Dungeon
