[HikarinParticipant]

Nvm. I was dumbdumb. I wasn’t actually using the scenario, but I was using the gathering tab one instead.
Please ignore.

[HikarinParticipant]

(11:26:29 AM) Going from 0 to 3 in 4 trips.
(11:26:32 AM) 3 trips more..
(11:26:35 AM) 2 trips more..
(11:26:40 AM) 1 trip more..
(11:26:40 AM) Destination reached!
(11:26:40 AM) Scanning for shiny gathering nodes like ‘<anything>’ *.*
(11:26:40 AM) I see a shiny node at (-509.930115, 846.148315, 127.120201).
(11:26:40 AM) Going from 3 to 7 in 3 trips.
(11:26:43 AM) 2 trips more..
(11:26:45 AM) 1 trip more..
(11:26:45 AM) Destination reached!
(11:26:47 AM) Selecting slot -> 3
(11:26:48 AM) Using action: (Start)
(11:26:48 AM) Using action: (Scrutiny)
(11:26:54 AM) Using action: (Scour)
(11:26:58 AM) Using action: (Scrutiny)
(11:27:01 AM) Using action: (Meticulous)
(11:27:06 AM) Using action: (Meticulous)
(11:27:09 AM) Using action: (+1 Attempt)
(11:27:12 AM) Using action: (Finish)
(11:27:12 AM) Hitting that poor node. :3
(11:27:21 AM) My precious shiny sparkles! (6/150)
(11:27:21 AM) Nom-nom a 200 GP cordial :3
(11:27:21 AM) Scanning for shiny gathering nodes like ‘<anything>’ *.*
(11:27:21 AM) No gathering nodes around. But hey, there’s a beacon over there for me ->
(11:27:21 AM) Going from 7 to 14 in 4 trips.
(11:27:25 AM) 3 trips more..
(11:27:28 AM) 2 trips more..
(11:27:39 AM) 1 trip more..
(11:27:39 AM) Destination reached!
(11:27:39 AM) Scanning for shiny gathering nodes like ‘<anything>’ *.*
(11:27:39 AM) I see a shiny node at (-625.635071, 654.718811, 120.744598).
(11:27:40 AM) Going from 14 to 10 in 3 trips.
(11:27:40 AM) 3 trips more..
(11:27:43 AM) 2 trips more..
(11:27:45 AM) 1 trip more..
(11:27:45 AM) Destination reached!
(11:27:47 AM) Not enough GP for this rotation: 447 of 700 required.
(11:27:47 AM) Hitting that poor node. :3
(11:27:48 AM) Hey, I can’t collect with 0 rarity :/
(11:28:03 AM) Hey, I can’t collect with 0 rarity :/
(11:28:18 AM) Hey, I can’t collect with 0 rarity :/
(11:28:33 AM) Hey, I can’t collect with 0 rarity :/
(11:28:48 AM) Hey, I can’t collect with 0 rarity :/
(11:29:03 AM) Hey, I can’t collect with 0 rarity :/
(11:29:19 AM) Hey, I can’t collect with 0 rarity :/
(11:29:34 AM) Hey, I can’t collect with 0 rarity :/
(11:29:49 AM) Hey, I can’t collect with 0 rarity :/
(11:30:04 AM) Hey, I can’t collect with 0 rarity :/

[HikarinParticipant]

Sorry, not entirely sure what you mean.

Do you have the extract materia command on your hotbar?

[HikarinParticipant]

Update:

For people downloading for the first time, this is the latest version.

An update has been for the Rutilated Quartz grid as it had some issues. I tested it, briefly, but it should work fine now.

Note:
Either download and replace the whole scenario, or download the grid separately.
*You will need to manually remove the old “Rutilated Quartz” grid and this new one.

Attachments:

You must be logged in to view attached files.

[HikarinParticipant]

Brykin wrote:

i’m sorry to say but v2 is not working for me at all, it stays afk all the time and i dont know what do with it

What does the Miqobot logs say? And are you choosing the correct chapter to begin the scenario based on the current ET hour?

When you start the scenario, you have to choose the chapter based on the current ET hour. So if you choose to start from Chapter 1 while it’s like 23:50ET, then the bot will AFK for 24 ET hours (about 70 minutes real life), because chapter 1 starts from 23:30ET.

I assume that’s what you’re experiencing. If the Miqobot logs show errors, then that’s another thing. But if it says something like, “afk for xxxxx seconds”, then you started on the wrong chapter.

[HikarinParticipant]

Nowlflr wrote:

Also, I get this on chapter 17 when it is extracting materia and it then just stops (what am I doing wrong?):
(12:21:58 PM) All gear repaired ^_^
(12:22:00 PM) Left to materialize: 7
(12:22:01 PM) A suspicious error…
(12:22:03 PM) Left to materialize: 6
(12:22:04 PM) A suspicious error…
(12:22:07 PM) Left to materialize: 5
(12:22:08 PM) A suspicious error…
(12:22:11 PM) Left to materialize: 4
(12:22:12 PM) A suspicious error…
(12:22:14 PM) Left to materialize: 3
(12:22:16 PM) A suspicious error…
(12:22:16 PM) Oh no, I broke something. Too many errors 🙁
(12:22:16 PM) ERROR (Chapter 17, Line 9): Execution error

Then does the same exact thing on chapter 19.

Not sure, I haven’t seen that happen. Been able to run it fine for over 9 hours straight.

Are you sure had enough inventory space? Or perhaps just restart Miqo?

[HikarinParticipant]

Nowlflr wrote:

How do I know when to start the scenario so the times line up? I started it too close to 12 because it wanted to sit afk an entire day before it would start again.

You can start anywhere (any odd numbered chapter) that comes next from the current ET time.

However, you need to consider 30 ET minutes before the node opens. So, if it’s 10:30, then you can start at Chapter 13 (12:00 ~ 14:00. However, if it’s 11:25, then you have to start from Chapter 15 (14:00 ~ 16:00), because you try to start with Chapter 13 at 11:25, the chapter will most likely hit the “afkUntil(11:30et)” command after 11:30, which will result in the bot AFK’ing for an entire 24 ET hours until the NEXT 11:30.

So just keep that in mind. But really, you can start anywhere.

[HikarinParticipant]

astynome wrote:

For the Tertium grid, I bypassed ’23,beacon’, went to ‘0,foot’, dismounted, then mounted back up, and returned to ’23,beacon’ to finally wait for the node. Thought that was unnaturally weird but can’t figure out how to fix it.

Hmm.

Sometimes things like that happen when there’s a sudden lag spike or FPS drop when the bot tries to do something.

Anyways, I wanted to adjust the route a bit anyways, so I made an update. I haven’t tested it yet though.

• This reply was modified 2 years, 1 month ago by  Hikarin.

[HikarinParticipant]

Go to “navigation”, and on the right side you’ll see a list of “grids”. Look for the “Ilmenite” grid. All the grids from my scenario are named after the materials that each grid is for.

So once you find the “Ilmenite” grid, click on it once and then click “delete”.

• This reply was modified 2 years, 1 month ago by  Hikarin.

[HikarinParticipant]

I have updated the Ilmenite grid.

Please remove the old grid and add this one.

[HikarinParticipant]

Update;
During my stress test, it ran into a weird trap about 6 hours in. I’m not entirely sure what happened, but it happened with the Ilmenite route on Mare Lamentorum. My character was stuck between some rocks, though it should have been flying over it.

I adjusted the route a bit, and I’ll post an update after a few tests.

• This reply was modified 2 years, 1 month ago by  Hikarin.

[HikarinParticipant]

I don’t know why, but I can’t find the edit button on the post anymore…

Anyways;

Notes:
1. Every “even number” chapter has “sendKey(g, 2.5)”. This is for cordials. If you want to use cordials, either assign to the G key, or change the key yourself (in every even chapter). If you don’t want to use them, either delete the entry, or don’t assign anything to the G key.
2. Only on chapter one, it has “sendKey(ctrl+num6, 2.5)”. This is for the spiritbond potion. Do the same as above.
3. On chapters 1/11/23/25/47/59/71, it has “sendKey(ctrl+num9, 2.5)”. This is for food. Again, do the same as above.
4. I noticed that sometime, depending on how many materia extractions are done at one time, the bot seems to skip 1 or 2 at the end. So each odd chapter will attempt to extract materia twice.
5. The scenario is set to move the chapter near the nodes 30 ET minutes before the node appears.

Also, small update to V1.1 and V2.1.

I will be doing a full stress test (over 6 hours) over the night. Hopefully things go well.

Again, if you find any issues, please let me know.

• This reply was modified 2 years, 1 month ago by  Hikarin.
• This reply was modified 2 years, 1 month ago by  Hikarin.

[HikarinParticipant]

I honestly would use minion. Sure it costs a bit more upfront, but it has quite frankly, far superior features overall.

I don’t use it because it can’t be used with Dalamud plugins and XIVAlexander. That’s the only unfortunate downside. If it wasn’t for that, I’d be using minion.

[HikarinParticipant]

I’ve been using a gathering scenario for timed nodes and I made it spiritbond effecient. It’s able to extract materia every 2-3 nodes.

I leave it on while I sleep and turn if off when I leace for work (about 6 hours). Which comes to tons of materia.

Sell and profit. Made 20 mil in 10 days or so. This is also when I stock some materia for myself for future pentamelds.

You can find the scenario in the forums.

[HikarinParticipant]

khmmiqobot wrote:

The overlay is part of it. But, it’s also the memory/routine load that Miqo does that might give some people FPS issues. if you are running around 16MB of RAM or less, you’ll see most of the problem. Windows hogs a significant amount. When the memory load gets to a certain threshold, applications will start stalling/stuttering. Unfortunately, there’s not a lot of fix to this if it’s a physical RAM issue. But, you can try one thing that might help clear up the RAM a bit:

– Press Win+R
– Type “regedit”
– Go to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Session Manager > Memory Management
– Find “ClearPageFileAtShutDown” and change value to 1″
– Restart

The only downside to this is that restarting your computer will take a bit of time since it is now clearing your page file.
See if this helps besides turning off 3D radar and other Miqo overlays. If this works for you, you will have to remember to restart the computer when memory usage hits around 70-80%.

Also, make sure you whitelist Miqo’s folder if you are using an Anti Virus and especially if you are using Windows Defender. It will constantly scan in the background that will use a lot of resources.

LASTLY, If you are running FFXIV Teamcraft (desktop version) I strongly suggest removing it, especially if you are auto uploading/downloading information to their site and Universalis. This app will run even if you have it closed.

I have doubts that this is the cause of the issue. I have 32GB of RAM. I’m pretty sure the overlay is just poorly optimized. Not even ACT overlays hogs this much.

[Author]

Posts