[KrudeParticipant]

Got another weird one. Doesn’t even seem to be a dismount issue, probably a LOS one somehow.

(03:19:49) I see a shiny node at (645.022522, -146.452194, 225.591400).
(03:19:49) Going from 197 to 203 in 4 trips.
(03:19:53) 3 trips more..
(03:19:59) 2 trips more..
(03:20:00) 1 trip more..
(03:20:02) Destination reached!
(03:20:04) Not enough GP for this rotation: 427 of 500 required.
(03:20:04) Hitting that poor node. :3
(03:20:12) Hitting that poor node. :3
(03:20:19) My precious shiny sparkles! (2/4)
(03:20:19) Scanning for shiny gathering nodes like '<anything>' *.*
(03:20:19) I see a shiny node at (634.364502, -88.834717, 225.453201).
(03:20:20) Going from 203 to 210 in 4 trips.
(03:20:23) 3 trips more..
(03:20:27) 2 trips more..
(03:20:28) 1 trip more..
(03:20:29) Destination reached!
(03:20:37) I give up - can't find that gathering node :(
(03:20:37) Scanning for shiny gathering nodes like '<anything>' *.*
(03:20:37) I see a shiny node at (634.364502, -88.834717, 225.453201).
(03:20:38) Going from 210 to 210 in 1 trips.
(03:20:40) 1 trip more..
(03:20:40) Destination reached!
(03:20:48) I give up - can't find that gathering node :(
(03:20:48) Scanning for shiny gathering nodes like '<anything>' *.*
(03:20:48) I see a shiny node at (634.364502, -88.834717, 225.453201).
(03:20:49) Going from 210 to 210 in 1 trips.
(03:20:51) 1 trip more..
(03:20:51) Destination reached!
(03:20:59) I give up - can't find that gathering node :(
(03:20:59) This node is just bugged, I see no reason coming back here. Blacklisted. :3
(03:20:59) Scanning for shiny gathering nodes like '<anything>' *.*
(03:20:59) I see a shiny node at (642.026123, -45.861450, 223.571594).
(03:21:00) Going from 210 to 214 in 4 trips.
(03:21:03) 3 trips more..
(03:21:06) 2 trips more..
(03:21:07) 1 trip more..
(03:21:09) Destination reached!
(03:21:11) Hitting that poor node. :3
(03:21:19) Hitting that poor node. :3
(03:21:23) My precious shiny sparkles! (3/4)
(03:21:23) Scanning for shiny gathering nodes like '<anything>' *.*

(This is where she gets stuck forever)

• This reply was modified 4 years, 3 months ago by  Krude.
• This reply was modified 4 years, 3 months ago by  Krude.

[KrudeParticipant]

When in the scenario tab, hit the ? button for a list of all commands and how they work.

[KrudeParticipant]

I mean anything that at least brings fishing up to somewhere close to the rate of MIN/BOT. I can leave Miqo running MIN for 3 hours with the infinite scenario and come away with a cool ten thousand points or so.

I left Miqo to fish for a round until the fishes got wary and could count the number of expert fishes i caught on one hand and got sub-1000 points.

[KrudeParticipant]

Looking forward to your solution for the 500k fishing achievement because HOO BOY, that is an insane grind.

[KrudeParticipant]

Here’s another node blacklist i found today:

(08:32:23) Adventure calls! I have to travel far away. (Grid: 'diadem mining grid', Waypoint: 145)
(08:32:23) Going from 145 to 145 in 1 trips.
(08:32:27) 1 trip more..
(08:32:27) Destination reached!
(08:32:30) Gathering started.
(08:32:30) 	Max node count: 8
(08:32:30) Scanning for shiny gathering nodes like '<anything>' *.*
(08:32:30) I see a shiny node at (451.373688, -638.102417, 194.701599).
(08:32:30) Going from 145 to 147 in 3 trips.
(08:32:32) 2 trips more..
(08:32:33) 1 trip more..
(08:32:33) Destination reached!
(08:32:41) I give up - can't find that gathering node :(
(08:32:41) Scanning for shiny gathering nodes like '<anything>' *.*
(08:32:41) I see a shiny node at (451.373688, -638.102417, 194.701599).
(08:32:42) Going from 147 to 147 in 1 trips.
(08:32:44) 1 trip more..
(08:32:44) Destination reached!
(08:32:52) I give up - can't find that gathering node :(
(08:32:52) Scanning for shiny gathering nodes like '<anything>' *.*
(08:32:52) I see a shiny node at (451.373688, -638.102417, 194.701599).
(08:32:52) Going from 147 to 147 in 1 trips.
(08:32:54) 1 trip more..
(08:32:55) Destination reached!
(08:33:02) I give up - can't find that gathering node :(
(08:33:02) This node is just bugged, I see no reason coming back here. Blacklisted. :3

I really don’t know how Miqo landed at that node to not be able to reach the gather point there… Maybe landed too far behind the rock, walked into range but not into LoS and couldn’t mine? Maybe jiggering around the points slightly will help.

[KrudeParticipant]

That depends – have you watched the process? Is it actually entering the Diadem that’s a problem, or is it leaving? I’ve had problems with leaving Diadem reliably by navigating throuhg the portal. Both in this scenario and the mining one. So there’s a couple things that could go wrong.

1) Miqo doesn’t hit the exit portal quite right, doesn’t leave the Diadem properly, and so can’t re-enter. The scripting continues, the bot gets kicked out of the instance shortly afterwards due to the timer, and miqo is stuck in front of the Diadem NPC.

2) If Miqo actually gets out on time and the cursor naviation for re-entering still breaks, it could be either: a) you moved the mouse which resets the UI cursor (even when the game is in the background), which fucks up the scripting, b) any UI windows were still open so Miqo can’t properly select the NPC and re-enter, c) your loading screen was longer than the afkFor() time and Miqo initiated the re-enter scripting before you were out of the loading screen.

These are my solutions to those problems:

– Put in a job change before you talk to the Didem NPC. This closes any errant windows in case you ever get thrown out weirdly, and enables Miqo to get back in when she reaches this scenario part.

– Check how long your loading screens take and adjust the afkFor() times for leaving and entering. Add in some buffer in case of server lags or whatever. To be safe, jsut enter double the time that you actually see them take. I set the time to 12 seconds to be safe. What’s a few more seconds every 3 hours compared to a broken script?

– This is the big one: Don’t leave Diadem through the portal. At the end of the round, just open the duty finder window and leave through there. This way, you don’t have to hope that Miqo hits the portal jsut right to bring up the exit dialog.

– The entire exit and re-enter sequence is still very susceptible to mouse movement. Every movement resets the keyboard cursor and desyncs the UI interactions. It’s just how Square-Enix programmed the game. You should either minimize the FFXIV window while running the scenario (putting it in the background is not enough) or, if you really want to watch during it, not interact with your PC at all.

This is what my exit sequence looks like at the end of the day:

// -> Exit Diadem
key(p, 1)  // duty finder
key(num4, 1)
key(num0, 1)
key(num4, 1)
key(num0, 1)
afkFor(00:00:12)
// Outside of Diadem
job(BTN) // closes any windows
key(num0, 1)
key(num0, 1)
key(num0, 1)
key(num0, 1)
key(num4, 1)
key(num0, 1)
key(num4, 1)
key(num0, 1)
afkFor(00:00:12)
repeatAll(10)

[KrudeParticipant]

Encountered a weird one today:

(07:08:36) I see a shiny node at (-106.733398, -546.101990, -14.249030).
(07:08:37) Going from 292 to 296 in 5 trips.
(07:08:42) 4 trips more..
(07:08:44) 3 trips more..
(07:08:46) 2 trips more..
(07:08:48) 1 trip more..
(07:08:48) Destination reached!
(07:08:52) Hitting that poor node. :3
(07:09:06) My precious shiny sparkles! (3/4)
(07:09:06) Scanning for shiny gathering nodes like '<anything>' *.*
(07:09:06) I see a shiny node at (-91.524498, -600.214417, -18.227560).
(07:09:07) Going from 296 to 303 in 4 trips.
(07:09:10) 3 trips more..
(07:09:12) 2 trips more..
(07:09:13) 1 trip more..
(07:09:24) Sorry, can't dismount :(
(07:09:24) Destination reached!
(07:09:31) I give up - can't find that gathering node :(
(07:09:31) Scanning for shiny gathering nodes like '<anything>' *.*
(07:09:32) I see a shiny node at (-91.524498, -600.214417, -18.227560).
(07:09:33) Going from 303 to 303 in 1 trips.
(07:09:33) 1 trip more..
(07:09:44) Sorry, can't dismount :(
(07:09:44) Destination reached!
(07:09:51) I give up - can't find that gathering node :(
(07:09:51) Scanning for shiny gathering nodes like '<anything>' *.*
(07:09:51) I see a shiny node at (-91.524498, -600.214417, -18.227560).
(07:09:52) Going from 303 to 303 in 1 trips.
(07:09:52) 1 trip more..
(07:10:03) Sorry, can't dismount :(
(07:10:03) Destination reached!
(07:10:11) I give up - can't find that gathering node :(
(07:10:11) This node is just bugged, I see no reason coming back here. Blacklisted. :3

Somehow, it got stuck on node 303 and couldn’t dismount.

I tried to replicate it and couldn’t do it, so it seems to be a rare issue. I have no idea what’s causing the dismount issue in the first place.

[KrudeParticipant]

I haven’t tried the full overhaul yet, but with the tornado adjustments, the DiademBoom log fix and the moved node 389 i did on v1.05, i’ve run three complete scenario repeats (that’s 9 laps i think) without an issue now.

Seems like it should be as good as it gets now.

[KrudeParticipant]

You should check the exact in-game name of the cotton bolls again. Pretty sure you have a typo in there somewhere if miqo doesn’t recognize it.

[KrudeParticipant]

Here’s another one unreachable node late in the lap:

(02:37:14) Adventure calls! I have to travel far away. (Grid: 'diadem mining grid', Waypoint: 323)
(02:37:15) Going from 330 to 323 in 3 trips.
(02:37:17) 2 trips more..
(02:37:28) 1 trip more..
(02:37:28) Destination reached!
(02:37:34) Gathering started.
(02:37:34) 	Max node count: 4
(02:37:34) Scanning for shiny gathering nodes like '<anything>' *.*
(02:37:34) I see a shiny node at (-486.014496, 608.308594, 327.447906).
(02:37:35) Going from 323 to 389 in 4 trips.
(02:37:37) 3 trips more..
(02:37:38) 2 trips more..
(02:37:39) 1 trip more..
(02:37:39) Destination reached!
(02:37:40) Ummm. I don't see any sparkles here :(
~~~
(02:37:54) Ummm. I don't see any sparkles here :(
(02:37:55) I give up - can't find that gathering node :(
(02:37:55) Scanning for shiny gathering nodes like '<anything>' *.*
(02:37:55) I see a shiny node at (-486.014496, 608.308594, 327.447906).
(02:37:56) Going from 389 to 389 in 1 trips.
(02:37:56) 1 trip more..
(02:37:56) Destination reached!
(02:37:56) Ummm. I don't see any sparkles here :(
~~~
(02:38:10) Ummm. I don't see any sparkles here :(
(02:38:11) I give up - can't find that gathering node :(
(02:38:11) Scanning for shiny gathering nodes like '<anything>' *.*
(02:38:11) I see a shiny node at (-486.014496, 608.308594, 327.447906).
(02:38:12) Going from 389 to 389 in 1 trips.
(02:38:12) 1 trip more..
(02:38:12) Destination reached!
(02:38:12) Ummm. I don't see any sparkles here :(
~~~
(02:38:25) Ummm. I don't see any sparkles here :(
(02:38:25) I give up - can't find that gathering node :(
(02:38:25) This node is just bugged, I see no reason coming back here. Blacklisted. :3

I only saw this in the log afterwards but from checking the area out, it seems that miqo pathes from the flying “scouting” position to landing on a rock and is supposed to jump downwards from 335 to 389 (there’s a one-way line there). When she lands on 335, she doesn’t walk forward far enough to fall down the rock though, and can’t reach the node right underneath her.
There’s another way she could fly down there but it’s a one-way line in the different direction (just tested – because otherwise she gets stuck on the rock hump and can’t dismount), so she lands on top of the rock every time and gets stuck there.

From my testing, 389 needs to be dropped pretty far back for miqo to walk towards it enough that she falls down from the rock.

[KrudeParticipant]

Something else i noticed:

At eaypoint 364, if the golem it wants to boom isn’t there, it tries to go for a proto nocti nearby south that’s behind a big fallen log that miqo can’t get past.
It might be better to move point 364 slightly more north, where there’s also a cobly spawnpoint, so miqo goes for that one instead of the nocti plant.

[KrudeParticipant]

I think there’s a way around the jankiness of the tornados, but it requires a bit more micromanagement for waypoints. This means you can’t tell miqo to pathfind up the tornado automatically.

You set Miqo up to walk to a waypoint in front of a tornado (not in it), so that she ends up facing the tornado. Now, instead of letting her pathfind up the tornado automatically, you just tell her to walk forward for 1 or 2 seconds, with

holdKey(w, 2.0)

She should walk into the tornado and get flung up. Maybe tell her to idle for a couple of seconds to reach the top of the really long ones, then you just tell her to resume finding the next waypoint.
Problem is you need to make sure she’s at the top before you continue navigation and not still “in flight” or that will mess up the pathfinding.

edit: For the one 216 -> 219 error i had above, i’ve got the following solution that should work:

waypoint(216)
angle(3) //turn towards tornado
holdKey(w, 2) // walk forward
afkFor(00:00:12) // tornado takes roughly 12 seconds
waypoint(219) // continue pathing after landing 

• This reply was modified 4 years, 4 months ago by  Krude.

[KrudeParticipant]

Yeah that’s the one. I ‘fixed’ it by putting the tornado waypoint closer to the edge and still on land, so Miqo can’t miss it. This means that sometimes she won’t walk forward enough to trigger the tornado jump, so i set node 113 to “fly” instead of “mount” so Miqo can manually fly up there if the tornado doesn’t work.

But then i found the next blackout at node 215 -> 219…

edit: this one seems much harder to replicate, i’ve tested that route a few times now and it works, but it definitely killed my miner run yesterday evening. These tornados are frustratingly unreliable.

• This reply was modified 4 years, 4 months ago by  Krude.

[KrudeParticipant]

With the branch distance set to like 10 to fix that one node, this grid seems pretty much perfect now. I had it run for 7 to 8 hours continuously without a problem now.

BTW, if you’re creating / tweaking a grid, it’s useful to go into Miqo’s 3D Radar and set it to show “gathering nodes”. If you run that together with the grid editor, it’ll show you the branch lines from each waypoint towards a node if they’re close enough. This way, you can tweak the max branch distance so every node is reachable from a waypoint, but it’s not so large that Miqo tries to reach a node from a waypoint too far away and gets stuck in terrain.

[KrudeParticipant]

Miqo sometimes blacks out going from node 111 to 113.
If the jump tornado catapults your character before miqo “reaches” the node on it (112 i think?), she gets flung up to the upper island, then try to gets back down to that node she missed, gets stuck on terrain, and eventually the killswitch triggers.

[Author]

Posts