Forum Replies Created
-
Posts
-
Are you using a separate program in conjunction with Miqo? Miqo does not control the mouse by virtually moving it, she uses keybind commands to move the cursor through items, targets, or menus in-game. Unless you add in a keybind that moves your camera or character it should never move the camera.
Either way, Miqo can always reset your camera with
angle().The leves repopulate randomly so, yes, you will need to accept the other two and let them rot in your quest log. There is also already a scenario for coffee biscuits in the index. https://miqobot.com/forum/forums/topic/index-scenarios/
There are a few ways to do this. Miqo currently doesn’t have a way to sense food buffs while crafting or gathering so it has to be ham-fisted a bit with the timing. A basic, multi-recipe scenario isn’t difficult to set up on its own. Putting food buffs into the mix is what throws it off as you have the set times for the buffs but the changeable times for the craft itself.
The trickiest part is knowing exactly how long it takes to make the crafts. Using your pre-made macro vs the solver will help immensely. At this point calculate how long each craft will take with your macro, and plug in the food/syrup uses at appropriate times. If your 15 crafts take longer than 1 minute each then you might be in a pickle. Hard-coding the sequence at this point might start to get a bit janky and you might overlap some syrup uses a tiny bit. This will be probably the harder option to set up but least likely to over-use food/syrup buffs.
An alternative is to tell Miqo to work for 14 minutes to be safe, craft your recipe A, re-syrup, work for 14 minutes, craft your recipe B, etc. Miqo will always finish a current craft if the work time finishes before she does. The problem with this then is if each craft takes too long and you don’t have your 15 of recipe item A before she moves on to recipe B then you will be a couple short and can either manually craft the remainders after or set the scenario to loop. With the loop, however, Miqo will use your food/syrups too much at the end. If Miqo is finished with crafting recipe A before the workfor time is over she will automatically move on to the next step.
Personally, I sit there and semi-babysit it if I’m crafting something I need buffs for. I have a timer on my phone to alert me when the syrup is almost over and adjust my needs from there.
You need to complete this quest first. Does not require a DoL to 60 but does require post-Heavensward MSQ. You can easily level DoH to 10 because the items can be bought cheaply from vendors. Afterward, if you wish to use the Diadem, spam an infinite loop and you’re set.
https://ffxiv.consolegameswiki.com/wiki/Towards_the_Firmament
TLDR Yes, putting the macro in Miqo is easier.
Miqo doesn’t know what is on a keybind when you tell her to press it with the command key(). Miqo is just going to press the keys as you tell her to. If you tell her to press 1 then immediately 2, she will do so regardless of what 1 and 2 actually do. So, unless you give her a delay she will just spam keys. You can use in-game macros this way, you just need to give Miqo enough of a delay before telling her to press your second step macro.
In-game crafting macro vs Miqo crafting macro is essentially the same thing in the result, just different in execution.
In-game you can set a <wait.#> time for each step of a macro but you’re limited to 15 lines per macro. You also need to consider any lag spike messing up using a particular skill. Miqo can then be told to press your macro and then afk for the duration of the macro.
Miqo crafting macro can be as long as you want it to be and I have never seen her mess up because of lag. However, you need to use the keybinds for the skills. I’d advise having a separate document to save your keybinds so you can easily copy-paste the sequence.
You can always go to your locked house/apartment or an inn room and spam your crafting there.
It definitely depends on what part you are currently on as to how long the delay should be. I have a scenario for each retainers, buying things with GC seals, and accepting/turning in leves. After testing them I have the timings down and they never mess up.
Things to note with making key() sequences:
If you have the game not minimised and want to keep using your computer you will need an additional monitor as sometimes moving the cursor on another application with the game in the back can mess it up.
The game responds quicker if it is the main window. Increase your delay if it is not, or if it’s minimised from the last point.
Always err on the longer side for a delay and trim it after testing.
Keys with names like esc work but it needs to be key({esc}, 1).
At the beginning of the sequence, add an extra key() to “wake up the cursor.” The key used will depend on which menu you are opening and where the initial default position of the cursor is. For instance, num4 is mine on my retainer scenario because trying to move the cursor left doesn’t do anything in that menu.
I recommend using commented-out notes on each line to keep things straight. A bunch of num2 or whatever might start getting confusing when you try to go back to fix a step. Miqo won’t let you use tab in-app to make space on the same line to start your note so I write them in a notepad first and it makes it all nice and neat. (Miqo forums don’t like tab either it seems lol)
key(f12, 2) //targets bell
key(num0, 2) //opens bell
key(num4, 2) //wakes up cursor-
This reply was modified 3 years, 11 months ago by
malarkey.
Perhaps this point requires clarification as well.
Implementation of level 80 Trust Dungeon is nearing its completion. This is not the kind of work we can undo and replace with another feature. But we appreciate the constructive feedback.Allegory mats will be essential to the new crafted gear. So I 100% disagree with malarkey’s malarkey.
Having an 80 farm is an excellent idea. Thank you Miqobot team 🙂Perhaps I need clarification as well. r/unpopularopinion
I’m not saying a level 80 trust support shouldn’t be done. I’m saying if it is something people are wanting it should be made sooner in the expansion to get more use out of it as a feature. The Miqo team has already been working on 80 trust support for a while now, and I’m not saying it should be scrapped just because it’s nearing 5.4 release.
In my opinion, if this is something people are wanting, it should be made sooner.
In the long term, when the next expansion is released there will be new tomestones, therefore decreasing the efficacy of this as a feature. Yes, you can still use it to level your combat jobs from 80 to 81, but you can also continue running Holminster Switch or Qitana Ravel until 81+ as well. Or farm minions/cards depending on which dungeon they’re working on.
I’m just trying to keep in mind the long-long term health of Miqo. In my opinion, more permanent features that can get more wide-spread use and aren’t on an efficacy time crunch are better for the whole. The more flexible the program the easier it will be for new people to start using Miqo and the easier it will be to retain customers, new and old alike. Given that the Miqo team themselves have said at one point there are ~100+ requested QOL features, that it’s nearing the end of the expansion, and that they’re already almost finished with the 80 trust support, that is why I put my word forward for QOL over the rest.
Proactive vs reactive. Planning ahead, the Miqo team obviously cannot work on 6.0 features yet as we have no information for them and the new code will break it anyway. When 6.0 releases everything will be put on hold just to get base Miqo running again. If again, people are wanting a trust equivalent for the max level dungeons for tomestone farming then that likely should be the next major feature planned for 6.x after “launch repair” and crafting/gathering updates are completed, provided nothing crazy happens. The sooner max level trust support for tomestone farming can be finished the more useful it is.
To the original topic, 61+ support for tank achievement, hell even 60 for Bitter Memory farm, would be nice to have. However, it is cosmetic and less essential and practically useful than a level 80 trust support. I say after 80 trust is completed, work on some of the more useful QOL requests, then if nothing else, throw some work in a 61+ tank run support. It is not a feature I don’t want, but I believe others should take priority.
@DarkenedSun
Indeed. If it is repair() it will use your crafters and dark matter to repair on your own. Requires appropriate grade dark matter in your inventory, repair on your hotbars, and crafters high enough to repair your gear. If it is repairNpc() then it should be routed to a repair npc and will repair that way.
In regards to monitors, I’ve only noticed issues with key() if the game is not minimised and on the same monitor I’m also currently working with something on.
TLDR; 1) QOL, 2) scenario engine updates, 3) gathering updates, 4) 80 trust support, 5) 61+ tank achievement support
=====
Since it doesn’t need to be synced, it would be easier to make a scenario for this unsynced than it would be for something synced on your own. Squadron support for Bitter Memory farm comes to mind.
Having a level 80 trust support coming out near 5.4 release seems like a waste of time/opportunity to me. The phantasmagorias people are wanting this support to farm for in the first place will be obsolete soon enough. In my opinion, if this is something people are wanting, it should be made sooner.
Given how long the development cycle is for a fully fleshed out support feature like this, including the Garuda Ex unsynced, and that it is something that once you have it you will never need the feature again, I would prefer updates to Miqo that are applicable to a wider audience, could get more use, and are more permanent to the lifespan of Miqo.
From memory, some of the more common threads I see posted are regarding QOL features; the ability to pause a scenario, and updating combat routines. I see people wanting support for the 60 squadrons a bit as well, but I believe it is only more common recently because of the current relics. People that are wanting it purely for leveling seem to not know they can just run Somh Al until 71 with no issues and that Miqo has already made posts regarding squadron support at that level saying that it is much less efficient for time and experience.
Probably my most desired feature would be being able to trigger the combat algorithms in a scenario so I could make my own dungeon runs, like Bitter Memory farms. Given how it could be abused for the dangerous and visible overworld I understand this will likely never be implemented.
Lastly, as for which instance. I just ran The Sirensong Sea on a 79 paladin in 385 crafted gear. Went just fine. No tank busters so the only thing to worry about is positioning. Only the last boss might be tricky with said movement because of her mechanics. Took about 32 minutes with one disconnect and a queue to log back in. Counted for Tank you, Paladin III.
– A lvl 61-62 dungeon to bridge the gap between 60-70. Right now this is the only level range where you need to rely on beast tribes/HoH/whatever else and currently the most difficult to level
It is incredibly easy. If you’re wanting to level combat jobs using squadrons you can just run Somh Al until 71. You don’t have to run unsynced-level appropriate dungeons to get exp. Not only do you get free gil from kills (which you don’t in Holminster Switch or Qitana Ravel), but you also get cards to turn in for MGP, pets to sell on the marketboard, and plenty of gear to make it a net gain in seals which you can then use to buy ventures, cordials, whatever.
– A lvl 80 dungeon to farm tomestones/desynth mats. Anyder is probably best because sublime solution and aethersand are both desynths from it IIRC.
The project the Miqo team is working on now is already a level 80 trust dungeon. Which should be coming out soon™.
-
This reply was modified 3 years, 11 months ago by
