Forum Replies Created
-
Posts
-
Am I doing something wrong here? This scenario seems way less efficient than the infinite mining scenario I have been using. It spends a lot of time flying to waypoints, missing lots of nodes. I must admit I haven’t left it running for hours yet and compared the overall yield but on first look it seems way slower.
I see you figured it out, but if it wasn’t clear. The crafting section is already using the // to stop miqobot from reading each line. If you want any of the crafting presets to work and start crafting teh expert recipes you would need to remove the //
For example:
//Make Water Otter Items
//2:00pm until 9:45pm
//#Not recommended to
//# let solver do this//teleport(Estate Hall, 1) <<<—— Removing the // here would make you teleport to your own house or fc house (depending what options you have)
//aetherialReduct() <<<—— Removing the // here would enable aetherial reduction during this chapter.//changeJob(ALC) <<<—— Removing all of the // in this section would change you to Alchemist and expert craft 5 resins
//setCraftRecipe(Water Otter Fountain Resin)
//selectSolverPreset(water otter)
//icon(3, 7)
//afkFor(00:00:05)
//icon(2, 7)
//workUntil(17:30et)
//craft(5)Hi, Is it possible to share your macro for HQ Tincture crafting?
I am pentamelded but couldnt make it without food.
Very appreciate if you are willing to share it.thank you in advance
Of course, sorry I didn’t see this straight away here it is: 16 steps.
Muscle Memory
Manipulation
Veneration
Waste Not II
Groundwork
Groundwork
Advanced Touch
Innovation
Preparatory Touch x4
Great Strides
Innovation
Preparatory Touch
Careful SynthesisI have my hotbar set up the same for each class, so I can re-use the macro’s for different recipes and adjust according to need.
The macro to get 100% HQ Dex 6 relies on the earlier part of the scenario that makes Dex 5’s HQ.
I found another way which worked better although it meant I had to create two macro’s, one to remove BV and one to put it back on. Because generally BV at the start is in alignment its fine to keep it on, then depending on fight mechanics you turn it off and on when needed to use with RF. I’m thinking of possibly macroing for Raging strikes and WM as well as they really shoudl be up for burst phase. I’ll experiment more today.
I did some testing in savage yesterday and I’m afraid the results are not great. What I am finding is that because Miqo is so good at pressing actions, I am trying to spam that macro over and over, much longer than I would when I did it manually. I wish there was a way that you could pause miqo with an assigned key tagged to a macro. My pause is currently ‘;’ key but I’m not sure if its possible to macro that. If it was and you could temporarily pause miqo, hit RF and BV in quick succession, then unpause miqo, that would work much more efficiently. In any case I went back to manually pressing, a tip I found to help alignment is to wait for miqo to hit BV, keep your eye on it, and as soon as you see it trying to press it, hit RF over and over, 90% of the time this meant both went off together. In terms of parse, hmm, they are ok, just like me without using miqo. Honestly I don’t think wanting to parse high numbers using combat assist is safe, especially with analytical software out there that can easily be read by anyone with your logs. When you analyse it closely you can tell its a bot or an extremely disciplined player! If anyone does know a way out there to be able to put the pause as an hotbar macro please let me know as it would be helpful to me particularly as I play on a controller.
I’ve sort of figured it out I think.
/micon “Radiant Finale”
/macroerror off
/ac “Battle Voice”
/ac “Radiant Finale”Because of the delay of having to keep pressing to get both to go off as close as possible, I have omitted RS and WM as miqo still handles them and has the amazing ability to weave them in! When you get to 3 stacks of coda, BV has a couple of seconds, which is perfect as you don’t get quite as much delay so it lines up better.
I’ve been a user of Miqobot long enough to know it will be broken as of Tuesday because of 6.05. I know nobody has a crystal ball but does the Miqobot team think they’ll have the bot up and running in time for Combat assist (in its current state) for Tuesday evening? Just need to know if I should make my excuses now or wait until I see what happens if I can’t use it.
I have a condition too, Miqobot allows me to play to a similar standard for raiding that I used to be able to play at. I play on both keyboard/mouse and controller and the pain I suffer is way lower when using a controller, it takes more getting used to and targeting can be a pain but its completely acceptable. Just thought I would would put that out there for anyone like the OP as it might help you.
