This topic contains 13 replies, has 5 voices, and was last updated by 
Miqobot 3 years, 11 months ago.
-
Posts
-
Hello,
I’ve been doing some dungeon runs on trusts and this may also be an issue on squadrons though I’m not leveling anything I can confirm with. Miqo will have my character stand in AOE’s and instead of moving out of the way it will jump or just stand still. I ran holminster while I was sleeping with a scenario to do 7 runs, repair, check materia, etc… (about 7hrs) and it only completed 6 runs, then hasn’t been able to complete one since. It can’t get past the first boss in Holminster. I’ve grabbed the latest Miqo, restarted it, tried restarting Miqo with trust support inside the trust run and nothing seems to help much. Like it’s navigation when it detects aoe’s is broken. Not sure what might be going on here. Using RDM.
The gear on the character did break due to the amount of deaths which is how it got stuck. This is starting with a repaired to condition of about 150% across the board, so it should have been able to handle 7 runs before needing to repair. I’ve used this for leveling 2 accounts worth of stuff and this hasn’t been a problem until the past month or so.
-
This topic was modified 3 years, 11 months ago by
acrazycyclist.
Miqo will have my character stand in AOE’s and instead of moving out of the way it will jump or just stand still.
First thing, which will come to mind is that you don’t have all keybinds set for movement (especially look for strafe left and right I think), a conflict and/or not using the legacy movement type.
Might want to look up here for some general tips in that regard:
https://miqobot.com/forum/forums/topic/help-keybinds/Or the quick setup, might have overseen some movement related stuff.
https://miqobot.com/#faqNothing has changed, as I mentioned I’ve leveled stuff across a couple of accounts and this just started to be an issue recently. It works fine for some stuff then randomly stands in an aoe or line aoe. It takes 20ish attempts and if I’m lucky it downs the 1st boss in Holminster.
Edit: I’ve already checked over keybindings, I’ve disabled the antivirus on the PC running it in case it’s causing a problem with temp files like miqoradar etc etc…
-
This reply was modified 3 years, 11 months ago by acrazycyclist.
if I’m lucky it downs the 1st boss in Holminster.
I had this problem once too, but that was just because I disabled my keybinds for strafe left/right. So I guessed that either those were disabled or maybe another action which has the same keybind in combination with maybe an ALT or SHIFT collides with the movement.
as I mentioned I’ve leveled stuff across a couple of accounts and this just started to be an issue recently
I think ffxiv saves configuration based on character, so I guessed there maybe was a conflict in your keybinds, which didn’t lead to problems until now.
If thats not the case, maybe it has to do with your class. I can think of that miqo might want to use some dash-related combat actions on your RDM which she doesn’t have access to, or the auto-target mob is turned off, but she still wants to do that, to reach the safe zone on the first boss.
I can’t think of anything else, which would result in your current problem. I ran holminster 2 times (with warrior) with the newest version (1.3.41) and I didn’t encounter this behaviour.
Probably need to wait for an answer from Miqo then.
I had this problem once too, but that was just because I disabled my keybinds for strafe left/right. So I guessed that either those were disabled or maybe another action which has the same keybind in combination with maybe an ALT or SHIFT collides with the movement.
I’ll check that out, the movement keybinds are standard wasd with sd doing turn instead of strafe, strafe keybinds are shift a / shift d rather than a/d so that q and e can be used for hotbar spells – however this hasn’t been an issue before in the past and it’s always worked out fine without me needing to tweak any keybinds. I’ve leveled about 3-4 jobs to 80 from 30/50/60 without any problems using squads then proceeding into trusts. Either some function in the combat assist has a hiccup now that causes reactions to slow down significantly, or something in the radar that it’s not picking up the aoe marker correctly.
I just ran it on my main pc since my last response to test it out with rdm and it cleared holminster with no wipes. I tried another class on that computer with miqo though (dnc) and wiped there as well. I just can’t think of a reason that this start happening in the past few updates.
The aforementioned problem that the PC in question had bitdefender antivirus, which I had a lot of issues whitelisting miqo with due to temp files and file paths. I ended up just turning it off any time I run miqo now so there shouldn’t be interference there.
-
This reply was modified 3 years, 11 months ago by acrazycyclist.
strafe keybinds are shift a / shift d rather than a/d
This is a keybind conflict.
Using Ctrl, Alt, or Shift in any of the combat navigation actions creates a collision.
Keybind conflicts are described in details in our Keybinds and Icons Recognition guide.You can find the full list of actions used in combat in the main beta thread.
These actions must have valid keybinds. It’s highly recommended to assign each of them a single key.
- Move Forward
- Move Back
- Strafe Left
- Strafe Right
- Jump
- Point Camera Up / Down / Left / Right
- Zoom Camera In / Out
- Cycle through Enemies (Nearest to Farthest)
- Target Self
- Target Member 2 in Party
- Target Member 3 in Party
- Target Member 4 in Party
Note. Only strafing is used for side movement. Miqobot does not utilize Turn Left or Turn Right actions.
A single key means that it doesn’t contain any composite keybind modifiers like Ctrl, Alt, or Shift.
Thanks @miqobot team — I’m going to give all that a try tonight, but I do want to note that this wasn’t a problem until recent patches and that Miqo worked just fine on the keybinds that were there through plenty of dungeon runs.
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.Are you currently leveling a caster? Because those always died way more often for me when running trusts, not sure why.
Cause we love our DPS numbers and mechanics adjust to us.
Haha, yes, but it’s also happened with DNC before. I went ahead and setup a fresh everything on a different PC with the other account I’ve been having these issues with so all the keybinds and everything are default. I’ve died a couple times as RDM but haven’t tried DNC yet which is the other 80. It definitely moves way better and the amount of wiping has gone down to to once every few runs instead of 10+ times in one dungeon.
It’s odd though that it dies more as a caster and there are the random jumps instead of movement away from AOE’s which I’m not sure what it jumps for? Cancelling a cast? I might need to focus more on it just to watch what it’s jumping for, but I see jumps a lot when I tab over to that window lol.
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.@miqobot, How can I send the keybinds in to you guys?
-
This reply was modified 3 years, 11 months ago by acrazycyclist.
Please contact our Tech Support and we will do our best to help you: https://miqobot.com/#support
-
This topic was modified 3 years, 11 months ago by
You must be logged in to reply to this topic.