[SirVGParticipant]

Minor updates.

Added new waypoint by 309
Changed boom point to 391 instead of 309 to try to solidify going after a mining enemy and not got stuck on a tree as well.

Adjusted waypoint 112 to better hit the tornado.
Adjusted waypoint 30 and connected it directly to 28 to avoid getting unable to dismount.
Adjusted waypoint 148 to avoid being unable to dismount.

[SirVGParticipant]

Lyfox wrote:

The branch distance is too short for that section. Its set to 3 and the node is too far from the waypoint to be connected. Set the branch distance to 5 at least.

Holy shit, that was it. I always on my sets just leave on the default 50 and didn’t realize he adjusted it down when he made the original set. I imagine he did it to avoid the wind timed nodes on the SW island. I put it on 20, tried my trimmed set and boom, it picked up node 352 no issues.

HALLELUJAH! THANK YOU!

[SirVGParticipant]

Diadem BTN Issue

I’m absolutely 100% stumped. Whenever the node by 352 is up, Miqobot just flat out ignores it. I have no idea why. It’s not blacklisted, since that resets every time you restart the program. There’s no messages of her trying to reach it and giving up. She just…ignores it. You can see it on the mini-map. You can even use Arbor Call. Nope.

I’ve made a condensed version of the scenario for faster testing (attached). This starts at waypoint 314, which is the first set of nodes you find going clockwise for BTN, and then goes counterclockwise as normal. It’s simply copy/pasted from the full scenario (just chapter 2).

(2:59:35 AM) Scanning for shiny gathering nodes like ‘<anything>’ *.*
(2:59:35 AM) I see a shiny node at (-463.724213, -272.271301, 27.448919).
(2:59:36 AM) Going from 351 to 357 in 5 trips.

I may just have to rewrite the scenario to avoid that node entirely, because it’s messing everything up. The problem if I work the “inside” lane to that point, the next available node won’t be for a ways after that (if I hit the 352/353 one manually the node on the SW island is way on the far east part, near the tornado, instead of the NW part), since they have set distances from each other and rotate around the entire diadem. Each “section” is 8 nodes. So I need to skip every node from 315 to 367/368 on the inside lane, while maintaining the ones on the outside, or else just skip BOTH lanes once I hit 314 and just work my way back towards the entrance to end the loop. I haven’t decided on what yet. This will almost certainly involve rewriting the grid too, though likely just changing paths to work with the altered plan.

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

[SirVGParticipant]

For some reason, Miqo is STILL wanting to go after 357 instead of 352/353, even after adding the move to Waypoint 351. I’m not entirely sure why she keeps doing this, but I might have to redo the scenario a bit to change order.

And even then, she should still see it (since it shows up on the small map when you’re at 358) so I’m frustrated at how to make this work completely. And then sometimes it works without issue.

*bangs head on desk*

[SirVGParticipant]

I noticed that sometimes the scenario would make it around, no problem, sometimes it would get stuck despite the fact it should see a node. I think I’ve solved it, but would like others to help test.

Adjustments:
Moved node 352 a smidge up the tree.
Broke up the scenario to prevent Miqobot from going to 357 before the 352/353 nodes, which breaks the flow.
Added an extra diademBoom after 357 and before going to 358 (should hit wood golem, can hit sprites in weather if dead)

[SirVGParticipant]

All you need to do is change the gathering tab info. You can delete the items in “Gather By Name” and change the gathering node to whatever slot number you want. The grid will work fine for all levels. I just set it up for people working for Expert recipes which are the big cheevo stuff.

[SirVGParticipant]

Sounds like a possible missed node, but without further info like your Miqo logs, I can’t help you much unless I ever run across it myself.

[SirVGParticipant]

Aha, an extra waypoint snuck in next to 169.

Waypoint 391 was unintentional and has been removed. That’s the only change.

[SirVGParticipant]

Made a few small adjustments, mostly to get around the stupid terrain issues which were causing dismounting issues.

Added an extra waymark by 335 and moved 335 to try to avoid getting stuck going for that node. Made one way routes from 335 to 389 and 389 to 336.
Modified 44 to be fly and adjusted its position.
Connected 50 and 45 for another path.
Changed 66 and 67 from mount to foot to prevent hangups by that node.
Added a new waymark to connect between 167 and 168/169 and adjusted positions for waymarks 167-169. One way paths were added between the new waymark and 168/169 and 168/169 and 167 to avoid getting stuck.
Adjusted 146 and 147 to avoid getting stuck unable to dismount.
Adjusted waymark 157 to avoid getting stuck unable to dismount.

I’ve tested some of this stuff, but haven’t gotten to do a ton because of reset day. Hopefully everything will work OK.

Also, like the Botany set, the Yield+2 was added to the Rotation set, and Gather Only is still in here as well.

I’ll continue to modify and test, but let me know if anybody sees any issues that arise.

[SirVGParticipant]

sabriii wrote:

Hey, How can i use the bazooka? 🙂

You need to put the Duty Action I on your hotbar. If you go to Action & Traits (P by default on your keyboard) and go under general, it’ll appear there.

I’ve got some more edits to the grid coming to clean up a few minor issues, not 100% done with it though. Mostly the updates are to fix some issues with Miqobot not being able to land in certain spots when going for certain nodes.

[SirVGParticipant]

Few more minor adjustments. I think I got the last few things squared away.

Added an extra waypoint between 298 and 299 to avoid getting stuck on the tree (and climb the root as intended)
Added an extra waypoint between 7 and 8 to avoid getting stuck on the rock.
Adjusted Waypoints 352 & 353 and made the paths from 352 to 353 and 353 to 354 one-way so the node could be gathered (miqo normally stops short).
Made paths from waypoints 299 to 300 and 300 to 301 one-way.
Added waypoint between 343 and 344 and moved diademBoom point to it in order to better hit the botany enemy instead of the sprite (still not guaranteed if the enemy is down and weather is not normal).

I made a full 3 rounds prior to these minor adjustments and that’s what all I noticed. Outside of very minor interventions I did it with like 25m to spare on the instance timer.

I’ve also changed the default preset to Yield+2, which will use Blessed Harvest II whwnever possible. Cordials are checked. If you don’t wish to use Cordials, uncheck the bos on the gathering tab. I’ve also included the old Gather Only rotation the old sets had as well.

Let me know if any further issues!

[SirVGParticipant]

Randle wrote:

Is it possible I get a copy of these for Slot 3 on both your mining and botany versions? I’ve tried changing things around to harvest slot 3’s and it won’t work, it reverts back to 4 or goes to slot 1.

What you need to change is the gathering preset in the gathering tab. Click on that tab and then either the diadem botany or diadem mining preset (in the scrollbox on the right). Since you want a specific slot and not specific items, double click the “Artisanal Skybuilders'” text in the “Gather By Name” box and hit delete on your keyboard to delete it. Then in the Gathering Node section, just change the number in Slot to whatever you want.

You will need to do both because the “Gather By Name” basically causes Miqobot to ignore the slot entry. I have these set to look for those items specifically because it’s the stuff used for expert crafts.

[SirVGParticipant]

Lots of just little adjustments. I tried fixing the tree (waypoint 260) again by moving it back and changing to foot. That should give it a much bigger space to land on and potentially avoid snags.

I also added a lot of extra waypoints around potential enemies it could pick up around the diademBoom spots, just to avoid getting stuck there. Some points were slightly adjusted to try to make sure only Botany enemies are picked up.

A couple of very minor changes to the scenario to account for these changes.

Only the navigation grid and scenario are changed.

Let me know if you have issues with anything and where they occur.

[SirVGParticipant]

Made a few more minor tweaks. I noticed in a run Miqobot got stuck diademBooming an enemy I didn’t account for, as the expected enemy was down. So I went back and tried to account for every possible enemy around the diademBoom spots and put waypoints and paths from them so she shouldn’t get stuck again.

Also modified the start path so it’s flying around the cabin and not running around it. Should look more natural.

Navigation Grid and Scenario are updated.

Let me know if there are further issues.

[SirVGParticipant]

You can put it on your hotbar and set up a keybind in a scenario. Something like…

key(ctrl+f12, 0.7)

Where ctrl+f12 is whatever keybind you have your food on.

[Author]

Posts