Forum Replies Created
-
AuthorPosts
-
Hey SLYG just wanted to let you know real quick. I have been using this scenario with these presets for a couple of days now. I think they work pretty similarly to the OP which is great; however, you do run into the issue of it being set to the number of gather attempts and then just completely skipping a timed node. The mining portion also seems to hit some snags where it actually just sits there, that is fine though as I personally just remove that segment of the scenario.
The last thing I am having problems with is the Diadem Boom segments of the scenario. I am going to try and rewrite them, but it appears that they do not work. All they do is fly back and forth between waypoints a few times (looks very very suspicious as it is in the same line). For now I am removing those as well.
I will say that when it did gather it did a great job! Although it kill switched itself 2 hours in. Is there a way to loop it like the infinite mining one does? I assume its just copy and paste the part of the scenario that does, but figured I would make sure that would not create a conflict first.
You will always trigger the kill switch if you run this scenario continuously for over 180 minutes. The game will automatically kick you out of the duty after your time limit expires.
I’m not sure why diademBoom isn’t working for you. Please check that you are using the latest version. Delete everything from the prior version before updating to the new version. The waypoint numbers will shift if I make any additions or deletions to any of the waypoints numbers that come after, so that would throw the scenario off if you’re using a new scenario, but still using an old grid.
I recently found out that the fishing islands has a lot of mobs, so I changed the diademBoom location to go there. There’s 5 mobs at the new location, so no need to hop between different points.
I’ve been trying my hand at this, I haven’t put it into practice yet but I believe it could be possible. I’m not experienced with scenario creation but hypothetically I believe you could do:
grid(a separate grid to go to a specific timed node)
gatherPreset(a separate preset for said specific time node)
goodWeather(Umbral Levin)
skipBadWeather
gather(1)
grid(DiademP3Botany)
gatherPreset(DiademP3Botany)skipBadWeather makes the next task only 60 seconds if it is anything but the goodWeather that is given, if it doesnt detect a node in the separate grid obviously it wont go, thus ending the task within 60 seconds. reset the grid and gather preset back to the original, and it can continue. you could add two chapters specifically for each weather. would only take two minutes for it to check for them. could split chapter 1 into two parts to check for timed nodes. or just add the timed node chapters after chapter 1, before using diademboom.
Okay, I have kept going and have figured this out. While this may not be efficient this is just how I came to figure it out and after some small testing as worked for me. Again please bear in mind I have very little experience in scenario creation, and grid creation. So it is highly likely this may be inefficient or wrong. But I have attached all necessary pieces that I have constructed. With the exception of the original grids given by OP, obviously.
The scenario checks for both botanist, and miner nodes. Takes about two minutes for a weather check, it does it three times in the scenario. In my own testing it is pretty hard for it to miss a weather window.
– Adjust your food to whatever slot you want in chapter one.
– Be sure to hotbar your gearset for MIN and BTN, as it is needed for the scenario
– I know the grid is ugly and very scuffed, adjust it as needed, or make your ownThanks! I will try adding this to the scenario. If it’s too out of the way, I will comment out the chapters. It may not be optimal for rankings, but would still be useful for getting the achievements.
I only have btn skills on the bar. Not sure why anyone would have other class skills.
I ran it twice again. Snipped out rest of log until the failure point;
Scanning for shiny gathering nodes like ‘<anything>’ *.*
I see a shiny node at (138.588104, -495.123688, -49.349411).
Going from 12 to 40 in 3 trips.
2 trips more..
1 trip more..
Destination reached!
(snip) Hitting that poor node. :3
(snip) gathering success here
Scanning for shiny gathering nodes like ‘<anything>’ *.*hangs at this point on the edge near wind current leading to weather based spawn. I’ve left it for 5 minutes and nothing happens.
A few things you can do:
1. Go to the Gathering tab in Miqo and make sure the gathering preset for this scenario is selected. Now check if Compass or Compass 2 is selected. If none of those are selected, check one of them, then click on overwrite to save the gathering preset.
2. Go to Actions & Traits > Additional and make sure none of the other jobs are selected.
3. You can also try wiping your hotbars by manually removing every skill from them, then re-add the Botanist skills to your hotbar. Take a screenshot before you do this, so you can remember where you put your skills.
- This reply was modified 4 years, 2 months ago by sternlast.
I have both on hotbar, still gets stuck at the end of first island 🙁
When you get stuck at the end of the first island, check for this line in the Miqo log:
‘I sense something far away (213, -699). I want to go take a look!’
Check your compass skills. You can only have Botanist skills for Botanist and Miner skills for Miner. If you have both sets of compass skills, Miqo will stop and do nothing at the end of the first island.
Worked perfectly, just a question. If I were to tweak it in order to account for the weather nodes, How would I go about it? Any tips?
Otherwise, thanks for the great job!
I’m not sure how I would do this. I looked at the weather functions, but they seem to be only related to fishing. Do you know of any examples of this being used for gathering in other scenarios? This would be a nice suggestion to be able to tag waypoints to specific weather conditions.
ank you so much for this! Food buff isnt working for me any ideas?
The food buff is set in Chapter 1. The first number is the hotbar number and the second number is the button number.
icon(5, 12)
I currently have the food buff set on hotbar 5, button 12, so you would need to drag your food to your hotbar and place it on that button in order for it to work. Of course, you can change those numbers to wherever you have the food buff located on your own hotbars.
- This reply was modified 4 years, 2 months ago by sternlast.
The bot almost fills all my compressed aether but not quite. It’s always 3 gathers away from doing so.
Sorry, I should have mentioned in the first post that this scenario is setup to account for the GP bonus (GP>858) that gives an additional 5 hits to the node.
The compressed aether gauge increases per hit, so the +5 hit nodes will make a big difference in how fast your compressed aether gauge fills up. You can try increasing the gather amount in Chapters 2 and 4. I originally had Chapters 2 and 4 set to 35 and 14 gathers, but sometimes it wouldn’t completely fill up the compressed aether, so I had to increase the gather number.
You can try increasing the gather() setting to a really large number, then watch Miqo until the compressed aether is completely full. Once it is completely full, check the Miqo log and look for this line ‘My precious shiny sparkles! (xxx/999)’. Take this number and add a few more to it (to be safe), then replace the gather() setting with that number.
I just have to move manually at that point but I am quite new to the game itself, I don’t see Prospect as a skill =D and I do have triangulate and arbor call II with Truth Of Forest.. I am assuming I need the first Arbor call aswell xD
Ok, you should have both Arbor Call and Arbor Call II on your hotbars. They both have different use cases depending on the situation, though in Diadem it doesn’t really matter which one you use because all of the nodes are considered equal level.
Updated Grid
added waypoint to gathering node
Attachments:
You must be logged in to view attached files.Actually I reran it, 2nd time went well but the third time it got me standing at the end of the island beside the tornado again (11:37:26 AM) Hitting that poor node. :3
(11:37:31 AM) My precious shiny sparkles! (22/38)
(11:37:31 AM) Scanning for shiny gathering nodes like ‘<anything>’ *.*What compass skill is it using when it gets stuck? It should use Arbor Call. Also check to make sure Prospect is not on your hotbar. You can’t have both skills on your hotbars at the same time while using Miqo.
This is what Arbor Call looks like in the log:
‘I sense something far away (213, -699). I want to go take a look!’
It sounds like you’re getting stuck at the end of the first island when Miqo needs to use the compass in order to find the next node. If your hotbars are messed up, it will never make it past the first island because Miqo can’t find the correct skill to use.
Ok, I found one gathering node that I missed, but I don’t think that’s the one that’s giving you trouble because it’s about 3 or 4 islands away.
- This reply was modified 4 years, 2 months ago by sternlast.
Updated Grid.
added more connecting waypoint lines to prevent dismounting at an empty node
moved a few waypoints away from the edge to prevent miqo from having to unstuck while dismounting- This reply was modified 4 years, 2 months ago by sternlast.
Attachments:
You must be logged in to view attached files.So at the end of chapter 2 I just stand still after the last node, is there a long timer on that before going to chapter 3?
It should immediately proceed to chapter 3 once it’s finished gathering from 38 nodes in chapter 2. What does your log say? It should say ‘My precious shiny sparkles! (38/38)’ before going to the next chapter.
Also, if there’s no mob at the diademBoom location, Miqo will wait for up to 3 minutes before moving on. The mob respawn timer is much shorter, so this should never happen.
diademBoom() from Miqo:
Function will select the closest enemy within a range of 50 yalms (twice the casting range). Function will automatically approach the enemy, dismount if necessary, and execute the Aetheromatic Auger. If the enemy is not detected, function will assume that it is on respawn and will wait for up to 3 minutes.An error does not break scenario flow. It will proceed normally through the script regardless of the reason it failed.
- This reply was modified 4 years, 2 months ago by sternlast.
I noticed a couple of times that Miqo got stuck waiting to find a new node to travel towards, usually at the “end” of an island close to a whirlwind with no nodes left on the island.
I haven’t encountered this issue yet. Do you know which waypoint this was occurring? Also, is Miqo using Arbor’s Call if there’s no gathering node in range? If not, then make sure that it is selected in the gathering preset. Miqo should go to the next node after using Arbor’s Call, even if it’s located on the other side of the map. The only time this wouldn’t work is when the node doesn’t have a waypoint set to it, which may be the case if I forgot to add a waypoint to the node.
Oh, make sure you only have Arbor’s Call on your hotbar. It will fail if you have both the Botanist and Miner versions on your hotbars at the same time.
The extra diademBoom’s are in case someone ninja’s the kill. Miqo can’t tell if you get credit for the kill and will simply go to the next step. I also added /dismount prior to each diademBoom to minimize the chance of this happening.
Feel free to change the waypoint numbers (or add more) if you don’t feel comfortable with the mob location.
-
AuthorPosts