[😾Participant]

MisterKrabs wrote:

im contemplating using miqobot for some light mindless farming, ive been to depressed and tired to actually do anything in game.
but im also kinda worried ill catch a ban hammer

I have a FC guildmate who is always on, and they only have one lv 80 classes for DOW/DOM but a lot of 80 in DOH/DOL. (This was like last expansion timeframe)

One day, all I said in the FC chat was “Dang, I always see you lol, how are ya?”

Then they whisper me that they are doing great but they are mainly botting. He said that he have a disablitty and can’t play as much but would like to still be useful to the FC since he enjoy the social aspect of the game and love to design the FC house.

I just reply back to him saying that’s cool lol. In my mind, I want to stay as far away from him and this convo as much as possible because I bot like crazy and here he is talking about botting via whisper where it is being logged.

To this day, he is still not banned and our FC coffer is almost at half a billion, and it is all thanks to him.

• This reply was modified 1 year, 6 months ago by  😾.

[😾Participant]

I know it have been a whole day since you made this comment,

But from my experience, running assist with a healer does well in any casual contents (excluding 81-90 since I am in ShB)

[😾Participant]

Slickster wrote:

Works great, thanks a bunch 🙂 Is there an easy way to setup spending of the compressed aether to get extra mats from killing monsters? I would do it manually but there’s no pause option in the miqobot and I don’t want to restart the scenario each time.

If you are doing it for the extra mats, then it is not worth it. If you are doing it for the achievements then that understandable.

But to answer your question, I’m going to say no. There is no easy way to do it effectively with this mesh.

The problem with diademBoom( ) function is that miqo will not shoot if there is no target. So you end up standing there afk for 3 mins. There is no way to change this 3 mins to something like 1 second, meaning using diademBoom() for extra mats is not ideal. The obvious con is that you stand there looking like a bot. Because who the heck stop for 3 mins exactly, in the same spot, everytime. If you want to move forward with this, then just add diademBoom( ). It will shoot if it see a target. If there is a way to change the wait time, then this would be a perfect script that will always use Auger, but alas, we cannot at the moment.

So the best way to make use of diademBoom( ) is to move to another area where there are bunch of mobs, so that you can guarenteed mobs shot. The cons of this is that you are losing time moving back and forth to the place with mobs, and the more moving you do, the more liking that the script can break. You also have a higher chance of your inventory slot be filled faster.

In my opinion, I rather have a little less effecting farm with no chance of breaking then a effecting farm with a small chance of breaking. If the script break, then you miss out on hours worth of grind.

[😾Participant]

Slickster wrote:

Can’t edit the above. I’m just stupid and I was hitting start from the gathering tab instead of the scenario tab.

I do have another question though, how do I edit it so it gathers the materials for expert recipes and not the ones for lv80 normal crafts? I have never edited grids or scenarios, so anything ELI5 would be great, thanks.

(I’m assuming it might only need changing all gather(7) to gather(8) but I’m not sure)

the normal lv80 one is needed for the expert recipe as well isn’t? Not sure. But in any case, you just have to add the name of the items you want to gather to the list. I attached a picture so that you can see what I mean. But make sure the name match exactly.

If you leave the “gather by name” blank/empty. Then you can use the gather by slot instead by changing the 0 to #. So for eg. if you change to a 2, it will only gather the item in the 2nd slot everytime.

Hope this helps.

Attachments:

You must be logged in to view attached files.

[😾Participant]

Yes, under the “Combat” tab

there is a pause section, and in there, is a box where you can input your hotkey. For example, I use shift+A for mine.

[😾Participant]

They get saved to a file called “presets.miqo” and that file is located where ever you have the miqobot.exe saved to.

However, don’t delete it from there, that is not fun.

It is best to simply delete it from within the miqobot by clicking “Delete”

[😾Participant]

powder wrote:

occasionally, after the script goes through the re-entrance of the diadem, it targets the guy on the left (turn in vendor) instead of the guy in front and continues to try to que into the diadem until it gets through the scenario, not sure why or how to fix it. adjusting the angles did nothing. It didnt happen every single time but leaving the diadem and trying to let it do its thing resulted in a mis target 7 out of 12 times

the original script by kitty does the same thing as well

ok, the way the scenario talks to the NPC is by using num0. So… the way num0 works is relatives to your position AND your in-game character facing.

And another fun fact, when you leave the diadem, your character get place EXACTLY where you entered. So if you enter from the left or right of Aurvael, it will run to waypoint(68) everytime, messing up the their physical rotation/facing. There is no commmand to rotate your character, resulting in luck if it will break on not. Using waypointPrecise() also wont fix it.

The way to fix this is by entering from waypoint(68) and making sure that you are directly facing Aurvael. Because when you leave Diadem, you will be in the exact spot as you entered. Resulting in the bot not run or move, mitigating the chance of it breaking.

That should fix it for you for both my scenario and Jenpy.

edit: Actually, now that I think about, it is possible to fix this but fixing the mesh, but that would results in your character looking like a bot by making it running away from Aurvael and then back to Aurvael again.

• This reply was modified 2 years, 5 months ago by  😾.

[😾Participant]

Jenpy wrote:

Hey there! Thank you so much for sharing this. I have replicated this into my own Botany version which I would like to share. Because it’s based on a direct copy of your simple miner loop I wouldn’t feel right sharing as my own work!

So here are my versions of your Miner loop (changes: preset titles to align with mine, additions: job change, materia extraction, yield+2, and slot 3 items specified) and my Botany version!

Thanks again!

Thanks for the shout out, but more importantly, thank you for the share!

Feel free to start another thread that way more people can see it.

[😾Participant]

powder wrote:

Is your script intentionally farming the lvl 60 nodes over the lvl 80 ones or have i done something wrong

Miqo will mine the first one by default. You going to have to make a new gathering preset.

Go to “Gathering”
Click “new”
Name it whatever you want.

Add in these five (copy and paste exactly one by one) ———- or add in what ever you are trying to gather.

Grade 4 Skybuilders’ Truespring Water
Grade 4 Skybuilders’ Mineral Sand
Grade 4 Skybuilders’ Bluespirit Ore
Grade 4 Skybuilders’ Gold Ore
Grade 4 Skybuilders’ Finest Rock Salt

Click “overwrite” in order to save.

Edit: I attached it if you want to import instead.

• This reply was modified 2 years, 5 months ago by  😾.

Attachments:

You must be logged in to view attached files.

[😾Participant]

tkin wrote:

I saw someone else asked about Botany already. My apologies. I need to figure out what some of these commands do. I see “gather(7) gathers from 7 different nodes, but I don’t see how it figures out the waypoints between.

gather() means start mining. gather(7) means gather 7 full nodes.

How does it knows where to go? Because of the mesh. So… if the average player are trying to find the next gatherable node, they would use “Lay of the Land” which will show them where to go and how far away the ndoe is.

However, Miqo doesn’t need to use Lay of the Land because it can see the available nodes that are nearby.

Now, let say you are botting with Miqo, and it see that there is a node nearby. It does not go to it, if the mesh doesnt take it there. So it will ignore that one and move to the one that is nearest to the waypoint on the mesh.

Below is an example:

gather(7)
Miqo will gather seven times.
Miqo see two nodes nearby. Let say… one is 30 yalms away and one is 10 yalms away.

However, the 10 yalms node is not on the mesh, but the 30 yalms is. Therefore, she will walk/fly/mount to the 30 yalms one since she knows how to get there, as appose to the 10 yalms one since she doesnt know how to get there.

tl;dr The mesh tell miqo where to go for the next one.

Hope this helps.

Edit: The 10 yalms and the 30 yalms nodes is kind of a bad example since miqo will attempt to walk off branch. But the logic still stands. You can adjust this limit under “navigation”, in “max branch distance”

• This reply was modified 2 years, 5 months ago by  😾.

[😾Participant]

under chapter 2, add in your gatherRotation() Click the ? to find out how gatherRotation() works in more details, but to sum it up, it use the name from your gather rotation in the “gathering” tab of miqo.

Anyway, you will have to make two rotation for this works. One rotation that will only do king’s yield II, and the other rotation to just gather. In this example, I am going to pretend to make two new rotation call first7 and Yield +2.

for example

waypoint(1)
randomAfkFor(1, 2)
gatherRotation(first7) <<<<< name of your rotation that will do the node 1 to node 7
gather(7)
randomAfkFor(1, 2)
waypoint(47)
gatherRotation(Yield +2) <<<<< name of your gather rotation that will do king’s yield II
gather(1) <<<<< this is node #8, aka the last node, so make sure your rotation is swap to the king yield II rotation before reaching this line.
randomAfkFor(1, 2)
waypoint(55)
repeatChapter(39)

Let me know if you still have questions. I am not very good at explaining.

[😾Participant]

Unfortunately no. That one was on my old computer which randomly decides to die so everything on there is lost.

[😾Participant]

Oh, incase you want it to do the auger, the command is diademBoom() If you are trying to add this in for faster skyward points. I do not recommend, but if you it there for the achivements, then feel free to add them in, but keep in mind that it will not be optimal since miqo will always wait up to 3 mins if there are no targets. And in case you didn’t know, every 8 nodes = roughly 1 bar, or 1 auger shot.

If you are using the auger, make sure you have a lot of inventory spaces. If filled up very quick with augur. You don’t want to lose time trying to farm mats with no spaces.

[😾Participant]

ffxivnewbiebot pretty much said it all. I also second on using the “?” for help, it explains everything.

To quickly answer your questions: It is chapter 4 that put you back into diadem. It walks to NPC and talk to the NPC using num keypad. Those num should be the default keybinds. If you change them, then you going to have to adjust your keybinds or edit the scenario to match your keybinds.

But to explain this particular scenario in details…

First chapter is basically afk, repair, and go to waypoint >>> leading to the island loop.

Second chapter is basically the bot doing the loop. gather() is basically it’s gathering that many times. Gather(7) will be gather 7 times. You are probably wondering why not put gather(999) or something like that. Welp, Miqo cannot see gather nodes outside of certain amount of yalms. I think maybe 100 or 300 yalms away is max? Which is why, after gather(7), I have to move her to the next node, which is waypoint(47), then finally finishing off the island loop with gather(1), then make her move to the beginning of the loop to waypoint(55). Now, to repeat the whole cheapter, I just use repeatChapter(). I am using repeatChapter(39) because doing the loop 39 times roughly = to about 170 mins. This is important to note. If you are gathering for too long, and the 180 mins is up. You are force out. Miqo will then break because she can’t find any nodes there by. If it’s too short, then you are not being optimal and leaving and going back in too many times.

Third chapter is baiscally dismount, and leave dungeon using the default U key.

key(u, 2) >>> means press U, wait 2 seconds
key(num4, 2) >>> means press 4, wait 2 seconds
key(num0, 1) >>> means presss 0, wait 1 seconds
key(num4, 1) >>> means press 4, wait 1 seconds
key(num0, 1) >>> means presss 0, wait 1 seconds

The wait time is needed or she will press too fast or too slow.

Fourth chapter is walk to NPC, adjust the angle, pressing num0 to intereact with NPC and I’m sure the rest is pretty much self explanatory. RepeatALL(15) will do all the chapters 15 times. This is more than 8 hours, it is 45 hours. 15 is just a random number I put there.

Me, personally, have my own threshold of botting, I like to do 6-8 hours a day, skipping botting every 3 days. If you want to bot for over 24 hours, then that’s your prerogative. But I’m a coward who scares of losing my account.

Hopefully this help.

• This reply was modified 2 years, 5 months ago by  😾.
• This reply was modified 2 years, 5 months ago by  😾.

[😾Participant]

Don’t want to hijack someone else thread. So I will go off topic this once.

It is uploaded to another thread.

[Author]

Posts