Forum Replies Created
-
Posts
-
Did you start in the correct spot? It seems it cannot go to the waypoint 442, which should be the point in front of the npc, which queues you for the diadem.
Start the scenario outside of the diadem in the ” The Firmament ” this is where the scenario starts and will auto join the diadem
If you are using a preset with its own post, it’s probably best to put questions/problems about it there: https://miqobot.com/forum/forums/topic/infinite-universal-diadem-scenario-botany-and-mining/
However it seems you are in the wrong tab. You need to start this in the Scenario Tab not gathering. A Scenario is like a script, which chains the single functions of Miqo together (gathering, moving, teleporting, etc.)
well it goes to the node and opens up the harvest. it even moves to the correct slot but it just doesn’t end up pressing the slot to actually harvest
Gathering for me works fine. If you post your miqo-logs (and maybe link to the scenario you are using, if it’s on here) when you’ve encountered a problem it’s much easier to troubleshoot it.
In your case, it probably is one of the following:
- You do not have enough perception to gather the item you want to gather
- You don’t have all the required skills for the rotation you want to use on your hotbar (in the logs, you would see the skill, she is stuck on)
Same here , i am using a grid i used previously in and even an old shadowbringers one , it gets to the node and then it just stops ,i’m guessing there’s still stuff to polish
Same as above, you should post your logs, when this happens and maybe elaborate a little bit, on the used scenario/grid and what item you want to gather.
[6.1] “Update” for Collecting Raw Eblan Danburite and Thavnairian Corn (v02)
Downloads are updated to include the adjustment mentioned below. (v02)There is no update needed for grids or rotations etc. If you’ve modified my Scenario you can just add this gatherSlot line for support of the 2 new items, as they are using the same node:
Chapter 2 and 14:
//# Raw Eblan Danburite // gatherSlot(8)Chapter 10 and 22:
//# Thavnairian Corn // gatherSlot(3)Reminder: At least 3230 Perception is needed!
I’m starting to believe this is a keybind issue, especially after reading many other posts having similar issues. Can anyone assist me with reviewing my keybinds and seeing if I have something set that’s causing the problem? Thanks!
P.S. – tried to upload the KEYBIND and HOTBAR.DAT files, but the site didn’t allow me to do so. If there’s another way to send them, please let me know.
I tried the grid you probably where using (from mochi the silver ore safe one). It is working, so the problem most likely is in your ingame-settings. Compass btw doesn’t seem to be needed, as the gathering nodes should be close enough. But even then, just use
use compasshere and not the second one. Compass II seeks for the highest level and might lead different results.You can see how the grid is setup when you tick the box
show on radar. You can read here, what every grid point means: https://miqobot.com/forum/forums/topic/help-navigation/
You can see that you need to fly to the gathering points first, as there is no connection from one aetheryte to the gathering area.
With the grid shown on radar, you can see how miqo follows the path.It sounds like a hotkey conflict for movement. You can read here, for how to setup your keybinds: https://miqobot.com/forum/forums/topic/help-keybinds/
The most important bit should be this:
But please don’t make any impossible shorcuts. If you assign W to Move Forward and Ctrl‑W to Camera Up, there’s absolutely no way for Miqobot to move and adjust camera at the same time. Your character will behave weird and eventually will get stuck.
Another example. If you assign NUM4 to Move Cursor Left and Alt-NUM4 to Hotbar Slot 1, Miqobot will not be able to access your hotbar without triggering cursor movement. Cursor actions have higher priority and hotbar slot will never be pressed.
Miqobot will Not detect this kind of conflicts as it would result in a significant performance penalty.
Miqobot is already trying her best to keep things as easy as possible for you. Just don’t make them impossible 🙂We recommend that the most basic actions are assigned to a single key each. This way, you will minimize the chance of running into unexpected issues.
The basic actions are:Move
Jump
Strafe / Turn (either of them)
Point Camera
Move CursorBy default, these keys are already assigned by the game, so if you didn’t mess with them much you have nothing to worry about.
Could you show me how you tweaked it?
Cause i gotta be honest, i have no idea where to even start. xDThe most tweaking is your own rotation and the amount of skills and time you need to set for every specific encounter. And of course the hotkeys, which are used with
keyandiconfunctions.Read trough the comments of the Scenario and look what input is intended here (like moving the cursor up once) and adjust it to your keybinds and hotbar layouts.
Create ingame combat macros for AoE and Single target. Maybe create shorter variants if you need them for that tiny extra dmg for adds or bosses. And put them on your hotbar, so you can adjust the
icon-lines.For example, Chapter 2 looks like that for me:
afkfor(00:00:15) //loading grid(Sirensea) waypoint(3) icon(5,1) //aoe macro L afkfor(00:00:43) waypoint(4) icon(5,2) //aoe macro S afkfor(00:00:44) waypoint(5) icon(5,6) //aoe macro XS afkfor(00:00:18)But you will just need to test it out. Prepare aoe and boss macros first and see how many you need for every add group. It’s a little bit of trial and error. You can prepare a set amount of pressed macros and afk timers (icon + afkFor). Then let it run, see where it gets stuck, where more dmg is needed to be consistent, or see where you might can remove a line. Depending on your level, you might even want to put in one or two heal macros.
Ingame combat macros can look like that:
/ac "GCD 1" <wait.3> /ac "GCD 2" <wait.3> /ac "oGCD 1" <wait.1> /ac "GCD 3" <wait.3>Those kind of Scenarios are not really plug and play, you always will have to adjust them for what works for you, currently.
Well, you pay the license per month. And months have a different amount of days. So thats normal.
-
This reply was modified 2 years, 8 months ago by
Nekro.
However with the 100 per day limit, you can only go so far.
There is no 100 per day limit. I’ve ran Garuda EX over 200+ times in a day with no issues.
Maybe this is a new patch they added? Or maybe this is due to something else if anyone else has encountered this issue before.
I thought so aswell, however. I found this forum post https://forum.square-enix.com/ffxiv/threads/422343 indicating that it already existed 2020
It might be, that there is a limit on dungeons but not trials.
You can try. You need to preset your duty finder settings. Then you need to write parts for:
– rejoining the instance
– fighting the mob
– leaving the duty
– desync / repair / materia extract, whatever you wish to do, before the next instance.The most complex part would probably be the fighting. You need to create a navigation grid for the arena. Move around, predict at which time stuff could happen. Write ingame macros to execute your rotation, like:
/ac "GCD 1" <wait.3> /ac "GCD 2" <wait.3> /ac "oGCD 1" <wait.1> /ac "GCD 3" <wait.3>and activate them in a Scenario with for example:
sendIcon(x,y) afkFor(00:00:40) //macro durationInstead of afking the whole macro, you might also move around and afk later for smaller amounts of time. A job which isn’t a caster or melee, makes the creation of the combat part much easier.
Make multiple such macros for maybe Burst, normal single rotation, AoE, if you need to. Then go in and try them out, see if you can reliably time things with your dmg output, from the macros.
Don’t use ingame macros for crafting.
Go to the crafting tab and uncheck the
useCheckbox. Clicknewin the bottom right of the white window. Name your macro, likelowlevel-maxhq. Then put your keysequence for those 2 skills you want to use in the box next to thestartButton separated with a comma,. Clickoverwritein the bottom right and accept.This will already work if you want to craft single recipes. Just go to your crafting tab, navigate to the item you want to craft. Set the numbers of crafts in the
countfield (or writemaxto always craft til your materials run out). Make sure your keysequence is selected (by clicking on your macro in the box) and hit start.If you want to chain more than one item in a single run, you need to create a Scenario.
I’m trying to create a scenario, but every time I attempt to import it to miqo’bot it says it contains no miqo’bot presets. 8(
Miqo can only import, what has been exported by her. The lines from Eyefinity for example are, what you need to copy directly into a new Scenario (Scenario Tab ->
newButton -> left box).
To learn more about Scenarios, you can look here: https://miqobot.com/forum/forums/topic/beta-scenario-scripting-engine/Ive been looking for something to to help with the first tank mounts, they have to be 61+ or they dont count. Maybe a unsyc ex trial?
I have no idea how to even start one myself, any help would be great 😀For the first tank mounts, garuda ex like rxantos mentioned is sufficient. For the second ones, where you need to be in a dungeon 61+, you can give this one from xtchc a chance: https://miqobot.com/forum/forums/topic/request-garuda-ex-tank-mount-farming/page/2/#post-35344 . I tweaked it for myself and it worked great.
On a further note: My Scenario would be completely fixed with one of those 2 things:
– Fix the resurrect in dungeons, where you need to hold the key
– Or tell Miqo death is intended and you want to handle the resurrection yourself in the catchup Chapter. (Maybe adding a single resurrect function for that aswell). For that Miqo however needs to be able to execute everything what she can do while death (like sendKey etc.), which probably is more work.For it to be more reliable, I already mentioned a function for queueing with the current settings here and if you add a leave duty function aswell, most of the inaccuracies would disappear.
However with the 100 per day limit, you can only go so far.
And thats what’s messing up the scenario. This is what I have currently going off of what Nekro posted. It works to go in, but messes up reentering the second time around. Is there something I’m missing?
After the first run is over, and Miqo opens the Duty Finder menu again, there ends up being one too many UP keystrokes when repeating the same sequence, and it causes the cursor to move right up past the Join button.
Only here’s the thing: This renders RepeatAll commands useless, because that will just send Miqo right back to using the extra UP keystroke that we need to avoid.
I encountered it aswell. The simple solution for it (as in my Scenario) is to start inside of the dungeon. You need to set your duty finder settings anyway. So a queue after it, to join it for the first time doesn’t hurt.
Edit: I just looked into a Sirensong Scenario I adjusted for my needs. And there I wait for 5 seconds after opening duty finder, there it is working just fine, everytime from first to last.After that, you can tweak the rejoin for the second time onwards only.
Thank you so much for the scenario and example! That’ll help with later uses like this. It works just fine, unfortunately @Michael was correct and you can only do 100 Registries in the Duty finder per day. So this isn’t an infinite money maker afterall. Cheers to everyone who helped answer this thread
Thats actually interesting. When did they add this? Because I remember using the garuda ex function from miqo with more than 100 registries in a day.
But if this is true, then 600k gil would be the maximum, if you don’t queue up for anything else on that day.-
This reply was modified 2 years, 8 months ago by Nekro.
For the fun of it I’ve basically created a working Scenario. The problem here is, that Miqo wants to resurrect when using koCheckpoints, which fails, as the resurrect windows in dungeons are different and needs the accept button to be hold. This will result in the Scenario breaking til you resurrect manually.
Therefore, if you currently want a working Scenario on it, you would need to do the instance without using the suicide skills. Plus you need to be consistent in your mob grouping and killing without taking too much dmg. As every death will result in a Scenario break.
You would basically need to kill the second group with different skills. Then for the last group, quickly gather, freeze and shatter them (33 + 92). After that leave the instance normally without a death.
I am sure it is possible with skills 102 and 103 for the second group, but I wont work on it anymore, because I don’t want to farm the skills I am missing. For now I’ll leave it here as a reference.
As with every custom Combat Scenario, it needs to be adjusted to the users hotbar and also hotkeys for specific actions, like opening duty finder. Also loading times might differ and needs to be adjusted aswell.
I’ve used the following setup on hotbar 3 from left to right:
91 – 12 – 16 – 33 – 34 – 13 – Swiftcast – 92 – 21 – SprintThe numbers are the blue mage skill numbers. I didn’t have a few of those skills mentioned in the video so I improvised with skills 33 and 34.
After setting up your hotbar or adjusting the Scenario, set your dutyfinder to The Vault, undersized parties and min. item level. Then queue up and enter the dungeon. When you are in, you can start the Scenario for one run (and after death, manually hold the resurrect button, to see the working loop).
I think I am using the default keybinds for every action, but if not, it is commented, which hotkey is used.
Good luck.
If you are writing your own Scenario, create a gathering preset which has the checkbox ticked and use it in your scenario with
gatherPreset(name)If the Scenario comes with a gathering preset, you need to check the checkbox on this preset and overwrite it in the gathering tab.
If the Scenario doesn’t come with one, you can check the checkbox in the gathering tab and it should be used automatically, if there are no gathering nodes near you.But you should think about changing other Scenarios compass settings. Normally a Scenario is designed in a way that it either needs the compass/truth or not. Some Scenarios uses grids, which have “beacons” acting as the compass without using the skill, because overusing it might attract attention from other players.
