Infinite Universal Diadem Scenario BotanistšŸŒ±, Miningāš’, and FishingšŸŽ£

Forum Forums Grids and Presets Infinite Universal Diadem Scenario BotanistšŸŒ±, Miningāš’, and FishingšŸŽ£

This topic contains 932 replies, has 245 voices, and was last updated by  daktrgonzo 2 weeks, 1 day ago.

Viewing 15 posts - 901 through 915 (of 933 total)
  • Author
    Posts
  • #40436
    Lyfox
    Lyfox
    Participant
    1+

    does anyone have a scenario/gathering preset for artisanal materials? updating my miqo wiped the one iā€™d been using šŸ™

    Check your backups: https://miqobot.com/forum/forums/topic/help-general/#backups

    #40445

    grandcypher
    Participant
    0

    oh damn, a lifesaver! thank you.

    one other thing that she seems to be doing now that she didn’t last time i used her, the targeting nearest object/npc. traditionally she’d just run up to a node and target it, but now she’s doing the lock on onto nodes and running to them and this seems to get her stuck in certain places. it’s a bigger issue in island sanctuary where i can’t seem to use any of the scenarios because she locks on to animals and can’t do anything, but appears to also cause hiccups in the diadem now.

    #40446
    Lyfox
    Lyfox
    Participant
    0

    Thats a game setting that youve turned on somewhere. Im not sure which one unfortunately. But try to look for something with ‘auto lock’ in the description and see if disabling it helps.

    #40561

    Ineeditexists
    Participant
    2+

    Issue to report with the scenario

    Pathing from waypoint node 276 to waypoint 121 gets the character stuck, causing miqobot to reliably crash.

    Steps to reproduce:
    1. set up miqobot under the “Mining with collectable turn ins” setting
    2. wait between 30mins and 2 hours, depending on what waypoint the scenario randomly decides upon in chapter 5

    Miqobot console log:

    
    ...
    
    (1:34:44 AM) 1 trip more..
    (1:34:49 AM) Destination reached!
    (1:34:51 AM) Hitting that poor node. :3
    (1:34:59 AM) Hitting that poor node. :3
    (1:35:06 AM) My precious shiny sparkles! (19/40)
    (1:35:06 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:35:06 AM) I see a shiny node at (-17.308760, -542.249878, -26.511299).
    (1:35:07 AM) Going from 134 to 136 in 2 trips.
    (1:35:12 AM) 2 trips more..
    (1:35:16 AM) 1 trip more..
    (1:35:18 AM) Destination reached!
    (1:35:20 AM) Hitting that poor node. :3
    (1:35:29 AM) Hitting that poor node. :3
    (1:35:35 AM) My precious shiny sparkles! (20/40)
    (1:35:35 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:35:35 AM) I see a shiny node at (74.268692, -504.542297, -46.791981).
    (1:35:37 AM) Going from 136 to 131 in 3 trips.
    (1:35:39 AM) 3 trips more..
    (1:35:44 AM) 2 trips more..
    (1:35:47 AM) 1 trip more..
    (1:35:50 AM) Destination reached!
    (1:35:52 AM) Hitting that poor node. :3
    (1:36:01 AM) Hitting that poor node. :3
    (1:36:06 AM) My precious shiny sparkles! (21/40)
    (1:36:06 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:36:06 AM) I see a shiny node at (109.910599, -500.400604, -47.776291).
    (1:36:07 AM) Going from 131 to 276 in 3 trips.
    (1:36:11 AM) 3 trips more..
    (1:36:13 AM) 2 trips more..
    (1:36:16 AM) 1 trip more..
    (1:36:20 AM) Destination reached!
    (1:36:22 AM) Hitting that poor node. :3
    (1:36:30 AM) Hitting that poor node. :3
    (1:36:37 AM) My precious shiny sparkles! (22/40)
    (1:36:37 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:36:38 AM) I sense something far away (220, -722). I want to go take a look!
    (1:36:40 AM) Going from 276 to 121 in 6 trips.
    (1:36:45 AM) 6 trips more..
    (1:36:49 AM) 5 trips more..
    (1:37:25 AM) 4 trips more..
    (1:37:31 AM) 3 trips more..
    (1:37:36 AM) 2 trips more..
    (1:38:16 AM) Oh noes, I couldn't reach the destination in time. I guess I'm stuck here. :(
    (1:38:16 AM) Time/Estimate: 39.9280/39.9031
    (1:38:16 AM) 1 trip more..
    (1:38:16 AM) Sorry, can't move. I got lost in the woods, and I can't find way back home.
    (1:38:16 AM) Destination reached!
    (1:38:16 AM) Sorry, can't move. I got lost in the woods, and I can't find way back home.
    (1:38:16 AM) Poking creatures in the woods... Good night! <3
    (1:38:16 AM) 	(NOTE) Kill switch is triggered.
    (1:38:16 AM) 	(NOTE) Please save the message log for analysis and restart Miqobot.
    

    Log has been truncated for readability.
    The bot will get stuck on the rock at map coords (25.8, 7.4) as it paths over to the nearest mining node, coming from the Southwest.

    #40608

    RavenCereal
    Participant
    0

    Found a great spot for using bazooka charges:

    boomTarget(Werewood)
    boomTarget(Bulb)
    boomTarget(Icetrap)
    
    waypoint(31)
    diademBoom()
    diademBoom()
    diademBoom()
    diademBoom()
    diademBoom()

    Hits 5 targets in a row with minimal issues. All plant-based BTN stuff if you care about what you’re getting, but personally I only plan on keeping this part in until I get my 1000 bazooka use achievement, then I’ll take it out anyway.

    #40744

    finalspacy1
    Participant
    0

    hi, im trying to use this scenario but the bot seem to does not use mount to fly over. How can i make the bot to use mount to fly?

    Chapter: 2
    Tread carefully now.
    Adventure calls! I have to travel far away. (Grid: 'The Diadem āš’šŸŒ±', Waypoint: 442)
    Sorry, can't find path sequence from 569 to 442 :( Maybe grid is not connected?
    Sorry, but I can't find the way to the next trip :(
    Woah! A 979 seconds trip? I don't think I can manage that. Let's try 300 second
    • This reply was modified 7 months, 2 weeks ago by  finalspacy1.
    #40746
    sageomithas
    sageomithas
    Participant
    0

    do you have a mount on your hotbar and have it with a keybind? I had this problem when I didn’t have the hotbar mapped to keybinds.

    #40823

    gugugu27
    Participant
    0

    Honestly same here, maybe a game update messed it up or something.
    (12:03:27) (SCENARIO) Chapter 1 complete.
    (12:03:27) Tread carefully now.
    (12:03:30) Adventure calls! I have to travel far away. (Grid: ‘The Diadem āš’šŸŒ±’, Waypoint: 442)
    (12:03:32) Sorry, can’t find path sequence from 193 to 442 šŸ™ Maybe grid is not connected?
    (12:03:32) Sorry, but I can’t find the way to the next trip šŸ™
    (12:03:32) Woah! A 947 seconds trip? I don’t think I can manage that. Let’s try 300 seconds first, okay? :3
    (12:03:42) (SCENARIO) Stopping…
    (12:03:42) Adventure cancelled… Yet, I’m still full of energy!
    (12:03:42) Final distance to target: 729.37

    #40824

    milqueteeth
    Participant
    0

    You should be in the Firmament when you start Chapter 2 of the scenario, not the Diadem. It sends you over to talk to Aurvael. If you’re already in the Diadem, make sure to start at Chapter 4 or later. And if you’re in the Firmament and it’s still giving you that error, try deleting the scenario and re-importing it. I had a weird error issue and that solved it for me.

    #40848
    Qwertybbop
    Qwertybbop
    Participant
    0

    Is there a grid for the northern island loops to grind the 500k points effectively for min/btn? I havent used miqo in forever so no clue how to set up something like that myself

    #40849

    HimeTan
    Participant
    0

    I don’t know if these things were brought up before – or at least, recently, but here are the issues I faced and was able to resolve.

    1. Getting stuck at nodes with no other nodes on the minimap
    Cause: Under Gathering, “Use Compass” was unchecked.
    Solution: fight the Gathering setting.

    2. Auger sequence not working correctly due to weird movements and lock-ons.
    Cause: I had a macro on my hotbar for Island Sanctuary that used the Duty Action I icon. The bot used that one instead of the actual Duty Action.
    Solution: Remove macro from hotbar or change icon. Place Duty Action I on hotbar.

    3. Dialogs not being clicked correctly
    Cause: YesPlease plugin defaulting prompts to the ‘yes’ option. NUM4 and NUM8 presses unnecessary, causing unexpected behavior.
    Solution: Remove NUM4 and NUM8 clicks from chapters. Basically spam NUM0 to get into the Diadem.
    Or just disable YesPlease while you’re in purgatory the Diadem

    Thank you for this scenario. Now I can do other stuff while getting prog on those achievs ā™„

    • This reply was modified 5 months, 1 week ago by  HimeTan.
    #40852
    Mellismera
    Mellismera
    Participant
    0

    Hi all! I have a couple of questions – for example, can I remove the part from the script regarding the repair and delivery of collectables? I don’t aim to leave the cycle for more than three hours.

    and how to properly configure the resources that I want to collect? Is it enough to include them in the Grid? That’s all? Or are there some nuances?
    Iā€™ve only been getting used to it here for a few days and there are still some things I donā€™t understand)

    #40856

    HimeTan
    Participant
    1+

    Hi all! I have a couple of questions ā€“ for example, can I remove the part from the script regarding the repair and delivery of collectables? I donā€™t aim to leave the cycle for more than three hours.

    I did and the script is working just fine, other than the known issue with the level 80 nodes for MIN.

    #40918

    LitaPlush
    Participant
    0

    i can confirm i have the whole same thing happening to me.

    #40919

    LitaPlush
    Participant
    0

    Issue to report with the scenario

    Pathing from waypoint node 276 to waypoint 121 gets the character stuck, causing miqobot to reliably crash.

    Steps to reproduce:
    1. set up miqobot under the ā€œMining with collectable turn insā€ setting
    2. wait between 30mins and 2 hours, depending on what waypoint the scenario randomly decides upon in chapter 5

    Miqobot console log:

    
    ...
    
    (1:34:44 AM) 1 trip more..
    (1:34:49 AM) Destination reached!
    (1:34:51 AM) Hitting that poor node. :3
    (1:34:59 AM) Hitting that poor node. :3
    (1:35:06 AM) My precious shiny sparkles! (19/40)
    (1:35:06 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:35:06 AM) I see a shiny node at (-17.308760, -542.249878, -26.511299).
    (1:35:07 AM) Going from 134 to 136 in 2 trips.
    (1:35:12 AM) 2 trips more..
    (1:35:16 AM) 1 trip more..
    (1:35:18 AM) Destination reached!
    (1:35:20 AM) Hitting that poor node. :3
    (1:35:29 AM) Hitting that poor node. :3
    (1:35:35 AM) My precious shiny sparkles! (20/40)
    (1:35:35 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:35:35 AM) I see a shiny node at (74.268692, -504.542297, -46.791981).
    (1:35:37 AM) Going from 136 to 131 in 3 trips.
    (1:35:39 AM) 3 trips more..
    (1:35:44 AM) 2 trips more..
    (1:35:47 AM) 1 trip more..
    (1:35:50 AM) Destination reached!
    (1:35:52 AM) Hitting that poor node. :3
    (1:36:01 AM) Hitting that poor node. :3
    (1:36:06 AM) My precious shiny sparkles! (21/40)
    (1:36:06 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:36:06 AM) I see a shiny node at (109.910599, -500.400604, -47.776291).
    (1:36:07 AM) Going from 131 to 276 in 3 trips.
    (1:36:11 AM) 3 trips more..
    (1:36:13 AM) 2 trips more..
    (1:36:16 AM) 1 trip more..
    (1:36:20 AM) Destination reached!
    (1:36:22 AM) Hitting that poor node. :3
    (1:36:30 AM) Hitting that poor node. :3
    (1:36:37 AM) My precious shiny sparkles! (22/40)
    (1:36:37 AM) Scanning for shiny gathering nodes like '<anything>' *.*
    (1:36:38 AM) I sense something far away (220, -722). I want to go take a look!
    (1:36:40 AM) Going from 276 to 121 in 6 trips.
    (1:36:45 AM) 6 trips more..
    (1:36:49 AM) 5 trips more..
    (1:37:25 AM) 4 trips more..
    (1:37:31 AM) 3 trips more..
    (1:37:36 AM) 2 trips more..
    (1:38:16 AM) Oh noes, I couldn't reach the destination in time. I guess I'm stuck here. :(
    (1:38:16 AM) Time/Estimate: 39.9280/39.9031
    (1:38:16 AM) 1 trip more..
    (1:38:16 AM) Sorry, can't move. I got lost in the woods, and I can't find way back home.
    (1:38:16 AM) Destination reached!
    (1:38:16 AM) Sorry, can't move. I got lost in the woods, and I can't find way back home.
    (1:38:16 AM) Poking creatures in the woods... Good night! <3
    (1:38:16 AM) 	(NOTE) Kill switch is triggered.
    (1:38:16 AM) 	(NOTE) Please save the message log for analysis and restart Miqobot.
    

    Log has been truncated for readability.
    The bot will get stuck on the rock at map coords (25.8, 7.4) as it paths over to the nearest mining node, coming from the Southwest.

    i can confirm this is a problem, i keep having the same happening to me to at this exact location.

Viewing 15 posts - 901 through 915 (of 933 total)

You must be logged in to reply to this topic.