[r51093Participant]

edgedy wrote:

With the upcoming start crunch in the future unsynced content is going to be even harder.

what do you mean even harder?

[r51093Participant]

Ver.4
Now have a working squadron scenario for The Twin Adder’s 🐍🐍 latest update can be found here on the original post

Maelstrom 🏴‍☠️⛴, Immortal Flames ♾️🔥, & The Twin Adder's 🐍🐍 Squad/Trust GC

[r51093Participant]

also sorry for the delay havent been able to be on much as i have been having power issues with the ice ❄ / snow 🌨 building up on the power line’s

grith511 wrote:

SO, no matter what i do it wont gather anything but slot 3. Every time i change the number it go’s back after 1 node. what am i doing wrong

SirVG wrote:

Miqobot gives priority to items in the gather by name list over the slot number. If you wish to gather by slot instead, you will need to delete all entries in the gather by name list.

Also don’t for get to click that “Overwrite” button and click save on the pop up window as well to save the changes ( you have to click it for both presets Mining ⚒ and Botanist 🌱 )

Attachments:

You must be logged in to view attached files.

[r51093Participant]

burton wrote:

I cannot seem to bypass the Oddly Jade nodes even with Lyfox fix

honestly i dont know what to do about the oddly jade nodes not even sure if there even is a fix for them

[r51093Participant]

just please keep in mind that the send key function is unreliable and may not always work but this is the best method that miqobot has to offer as of right now

r51093 wrote:

the send key function which is unreliable

[r51093Participant]

ps34pc wrote:

Is there a way at the end instead of having it afk have it actually exit the game?

yes there is but it uses the send key function which is unreliable but there is an auto logg off sequence in the last chapter of every scenario you have to manually enable it by removeing the // from the code in the scenario its all explained in the final chapter also you need to make a macro with the following command /shutdown and place it on hot bar 4 slot 1 this is vital to the shutdown sequence

[r51093Participant]

vivre wrote:

Thanks! I also realised that I didn’t have keybind Num0 set up on Confirm so that’s was the problem for me too. Everything’s working fine now

glad to hear it 😀

[r51093Participant]

kdumbledore wrote:

Oooh I finally ran into the rock thingy again!!!! I have no idea how to get the z coordinate from miqo (I know the x,y from in game though)..

I’m at x26.7 y24.9 and it’s when you go to waypoint 526 (I’m hoping knowing the exact waypoint will help you find the z coordinate lol). If it helps any I’m on the 9th section of the scenario.

Trying to attack and boom a Diadem Ice Golem that is behind a giant rock. I’m going to add the // in front of the ice golem’s for now and hope that helps, but if you ever fix the waypoints here’s the info hehe! And below is what I stole from miqo right before I stopped the scenario once I noticed it freaking out over that rock.

(9:23:02 AM) Adventure calls! I have to travel far away. (Grid: ‘The Diadem ⚒🌱’, Waypoint: 526)
(9:23:03 AM) Going from 50 to 526 in 7 trips.
(9:23:07 AM) 6 trips more..
(9:23:09 AM) 5 trips more..
(9:23:13 AM) 4 trips more..
(9:23:17 AM) 3 trips more..
(9:23:33 AM) 2 trips more..
(9:23:38 AM) 1 trip more..
(9:23:38 AM) Destination reached!
(9:23:41 AM) Boom this: ‘Diadem Ice Golem’
(9:23:42 AM) Diadem Boom!
(9:23:44 AM) Diadem target eliminated.
(9:23:45 AM) Boom this: ‘Diadem Ice Golem’
(9:23:49 AM) Diadem Boom!
(9:23:51 AM) Diadem target eliminated.
(9:23:52 AM) Boom this: ‘Diadem Ice Golem’
(9:24:14 AM) (SCENARIO) Stopping…

vivre wrote:

Hi! It’s my first try at using miqo and I’m getting error for some reason

ERROR (Chapter 3, Line 13): Syntax error. Expected format: function(arguments)

Please help, what should I do? I’ve deleted previous Diadem presets
ALso it seems like the problem is that char can’t access diadem with this chapter. If I enter it myself and start at step 4 it works fine. Can you please give me an example how step 3 should look so I can fix it maybe?

just droped the update with both fix’s it can be found here in the Original post

Infinite Universal Diadem Scenario Botanist 🌱 and Mining ⚒

[r51093Participant]

vivre wrote:

Hi! It’s my first try at using miqo and I’m getting error for some reason

ERROR (Chapter 3, Line 13): Syntax error. Expected format: function(arguments)

Please help, what should I do? I’ve deleted previous Diadem presets
ALso it seems like the problem is that char can’t access diadem with this chapter. If I enter it myself and start at step 4 it works fine. Can you please give me an example how step 3 should look so I can fix it maybe?

this was my screw-up sorry theres text that should not be there copy and paste the below text into chapter 3 i will fix this in the next ver update that i wll post as soon as i adjust the waypoint for the above issue

job(miner)
job(botanist)
job(miner)
key(num0, 1)
key(num0, 1)
key(num0, 1)
key(num0, 1)
key(num4, 1)
key(num0, 2)
key(num8, 1)
key(num4, 1)
key(num0, 1)

afkFor(00:00:10)

[r51093Participant]

kdumbledore wrote:

Oooh I finally ran into the rock thingy again!!!! I have no idea how to get the z coordinate from miqo (I know the x,y from in game though)..

I’m at x26.7 y24.9 and it’s when you go to waypoint 526 (I’m hoping knowing the exact waypoint will help you find the z coordinate lol). If it helps any I’m on the 9th section of the scenario.

Trying to attack and boom a Diadem Ice Golem that is behind a giant rock. I’m going to add the // in front of the ice golem’s for now and hope that helps, but if you ever fix the waypoints here’s the info hehe! And below is what I stole from miqo right before I stopped the scenario once I noticed it freaking out over that rock.

(9:23:02 AM) Adventure calls! I have to travel far away. (Grid: ‘The Diadem ⚒🌱’, Waypoint: 526)
(9:23:03 AM) Going from 50 to 526 in 7 trips.
(9:23:07 AM) 6 trips more..
(9:23:09 AM) 5 trips more..
(9:23:13 AM) 4 trips more..
(9:23:17 AM) 3 trips more..
(9:23:33 AM) 2 trips more..
(9:23:38 AM) 1 trip more..
(9:23:38 AM) Destination reached!
(9:23:41 AM) Boom this: ‘Diadem Ice Golem’
(9:23:42 AM) Diadem Boom!
(9:23:44 AM) Diadem target eliminated.
(9:23:45 AM) Boom this: ‘Diadem Ice Golem’
(9:23:49 AM) Diadem Boom!
(9:23:51 AM) Diadem target eliminated.
(9:23:52 AM) Boom this: ‘Diadem Ice Golem’
(9:24:14 AM) (SCENARIO) Stopping…

thank you i will work on this and yes i know were all most of the cord’s are thank you for that for future reference you can find Miqobots XYZ cords in the monitor tab of miqobot like shown below thies are way more detailed then the ingame ones and can literally take me to the exact location lol

Attachments:

You must be logged in to view attached files.

[r51093Participant]

djangomouse wrote:

This works really great, by the way. Thanks for your hard work!

thank you glad for the feedback 😀 everyone here in the comunity helped to make the grid / scenario what it is especially with the bug testing lol 😆

[r51093Participant]

hello, and sorry guys for my absence 😀

vega wrote:

Did lyfox workaround resolve the issue with the oddly delicate nodes?

hello yes it dose work very nicely in fact i did change it to randome waypoints through becuse SE might get suspiciousog a bunch of gathers going to the some location 😂 this fix is only needed if you have issues with the oddly specific jade
the fix is below
replace gather(40) in chapters 5, 8, 11, and 14 with the below text

gather(18)
randomWaypoint(578,282,24,184,284)
gather(22)

Falbium wrote:

I got this error
(8:43:52 AM) Going from 487 to 526 in 9 trips.
(8:43:56 AM) 9 trips more..
(8:43:57 AM) 8 trips more..
(8:43:59 AM) 7 trips more..
(8:44:01 AM) 6 trips more..
(8:44:02 AM) 5 trips more..
(8:44:04 AM) 4 trips more..
(8:44:06 AM) 3 trips more..
(8:44:40 AM) 2 trips more..
(8:44:46 AM) 1 trip more..
(8:44:46 AM) Destination reached!
(8:44:48 AM) Boom this: ‘Diadem Ice Golem’
(8:44:49 AM) Diadem Boom!
(8:44:52 AM) Diadem target eliminated.
(8:44:52 AM) Boom this: ‘Diadem Ice Golem’
(8:44:56 AM) Diadem Boom!
(8:44:59 AM) Diadem target eliminated.
(8:44:59 AM) Boom this: ‘Diadem Ice Golem’
(8:46:21 AM) Oh noes, I couldn’t reach the destination in time. I guess I’m stuck here. 🙁
(8:46:21 AM) Time/Estimate: 36.1272/36.1231
(8:46:21 AM) Poking creatures in the woods… Good night! <3
(8:46:21 AM) (NOTE) Kill switch is triggered.
(8:46:21 AM) (NOTE) Please save the message log for analysis and restart Miqobot.

kdumbledore wrote:

Heeey, I had the same error! Here’s mine haha

(9:46:38 AM) My precious shiny sparkles! (40/40)
(9:46:38 AM) Woot-woot!
(9:46:38 AM) I got loads of sparkles in my pockets!
(9:46:38 AM) Guess it’s time to rest for a bit 🙂
(9:46:38 AM) Everything is gathered!
(9:46:38 AM) (SCENARIO) Chapter 11 complete.
(9:46:39 AM) Added target for diademBoom(): ‘Golem’
(9:46:39 AM) Added target for diademBoom(): ‘Zoblyn’
(9:46:39 AM) Added target for diademBoom(): ‘Ice Golem’
(9:46:39 AM) Added target for diademBoom(): ‘Biast’
(9:46:39 AM) Added target for diademBoom(): ‘Ice Bomb’
(9:46:40 AM) Added target for diademBoom(): ‘Diadem’
(9:46:44 AM) Adventure calls! I have to travel far away. (Grid: ‘The Diadem ⚒🌱’, Waypoint: 504)
(9:46:46 AM) Going from 74 to 504 in 9 trips.
(9:46:49 AM) 9 trips more..
(9:46:51 AM) 8 trips more..
(9:46:56 AM) 7 trips more..
(9:46:57 AM) 6 trips more..
(9:46:59 AM) 5 trips more..
(9:47:01 AM) 4 trips more..
(9:47:22 AM) 3 trips more..
(9:47:27 AM) 2 trips more..
(9:47:34 AM) 1 trip more..
(9:47:34 AM) Destination reached!
(9:47:36 AM) Boom this: ‘Diadem Ice Bomb’
(9:47:37 AM) Diadem Boom!
(9:47:40 AM) Diadem target eliminated.
(9:47:40 AM) Boom this: ‘Diadem Ice Bomb’
(9:47:43 AM) Diadem Boom!
(9:47:46 AM) Diadem target eliminated.
(9:47:46 AM) Boom this: ‘Diadem Bloated Bulb’
(9:49:08 AM) Oh noes, I couldn’t reach the destination in time. I guess I’m stuck here. 🙁
(9:49:08 AM) Time/Estimate: 81.2184/81.1918
(9:49:08 AM) Poking creatures in the woods… Good night! <3
(9:49:08 AM) (NOTE) Kill switch is triggered.
(9:49:08 AM) (NOTE) Please save the message log for analysis and restart Miqobot.

• 
  

  r51093 wrote:

  Note: it is recommended to place // before any boomTarget(Monster Name) you dont want the augur to target

thies are miqobot targeting mobs behind walls and such i will adjust he waypoints to try and prevent this but best bet is to put //before the boomTarget(monster name here) you dont want to farm like this //boomTarget(monster name here) this will help prevent miqobot from trying to targeting mobs ontop of cliffs and the like

[r51093Participant]

Lyfox wrote:

r51093 wrote:

though dose is mess up with the timer though? with the extra time spent running back to that specific waypoint? i know when he scnario is over there is genrally about 60 min left on the timmer not sure how much time this will subtract from it if any i have done any testing yet

It shouldnt spend any time at all. The point is to tell Miqo to go to the upper island instead of letting her hit compass. Before the appearance of Oddly Jade she would go there herself. Now you count the exact amount of nodes she farms on the first island and tell her where to go directly. gather(18) was a number for my own Diadem scenario. Im not sure how many nodes she collects on the first island in yours since we have different grids but you can simply run it and count them.

With scenarios you can do many flexible things. You can actually do precise navigation through a single chain of nodes like this.

waypoint(333)
gather(1)
waypoint(350)
gather(1)
waypoint(377)
gather(1)

This is actually the most efficient way to farm Diadem. And there are also beacons in Miqo which allow gathering to work without compass at all. There are many ways to solve this. My point is the tools are already there its up to you how to use them.

r51093 wrote:

here is the scenario in question

Ok im looking at it now.

r51093 wrote:

below is the entire scenario in question again waypoint(18) not even listed as a destination

Yea i see theres no waypoint(18).

r51093 wrote:

(11:49:07 AM) WORK time is over! Let’s go to another chapter ^_^

Yea what FouGilang said. This line means workFor() or workUntil() was used. And this is the reason it skipped through chapter 2. Yet i dont see them in this scenario. Are you sure this is the one that was running?

r51093 wrote:

your right im just fustraded sorry

It looks like youre tired mate. I see you making tons of scenarios and sharing them on forums. Have you taken a break lately?

im fairly certain that was the one i was running but its posible i accidently ran a diffrent one 😕

Andylynyn wrote:

To pick up on the person above me:

We all appreciate the work you put into these, but we’ll all still be here waiting for new stuff.

Take a break if you want/need to, my guy.

thanks 😀 and sorry its been abit stressful lately ( IRL stuff going on ) but from now on things should be calming down ( well for the time being lol things just tend to happen all at one time )

[r51093Participant]

r51093 wrote:

Lyfox wrote:

Isnt that fixable with a few scenario lines? Instead of gather(40) you can do something like

gather(18)
waypoint(578)
gather(22)

So instead of relying on Lay of the Land you tell her to go straight to the upper island. Seems like an easy fix.

thank you i will have to look into this

i am testing this now need to make sure that with the time added for travel that there is still sufficient time for Miqobot to finish the scenario and not be forced out of the diadem becuse of the timer

[r51093Participant]

Lyfox wrote:

r51093 wrote:

even the diadem is broken becuse of the oddly specific jade that can be farmed in there now the game is picking up them waypoints as closer then the other nodes and farming them non stop

Did you read my fix in your thread? Ive applied it in my Miqo and its been running flawlessly ever since.

r51093 wrote:

below is the entire scenario in question again waypoint(18) not even listed as a destination

Could you export your scenario as it is right now? Ill take a look.

r51093 wrote:

MIQOBOT is in need of an overhaul becuse something is really wrong with it

Not sure if its constructive enough. We should do a proper bug report otherwise theres nothing to work with. Like the one i did for your grid rename crash.

here is the scenario in question, the scenario is only the latest issue the waypoints are way off to the point where sometimes is errors out becuse it’s not close enough to the deliverGCGear() NPC even though i have it as close as i possibly can to the NPC! and miqobot somehow running into the vortexes (in the diadem) again

Lyfox wrote:

Not sure if its constructive enough. We should do a proper bug report otherwise theres nothing to work with. Like the one i did for your grid rename crash.

your right im just fustraded sorry

Lyfox wrote:

Did you read my fix in your thread? Ive applied it in my Miqo and its been running flawlessly ever since.

i did just recently i havent had time to apply it yet i will soon though dose is mess up with the timer though? with the extra time spent running back to that specific waypoint? i know when he scnario is over there is genrally about 60 min left on the timmer not sure how much time this will subtract from it if any i have done any testing yet

Attachments:

You must be logged in to view attached files.

[Author]

Posts