This topic contains 1,142 replies, has 259 voices, and was last updated by 
Miqobot 2 years, 11 months ago.
-
Posts
-
Miqobot is fixed for Patch 5.31.
Please refer to the main status thread for updates: Shadowbringers – Miqobot StatusHello! I am having a minor issue with SAM. Miqo runs through the rotation just fine but if you happen to be out of range of an enemy when she wants to use Yukikaze next, she will spam it over and over until you get back into range where she will continue as normal. Spamming Yukikaze makes the character spin around to face the enemy over and over while you’re running, and I’m not sure if it shows on other people’s screens or not.
Expected behavior would be to detect when she is back within range before attempting to use Yukikaze just like the other melee abilities in the SAM arsenal.
Thanks for your time, and keep up the great coding work!
Man… miqo’s crafter is hands down the best out there. Been using one of the competition’s and it just doesnt even come close. Already doing the new expert synths like nothing even changed. Well worth the wait, thanks!
Thank you for your feedback very much.
Hello! I am having a minor issue with SAM. Miqo runs through the rotation just fine but if you happen to be out of range of an enemy when she wants to use Yukikaze next, she will spam it over and over until you get back into range where she will continue as normal.
Thank you for reporting.
Indeed, there is a weak spot in the algorithm for Meikyo Shisui, it doesn’t handle disengaging properly. We will try to address it in the next version.Hello! Spamming Yukikaze makes the character spin around to face the enemy over and over while you’re running, and I’m not sure if it shows on other people’s screens or not.
Turn off “Automatically Face target when using action” under; Character configuration > Control settings > Target tab. It’s something that gets a lot of healers killed, and you can heal without facing an ally anyway.
Just want to add on and say thanks for the crafting solver as well. The other bot I use for other things doesn’t even come remotely close to miqo in terms of quality in the craft.
Just did 10 expert crafts with miqo and these are the qualities I got: 7071, 8240, 8240, 8240, 8240, 8240, 8240, 6865, 8125, 8240. For reference if people don’t know, the expert crafts are 11,126 progress and go up to 82,400 quality, so miqo maxed quality a majority of the time even with the heavy RNG of expert crafting (granted I have BiS melds, specialist, food, syrup, the whole thing but even without this I could easily see miqo hitting at least min collectability every time with ease).
Plus, the crafter is pretty fast too. This is a screenshot I just took https://gyazo.com/9c70b3feb5f463eaa831706d0384abf2 (I took it right as the end craft text popped up, hence the blue line). And then another craft taken right after: https://gyazo.com/cb8f50024fc10e9176de3993ccf2b00f, also max collect. Both of these were just under 40 steps, which is actually nuts considering the other bot I used would be lucky to make it under 50, usually would hit around 60. With Miqo, I can do about 32 expert crafts an hour.
So thanks Miqo team <3
Hey I have a problem with the bot. Whenever I start it, it gets stuck on the part when it’s looking for my catnip license. It will keep loading until it says no response on the top bar so I have to force quit the game. After that I cant restart the bot(maybe because its still running in the background) and cant remove it in task manager. My antivirus doesnt affect it I turned it of and I also tried to restart my pc. Any ideas how to fix it?
Just want to add on and say thanks for the crafting solver as well.
Thank you for your kind feedback.
After that I cant restart the bot(maybe because its still running in the background) and cant remove it in task manager.
This issue usually indicates that there is a third-party program blocking Miqobot. It may be not an antivirus, but this behavior is definitely a sign of external interference.
Please contact our Tech Support and we will see what we can do: https://miqobot.com/#supportIf your question is about Rowena’s House of Splendors, then yes, it will require one more update.
Please refer to the main status thread for details:- Function deliverCollectables() is partially reimplemented, but only for Ishgard and Diadem.
– Supported: Ishgard Restoration.
– Supported: Diadem Resource Inspection.
– Not supported: Rowena’s House of Splendors.
I’m currently having an issue with gathering in the new Diadem. Some nodes just seem to ignore the “gather by name” section of my preset and go straight to the default slot and amount. Some nodes work as expected, others just don’t, and I can’t really seem to see any rhyme or reason to it. Any idea what could be causing this?
We are sorry, but this is not enough information to identify the reason. We would have to see the exact gathering setup you are using. Perhaps you have enforced Miqobot to use rotation on certain names with {} brackets, and maybe there is another reason.
Please take a look at our guide: Gathering – Gather by Name
And if you still require technical assistance, please contact our Tech Support and try to provide as much information as possible: https://miqobot.com/#support
Got a small question regarding scenario commands…. but it seems i can’t post in the scenario engine thread so i’ll ask here.
Are all the timer functions independent from each other or do they share the same clock?
Could i do something like this:workFor(00:05) gather(1) repeatChapterFor(01:00)to gather 1 item every 5 minutes for an hour? Or would the workFor command overwrite the repeatChapter timer?
edit: i know it’s a dumb example since miqo will just gather the item and then continue the script and not wait out the 5 minutes, but you know what i’m trying to ask here.
-
This reply was modified 4 years, 2 months ago by
Krude.
The timers are independent.
However, please note that each timer begins counting at the moment of function call. So in your example, the repeatChapter timer will be initiated after the first iteration of gather(1). For this reason, it would be better to put repeatChapterFor() at the start of the chapter. - Function deliverCollectables() is partially reimplemented, but only for Ishgard and Diadem.
The topic ‘Shadowbringers 5.58 – Issues & Feedback’ is closed to new replies.