Forum Replies Created
-
Posts
-
Sure, you can do it like this for example:
// ► Duskcourt Cloth ◄
job(WVR)
repair()
startMateriaExtraction()
recipe(Duskcourt Cloth) // ingame Recipe
craftMacro(Duskcourt Cloth) // miqo Recipe
icon(3,12,3) // Food
icon(3,12,3) // Food
// nqhq(balanced) – use this if you need hq mats to guarantee hq items
craft(76)
repeatAll(20)For more info on the nqhq() command check out the Help in Miqo, you can actually tell the bot a ratio of hq/nq mats for each mat in the recipe if you want.
I got this from another thread in the forums but for me pressing ALT while the scenario is running does actually pause it.
At least most of the time 🙂-
This reply was modified 3 years, 4 months ago by
derm.
I’ve been running Trusts/Squadrons basícally 16 hours every day for the past weeks.
Thats not a huge samplesize but i personally think its much safer than for example farming legendary nodes out in the world since you spend most of your time in the dungeons.And i get people being careful but we’re taking it a step too far imo, if i have to watch the bot everytime it runs its not really useful to me. I’m using the bot to save time and doing duty finder on healers/tanks makes literally no sense to me.
Leveling Squadrons/Trusts from 40-80 takes 60+ hrs and im not supervising the bot during that time.
Also fwiw there is only a very slight difference (<5%, usually less than a minute) in completion time running healers/tanks vs running dps.I’m not 100% sure this works in your case but you can set a hotkey to target your Focus. If you set the Exchange NPC in your Focus and it doesnt reset inbetween runs you could use that. It does mean you would need to set the focus target at the start of each run tho.
Alternatively i’ve used the NPCs in Eulmore and made 2 waypoints in a position where each of the NPC is clearly closest. Then you use waypoint(x) inbetween the turnin and exchange and just target the NPCs using F12.
Actually i thought i can just attach my turn in scenario (its yellow scrips tho) and the edited Eulmore grid. Heres a paste if you just want to look it over: https://paste2.org/fd2jN5DD
Maybe you can find something useful in there, i wouldn’t recommend running it though since i haven’t used it in ages. Can’t guarantee it still works.-
This reply was modified 3 years, 4 months ago by
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.
Wow thanks this actually works for me too.
I do appreciate the math done here, but i see a very critical flaw in the math:
The lack of Heat of Battle 2 or 3.
Because hear me out, i earn at least 1,1 mil exp in a Sohm Al. With either the FC buff or the Squadron Scrolls. I daresay using these can reduce the run time for this significantly – espescially abusing rested exp. Might not be an instant do-all-at-once scenario but i daresay it is worth abusing the heck out of rested and the Heat of battle buff.Sorry, it includes Heat of Battle 2, its always on in my FC.
But you’re right about rested xp. I’ve had a couple of Sohm Al runs at ~940k xp and it took me a while to realize it was because of the rested buff. Non rested is between 740-780k for me.
I dont know enough about how xp is earned to explain where the variance comes from but there is some slight variance in xp gain across all runs.
Samplesize is also always an issue. For most of the dungeons i have 5-6 recorded runs, for Sohm Al i stopped at 10 because apart from the rested xp runs everything was hitting the 740-780k range.
The numbers in the first pic are the average of my runs.I also did run Qitana a couple of times and 75-80 takes ~10 hours or 19 runs. ~7.8mil xp in a 33min run.
So doing Holminster and Qitana from 71-80 would take ~18 hours instead of the 24 hours only Holminster wouldve taken.-
This reply was modified 3 years, 5 months ago by
I’ve been leveling my alts over the last couple weeks.
Sohl Al is the only option, i’ve played around in excel a bit and i got the following:
Thats the average of my runs on which the next table is based. These are not perfect by any means but should be close-ish.
I’m using the preorder earring and 3% food.
Here is how the above data works out while running the dungeons. It’s split between the time spent in the dungeon and the number of runs per level.
Running Sohm Ol from 53-71 takes ~39 hours or 124 runs.
I didn’t log the first alt i got to 80 so i dont have data for Qitana Ravel yet but compared to that just doing Holminster 71-80 (Trusts) would take 24 hours or 43 runs, Qitana would cut that down by a bit though.There is a thread by r51093 that has a scenario to run the squadrons and sell the items at the gc vendor.
I’m using an edited version of his Scenario but it does work, it just takes some time.Whats missing most for me personally is:
– runChapter(4), a way to skip chapters within a Scenario
– runScenario(Name), a way to run different Scenarios within a Scenario and then go on with the original Scenario.
I realize that there is conflicts with workFor() for example but the option of having a library of small Scenarios and being able to call them basically like functions would be amazing.
– being able to move the Scenarios within the list in Miqo. “Right Click/Move Up” or something?I mean in a perfect world i’d like to be able to define variables etc but “small improvements” would be nice to have QoL tweaks.
And i’m not trying to hate just raising my hand to show some interest. Still love the bot 🙂You were just lucky. There are people who got banned by running 24/7. Dont do that.
See? 😀
But i don’t think anýone who cares about getting banned should be doing what i do.
To be fair i basically do modify any grid i actually run for any longer timeframe. Not to avoid detection tbh just to optimize it.So before i started using Miqo i was gathering legendary mats and noticed that its literally just bots.
I mustve sent out 100+ reports over the next week since its sooo easy to see, everybody arrives at the nodes at the exact same time, leaves at the exact same time and takes basically the same grid.Nothing ever happened so i said fuck it and googled ff14 bots. First using the bot i used it for a couple of months literally 24/7 (which people tell you not to do) but nothing ever happened.
So maybe im just lucky or maybe they dont give a single fuck.Yup you would have to put the line twice. I think 1.5sec delay is ok for food but you should double check it works.
Also i made a mistake with the workFor(29:00), that would be 29 hours. Instead it should be workFor(00:29). And if it only crafts one just put a high number into it like craft(100) it should stop after 29min.And im not sure you can make it stop by realising the inventory is full. Maybe there is some creative way but i cant think of any right now.
But you could just count your inventory spaces, let it craft for 30min, math it out and use repeatAll(x) accordingly.Yes, you can try to create a scenario like this:
solverPreset(recommended) // you said you use the recommended preset job(BSM) // choose your job recipe(Grade 4 Artisanal Skybuilders' Chocobo Weathervane) sendIcon(2, 1, 1.5) // eat your food, in this case it would be Hotbar 2, Button 1 with a 1.5sec delay workFor(29:00) // make the next action last 29 min craft() // next action -> craft for 29 min repeatAll(10) // would repeat the whole thing 10 timesyou could use food twice and make it last 58-59 minutes and put a repair in there to be safe if you want.
Yes, these functions are already planned for implementation along with the rest of Scenario Engine updates.
Honestly i assumed you already were while writing this but still decided to keep it.
Thanks 🙂Defining variables is a step towards making scenarios unnecessary complex, and this is something we would like to avoid.
But we will try to implement a similar functionality.Completely understandable.
– useCorials(0/1)
This setting is activated or deactivated automatically as a part of gatherPreset() function. You can also use a cordial via sendIcon() function.
Additional function with automatic hotbar slot detection is planned as well.To be honest my use case here is lazyness. I have lots of imported gathering presets with different settings from different people. I wouldve liked a way to just define it within a scenario without having to go through all the presets and manually changing them 😀
– if the Scenario Engine gets expanded an option to reorganize the scenarios/chapters would be nice.
Yes, this feature is already planned.
Thank you for your feedback.<3
Would you please clarify your request? Miqobot offers two crafting methods, Macro Crafting and Crafting Solver. Which of them do you wish to be improved exactly?
*i moved this to the end because of the pictures*
In the rotation tool for gathering you can use the skills on the left to build your rotation and save multiple different rotations. The ones you call with gatherRotation().
Right now you can use macros, but you dont ‘build’ it through the menu, you tell miqo what buttons to push. Now if i export it and give it to a buddy he would have to rebuild my exact hotbar setup for the macros to work. And especially the high end macros are kinda long.First pic should be of the gathering rotation menu, 2nd of the crafting macro.
I cant find a preview button so i really hope i didnt completely mess the quotes up btw.
Hey,
just thought id give a little feedback after my first couple weeks of usage. First off i really like the bot, right now i actually enjoy playing around with it more than i do playing the game.
But heres a couple of things id like to see:
– a notes section like on the navigation page for the crafting tab. It would be nice to keep track of needed Stats/food or similar things.
– in a perfect world id love to see a rotation tool for the crafting tab (like the gathering one). it works perfectly fine like it is but something like that would make sharing crafting settings easier.
– runScenario(Name) would allow us to easily create a queue of scenarios, or have certain standard scenarios for turn-ins, repair, materia extraction etc. maybe even runScenario(Name, x) where x is the number of times the scenario repeats.
– runScenarioUntil(Name) unless workFor() does the trick.
– toChapter(x) a way to skip chapters without actually deleting them.
– id love a way to define variables even if its just integers. say you write a scenario to gather compontens for and craft item x. you could tweak the numbers while writing the script and declare the desired ammount of the item you want in a variable at the start of the scenario.
– useCorials(0/1) i thought i saw something like this in a script once but i cant find it anywhere.
– if the Scenario Engine gets expanded an option to reorganize the scenarios/chapters would be nice.Btw, if any of that is already possible please ignore it and let me know how 😀
Not to be a dick but a quick search of Mist Spinach, Lemonette or Peppermint all return the grids within the 1st page of results.
The Error tells you that in Chapter 1, Line 5 theres an Error, probably in your Syntax.
If this is your whole scenario then the mistake is within “gatherPreset(mist spinach)”, which in this case would have to be the name of the preset “mist spinach” but if that was the case you would get 2 Messages in a row:
(19:01:46) DEBUG: Name not found. GatherPreset: ‘silve2r ore’
(19:01:46) ERROR (Chapter 17, Line 7): Execution errorSo if you missed the debug message you should check the name of the gathering preset you created, if there is no debug message then this isnt your whole scenario. You should check whats in Chapter 1 Line 5.
With regards to premade scenarios there is a pinned thread in this forum. Go to the Botanist section and try some of the linked scenarios. Especially the white/yellow scrip scenarios since those will contain the unspoiled nodes.
-
This reply was modified 3 years, 4 months ago by
