Forum Replies Created
-
Posts
-
Might be an idea to let us use own navigation grids or behaviour coding for boss battles just like current behavior. Just looking at current way squadrons are implemented with checkpoints and bossbattle flags it doesn’t seem like a stretch to just let the community build those scenario’s for eachother.
Similary with the rotations and optimization of combat. Adding an additional layer on top of the base skills currently where priority lists can be implemented with some logic can be of great improvement for the future.
Yes, these feature are already planned.
Rotations and Dungeons Customization are already in the list of next features: [Beta] CombatOk, here goes. Other users might find it useful too (if you ignore backtrack issue) – it’s leveling BTN 56-60 with collectables on Birch place in Clouds.
We have experimented with your grid and haven’t encountered anything unnatural.
Would you please clarify, which beacon does Miqobot backtrack to and under what conditions?BLM also has a horrible rotation now, guess we gotta wait for an update on the rotations 🙂 <3
As we mentioned a few posts earlier, BLM rotation is optimized for levels 1-66 only.
Please refer to the main status thread for detailed information on all jobs: Shadowbringers – Miqobot StatusNew rotations will be implemented in the next update.
Then I have no idea why does it backtrack to a beacon just visited… I can attach the grid which produces this bug if that helps.
Of course, any additional information will help us identify the issue faster.
Weird %) I’d just add a single variable to store number of last gathered slot (1-8), which is reset to zero once node is fully gathered. This way bot can perform GP check only in case variable holds 0 (i.e. we didn’t gather anything from the new node yet), otherwise it should stay on the last gathered slot unless it disappears (and then it shouldn’t perform GP check anyway – just take the next “no {} brackets / no rotation” item name from the list.
Thank you for your contribution very much. We will implement it after all critical issues are fixed.
I’m sorry… any chance you clarify it a bit? Did you mean it’s implemented in the current release, and I’m just doing something wrong (what exactly)? Or that it’s implemented, but not released yet?
It’s implemented in the current release. You can find the detailed explanation of the beacons rotation algorithm in your thread: General gathering problem (HW/SB only)
Hmmm why? If an item disappears – then you more “cursor” to another item; though, my idea is that you never move “cursor” because current amount of GPs changed (i.e. no GP checks except for before the very first hit)!
The current algorithm has no rule to move cursor. At each moment it evaluates the required gathering slot based on the current environment and settings. It does not have any memory of a previously gathered item. Therefore in order to address this issue, we will have to redesign this feature from the core.
Any luck with it? Just to remind: it was a bug where Miqo does weird backtracks once ephemereal node (not connected to the grid) appears. Just encountered it again using another grid…
Yes, we’ve managed to reproduce this issue, albeit only once.
It seems to occur under very rare circumstances and is related to loading processes in the game memory. We need more time to investigate it.I. Once Miqo flies through a beacon (no matter if it is used as a beacon or not), beacon should be marked as “visited”. Later it should choose next unvisited beacon. Of course, in case of star-like grid with just a single “central” beacon it should still fly to this beacon, no matter if it’s “visited” or not.
This solution is already implemented. Please note that the beacon is only marked as visited when Miqobot flies directly through it. Alternative routes in close proximity do no count.
it moves cursor to collectable item and… starts to gather completely useless items as non-collectible, without starting the rotation (well thank goodness: at least it does not waste GPs).
Possible fix: rotation GP check should never be performed once gathering of current node is started. You hit an item = you gather this item until node is totally gathered, no matter of new GP.
Yes, we are aware of this problem. The solution you proposed, however, will not work due to the existence of rare items which disappear from the node after one hit. It requires a more careful algorithm.
The effect of not wasting GP is a result of the solution we implemented earlier when this issue was discovered. In order to address it completely, we will have to redesign this feature from the core. It will be done after all critical issues are fixed.I´m having issues with Ingenuity II on my LTW.
When it´s active it often completes the craft without doing much quality, didn´t have that problem on other crafters as far as I remember.Miqobot has not yet adapted the new crafting math and may indeed miscalculate progress under certain conditions. Especially if you are using Ingenuity.
Please refer to the main status thread for detailed explanation: Shadowbringers – Miqobot StatusIf you are not satisfied with the current state of Crafting Solver for any reason, please consider resorting to macro crafting for the time being.
Does the BLM rotation not include Flare AOE? I’ve noticed that when I was doing assisted Trusts in the 71 dungeon, it never does Flare.
At the moment BLM rotation is optimized for levels 1-66 only. Flare is used as the last spell in Astral Fire phase and does not account for level 68 trait.
Please refer to the main status thread for detailed information on all jobs: Shadowbringers – Miqobot StatusNew rotations will be implemented in the next update.
As we stated in the main status thread, Miqobot was not tested with 71+ content and may perform unpredictably. Especially if you are using Ingenuity.
Please refer to this thread for detailed explanation: Shadowbringers – Miqobot StatusIt will take some time before Miqobot adapts the new crafting math.
If you are not satisfied with the current state of Crafting Solver for any reason, please consider resorting to macro crafting for the time being.Miqobot is designed to support all game client languages, including Japanese.
Would you please give us more information about your issue?1. Show us a screenshot of your settings on Gathering tab.
2. Show us the message log from the Output Area. (Starting from “Hello! I am your Miqobot!”)The more information we have, the faster we’ll be able to help you.
Our developers have verified your information and unfortunately we couldn’t reproduce your problem.
The Beacon of Passage is identified and displayed without issues.- Please verify that you have enabled the necessary settings on 3D Radar tab.
- Please verify that you have enabled Beacon of Passage identification in Advanced Settings of 3D Radar.
If you require additional assistance, please contact our Tech Support directly: https://miqobot.com/#support
We would recommend to read our guide on Keybinds and Icons Recognition in order to understand how Miqobot operates with your hotbars.
Our Tech Support can analyze the hotbars and identify the exact cause of your issue.
Please contact us directly and we will do our best to help you: https://miqobot.com/#supportPatience 2 never seems to get used on FSH whether or not it’s enabled
Patience II is activated under the following conditions:
- GP is at maximum value.
- Patience II icon is on hotbar.
- Powerful or Precision hook is enabled.
If you require additional assistance, please contact our Tech Support directly: https://miqobot.com/#support
Hey guys, SAM rotation isn’t fully functional for shadowbringers, could we get an update on that by any chance?
Yes, we are working to upgrade all rotations for 71+ content.
Please refer to the main status thread for updates: Shadowbringers – Miqobot StatusSorry if this isnt the correct place, i did try and do a search. I’m a new user of this but I noticed on my bard in alexander arm of the father after the adds when you get to the Living Liquid boss, during the fight I was stuck in the aoe rotation for my bard (RoD, Quick Knock etc).
Thank you for reporting! We will review Miqobot performance in this raid and will make the necessary adjustments.
