Forum Replies Created
-
Posts
-
That one particular hotbar is a confusing mess (Normally I had them as the Ctrl+#, but I rebound a few to just the direct # for a custom private script of my own (which has been off entirely for these tests). I was only thinking about it in terms of same hotbar sequential status, but yeah, it does sound like there’s a good chance that’s got to be the core of the problem. I put everything on that same hotbar and put the macro before the other skills thinking that should be enough, but I’ll give 1. Settings the whole hotbar back to the same control scheme and 2. Some different orderings to see if that resolves the freezing before then changing it back when I need to use my other unrelated script.
Thank you for the insight. I think I should be able to fix this now.
(3:29:38 PM) I see a shiny node at (-532.860413, -400.045807, 25.399170).
(3:29:38 PM) Going from 12 to 13 in 2 trips.
(3:29:39 PM) 1 trip more..
(3:29:40 PM) Destination reached!
(3:29:42 PM) GP = 741. OK – rotation ‘GR-6.0-Collectable_Hard_Full-700GP-4T’ (700).
(3:29:42 PM) Using action: (Start)
(3:29:42 PM) Using action: (Scrutiny)
(3:29:47 PM) Using action: (Scour)
(3:29:50 PM) Using action: (Scrutiny)
(3:29:52 PM) Using action: (Scour)
(3:29:56 PM) Using action: (Meticulous)
(3:30:00 PM) Using action: (+1 Attempt)
Then freezesOr Alternatively
(3:33:37 PM) Destination reached!
(3:33:39 PM) GP = 735. OK – rotation ‘GR-6.0-Collectable_Easy_Full-700GP-4T’ (700).
(3:33:39 PM) Using action: (Start)
(3:33:39 PM) Using action: (Scrutiny)
(3:33:43 PM) Using action: (Scour)
(3:33:47 PM) Using action: (Scrutiny)
(3:33:49 PM) Using action: (Meticulous)
(3:33:52 PM) Using action: (Meticulous)
(3:33:56 PM) Using action: (+1 Attempt)
Then freezesThen it just freezes there (regardless if the meticulous procs).I have Both the corrected Ageless Words/Solid Reason micro (on the very first spot on that hotbar even) and I can then directly just use my keyboard to activate it (Bound to Ctrl+1) and the macro works great, and then have to manually collect for however many integrity I have left. After I clean out the node, the script continues. Another notable oddity is that for the collections it does do, it scrolls via keyboard to the Collect button on the new UI; but on the manual ones I’m using the collect from a keybind off that hotbar with the skills.
Additioanl Info: I melded moderately into gathering/perception. Roughly over 3300/3200 respectively. Not pentamelded, but some overmelds.No extra GP or foods.
With manual intervention when it hits 1000, it looks more like
(3:40:54 PM) Destination reached!
(3:40:56 PM) Selecting slot -> 2
(3:40:56 PM) GP = 707. OK – rotation ‘GR-6.0-Collectable_Easy_Full-700GP-4T’ (700).
(3:40:56 PM) Using action: (Start)
(3:40:56 PM) Using action: (Scrutiny)
(3:41:01 PM) Using action: (Scour)
(3:41:05 PM) Using action: (Scrutiny)
(3:41:07 PM) Using action: (Meticulous)
(3:41:10 PM) Using action: (Meticulous)
(3:41:14 PM) Using action: (+1 Attempt)
(3:41:29 PM) Using action: (+1 Attempt)
(3:41:41 PM) My precious shiny sparkles! (15/200)
(3:41:41 PM) Scanning for shiny gathering nodes like ‘<anything>’ *.*
(3:41:41 PM) No gathering nodes around. But hey, there’s a beacon over there for me ->
(3:41:41 PM) Going from 33 to 34 in 4 trips.
(That’s got me 4×1000 collects)During the node gathering, Miqo stops doing anything when/if 1000 collectability is achieved. If it doesn’t hit 1000, it will collect on the last integrity, or I’ll have to manually select collect if it hits 1000. It appears to be using the skills correctly up until that point, and collects when <1000, but I dont’ know what’s wrong if it maxes out collectability during the process. Any idea what’s going on here?
I’ve had my windows 10 remove it 3 times over the past 3 days, despite granting it exemption status.
My Windows 7 machine removed it once, although since it’s not supposed to be removing things as easily as windows 10 does, was much more of a shock.So far I’m glad it hasn’t happened while I’ve had scripts running, because that would be a major major headache. And Windowss 10 only easily allows you to temporarily turn off the active file protection before it turns itself back on. JFC Microsoft, stop treating us all like idiots. This windows 10 machine’s sole purpose is to run Miqobot and you’re making it difficult to do it’s one damn job.
Not sure if it’s intentional, but pressing alt while Miqobot client is selected pauses the script for me until I press it again.
It was driving me crazy for a while before I realized what was happening because it would trigger sometimes if I alt+tabbed from Miqo back into ffxiv and I had to work out an alternate solution to change windows.
Damn. While I’m glad yours is working for you, sounds like this is going to be a pain for me to isolate. Not running my own bots for long enough to wait for the seemingly random error to occur would be rather costly, so trying to figure out what, if anything, changed between versions comes first.
Since I’ve been running the same AHK version with luckily no updates lately, it’d be good to hear from the Miqo devs if they changed anything functionally under the hood with the last update that was different than the usual patch memory address updates and new scenario functions.
Update: The error message itself is “A fatal directx error has occurred (11000002)” which at least was a common error back around 4.3 as well.
It’s really weird that it’s affecting both of my clients yet doesn’t seem to be a newly widely reported error in the ffxiv community lately.
It could be that the error causing shared behavior between the two clients isn’t that they run Miqobot, but that they craft a lot. Maybe I’m getting this error at such a high frequency (it’s been a rare twice in the past 2 hours now…) because I’m just triggering a crafting related bug.
So if that’s the case, has anyone been managing to use Miqo to craft a ton and /not/ been getting errors lately?
