This topic contains 1,142 replies, has 259 voices, and was last updated by 
Miqobot 3 years ago.
-
Posts
-
Is there any plans in the future to toggle using Provoke for the combat assist feature? Using the bot to play tank in fights that require tank swapping has proven next to impossible because it wants to use provoke off cooldown when you are not the first in the aggro table. Unless I am missing some way to turn it off?
You can either make a macro of it and change the icon to something else so Miqo doesn’t use it, or you can place it on it’s own hotbar (same with shirk and any invulnerability) and set Miqo to ignore that hotbar number through the advanced settings.
So does the Combat routines just assume the move is there, and assist mode scans for them? Or what is the major difference?
We are sorry, but we do not understand the question.
Combat rotations and Assist Mode do not scan hotbars, they are parts of the combat module.
Hotbar scanning is a separate procedure which evaluates and caches each hotbar slot for future use by the combat module. The combat module calculates the rotation based on the abilities available on hotbar at the current moment and makes predictions of the next action in advance.
But the internal application structure is irrelevant for scanning speed, frequency, or the inability to synchronize with third-party game client modifications. These are technical limitations caused by the fact that Miqobot doesn’t use code injections.If this does not answer your question, please clarify what kind of information you would like to receive.
Is there any plans in the future to toggle using Provoke for the combat assist feature?
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.
If neither of these methods work for you, then we donβt have any other suggestions.
As it turns out, the combat routine just backflips out early on Red Mage regardless of plugins, I turned off the combo addon and placed all ability icons on the bar and it consistently missed the third part of the combo and backflips out early. I was testing with a Red Mage and Holminster Switch combat mode, it will sometimes finish the combo and sometimes not.
In this case, we have analyze your hotbar and keybind configuration in order to identify the problem.
Please contact our Tech Support directly and we will try help you: https://miqobot.com/#supportMiqobot seems to not like the crafting skill “Final Appraisal” when used in a crafting macro sequence.
Miqo will repeatably spam the skill as if it never pressed it to begin with.
Sure a way to deal with this is to just remove it from the macro so Miqo dodges the whole problem, but it might still be interesting to look into.
- Things I have done to see if the problem disappears:
Change “Final Appraisal” to a different hot key –> Problem remains
Restart Miqobot –> Problem remains
restart PC –> Problem remainsYes, Final Appraisal does not advance the synthesis step and may indeed break your macro.
However, there is a simple workaround for that. Please create the following ingame macro and put it on your hotbar instead of Final Appraisal:/ac "Final Appraisal" <wait.2> /ac "Delicate Synthesis"Please replace Delicate Synthesis with the action that comes next in your rotation.
This macro will execute two actions at the same step and will advance the synthesis correctly.Please note that this workaround is not required for Crafting Solver. The solver is fully capable of handling Final Appraisal as intended.
I saw that custom openers or a selection of openers was already requested in other threads so I wanted to share my suggestion here. From what is known, Miqobot requires an update for combat assist for all classes as the level 90 rotation will probably change for everyone. With that in mind, would it be possible to implement the opener-feature in the 6.0 combat assist update? At the very least it’s good to have the code foundation of it already so it’s easier to implement if a future version. Thank you for your time and consideration.
Yes, opener customization has already been requested and planned for implementation.
No, it will not be possible to implement it in 6.0 update.This is a feature that would require several months of development.
We don’t think that delaying the core Endwalker upgrade by several months in addition to the initial downtime would be a wise decision.
First, we have to reimplement the broken core modules and make Miqobot functional in its original state. And the development of new features can only happen after that.I’m having problem with the GP based rotation. it seems that Miqobot is not using the 0GP rotation:
Here is my log:(2:50:04 AM) (SCENARIO) Started: (2:50:04 AM) 'Dusk' (2:50:04 AM) Chapter: 2 (2:50:05 AM) I am 'MIN' now! :3 (2:50:05 AM) Teleporting to: 'Tailfeather' (2:50:15 AM) Successfully teleported to 'Tailfeather'. :3 (2:50:17 AM) Purifying 'Fire Moraine ξ½'. (2:50:40 AM) Aetherial reduction complete :3 (2:50:41 AM) Added 400 GP rotation: '1000 Collectability' (2:50:41 AM) Added 0 GP rotation: 'Ephemeral 0GP' (2:50:42 AM) WORK until: 07:50ET (131 seconds) (2:50:42 AM) Gathering started. (2:50:42 AM) Max node count: 2 (2:50:42 AM) Scanning for shiny gathering nodes like 'ephemeral' *.* (2:50:42 AM) No gathering nodes around. But hey, there's a beacon over there for me -> (2:50:42 AM) Going from 4 to 12 in 5 trips. (2:50:45 AM) 5 trips more.. (2:50:46 AM) 4 trips more.. (2:50:49 AM) 3 trips more.. (2:50:51 AM) 2 trips more.. (2:51:11 AM) 1 trip more.. (2:51:11 AM) Destination reached! (2:51:12 AM) Scanning for shiny gathering nodes like 'ephemeral' *.* (2:51:12 AM) I see a shiny node at (166.123596, -148.727600, -59.993382). (2:51:12 AM) Going from 12 to 17 in 3 trips. (2:51:12 AM) 3 trips more.. (2:51:18 AM) 2 trips more.. (2:51:20 AM) 1 trip more.. (2:51:21 AM) Destination reached! (2:51:23 AM) Selecting slot -> 4 (2:51:24 AM) GP = 512. OK - rotation '1000 Collectability' (400). (2:51:24 AM) Using action: (Start) (2:51:24 AM) Using action: (Scrutiny) (2:51:28 AM) Using action: (Meticulous) (2:51:32 AM) Evaluating condition: (If Standard Procs) - Yes! (2:51:32 AM) Using action: (Scrutiny) (2:51:34 AM) Using action: (Meticulous) (2:51:37 AM) Using action: (Meticulous) (2:51:41 AM) Using action: (Finish) (2:51:41 AM) Hitting that poor node. :3 (2:51:48 AM) My precious shiny sparkles! (1/2) (2:51:48 AM) Scanning for shiny gathering nodes like 'ephemeral' *.* (2:51:48 AM) No gathering nodes around. But hey, there's a beacon over there for me -> (2:51:48 AM) Going from 17 to 12 in 3 trips. (2:51:52 AM) 2 trips more.. (2:51:58 AM) 1 trip more.. (2:51:58 AM) Destination reached! (2:51:58 AM) Scanning for shiny gathering nodes like 'ephemeral' *.* (2:51:58 AM) I see a shiny node at (51.449371, -33.933411, -60.484749). (2:51:59 AM) Going from 12 to 16 in 3 trips. (2:52:05 AM) 2 trips more.. (2:52:06 AM) 1 trip more.. (2:52:07 AM) Destination reached! (2:52:09 AM) Selecting slot -> 1 (2:52:10 AM) Hitting that poor node. :3 (2:52:18 AM) Hitting that poor node. :3 (2:52:27 AM) Hitting that poor node. :3 (2:52:35 AM) Hitting that poor node. :3and here is my chapter:
//Avalonia Fallen job(MIN) teleport(Tailfeather) aetherialReduct() gatherPreset(DuskSands) grid(Dusk_forelands_min) rotationIfGP(1000 Collectability) rotationIfGP(Ephemeral 0GP) workUntil(07:50ET) gather(2) icon(1,12,1) workUntil(07:50ET) gather(2) icon(1,12,1) workUntil(07:50ET) gather(2) icon(1,12,1) workUntil(07:50ET) gather(2) icon(1,12,1) workUntil(07:50ET) gather(2)Could you please take a look if there’s something I am doing wrong?
for some reason, when I manually changed to the 0GP rotation miqobot suddenly realizes the go rotation selections:
(3:08:36 AM) Destination reached! (3:08:38 AM) GP = 455. OK - rotation '1000 Collectability' (400). (3:08:38 AM) Using action: (Start) (3:08:38 AM) Using action: (Scrutiny) (3:08:42 AM) Using action: (Meticulous) (3:08:46 AM) Evaluating condition: (If Standard Procs) - Yes! (3:08:46 AM) Using action: (Scrutiny) (3:08:48 AM) Using action: (Meticulous) (3:08:51 AM) Using action: (Meticulous) (3:08:55 AM) Using action: (Finish) (3:08:55 AM) Hitting that poor node. :3 (3:09:01 AM) My precious shiny sparkles! (1/2) (3:09:02 AM) Scanning for shiny gathering nodes like 'ephemeral' *.* (3:09:02 AM) No gathering nodes around. But hey, there's a beacon over there for me -> (3:09:02 AM) Going from 16 to 12 in 3 trips. (3:09:06 AM) 2 trips more.. (3:09:14 AM) 1 trip more.. (3:09:14 AM) Destination reached! (3:09:15 AM) Scanning for shiny gathering nodes like 'ephemeral' *.* (3:09:15 AM) I see a shiny node at (-153.825394, 690.634277, -32.673309). (3:09:15 AM) Going from 12 to 15 in 3 trips. (3:09:18 AM) 2 trips more.. (3:09:20 AM) 1 trip more.. (3:09:21 AM) Destination reached! (3:09:23 AM) Selecting slot -> 1 (3:09:24 AM) Hitting that poor node. :3 (3:09:33 AM) Hitting that poor node. :3 (3:09:41 AM) Hitting that poor node. :3 (3:09:50 AM) Hitting that poor node. :3 (3:09:54 AM) Selecting slot -> 4 (3:09:55 AM) GP = 135. NOT ENOUGH - rotation '1000 Collectability' (400). (3:09:55 AM) GP = 135. OK - rotation 'Ephemeral 0GP' (0). (3:09:55 AM) Using action: (Start) (3:09:55 AM) Using action: (Scour) (3:10:01 AM) Evaluating condition: (If Standard Procs) - No :( (3:10:01 AM) Using action: (Scour) (3:10:05 AM) Using action: (Finish) (3:10:05 AM) Hitting that poor node. :3 (3:10:13 AM) Hitting that poor node. :3-
This reply was modified 3 years, 2 months ago by
Erichan.
Yes, of course we can.
Please export your scenario and send to us for investigation. We will try to reproduce your issue and identify the problem. You can attach it here to your next post or contact our Tech Support directly:
https://miqobot.com/#supportThank you for providing the requested information.
Your issue is caused by a collision of several different settings:- Gathering rotation selected by default.
- Gather by Name utilizing the rotation blocker with {} brackets.
- GP-based rotation selector.
When you specify an item name enclosed in {} brackets, you instruct Miqobot to ignore this item when there is not enough GP.
Your Gather by Name setting looks as follows:{[Fire Moraine]} {[Lightning Moraine]} {[Granular Clay]}By default, there is a 400 GP selected. It means that Miqobot will ignore all items in Gather by Name, when there is less than 400 GP.
However, you have also added a 0 GP rotation into the rotation selector, which means you don’t need GP verification to perform gathering anymore. But since you have instructed Miqobot to ignore these items, she doesn’t have a choice but to follow orders.Technically, this is a case of ambiguous setup, because you use two different settings with conflicting results. Miqobot resolves it by setting a priority to one of them. Gather by Name in this case has a higher priority.
In order to fix your issue, please remove curly brackets from Gather by Name:
[Fire Moraine] [Lightning Moraine] [Granular Clay]Please note that the second preset in your scenario for Seventh Heaven is also affected by this issue.
The topic ‘Shadowbringers 5.58 – Issues & Feedback’ is closed to new replies.