[LyfoxParticipant]

Put your item on hotbar. Lets say its on hotbar 7 slot 3 and if its food you need to wait 5 seconds after.

craftMacro(YOUR_MACRO)
icon(7, 3, 5.0)
craft(30)
repeatChapter(2)

YOUR_MACRO is the name of macro in Miqo on crafting tab.

[LyfoxParticipant]

Use the second scenario in attachment named Aethersand 66+.

[LyfoxParticipant]

50-51 should take 20 minutes in Falcons Nest no need for a complex scenario. Just grab some bait from local vendor and fish with Miqo in a nearby spot.

[LyfoxParticipant]

he_le wrote:

I really don’t see how this ‘should never happen’.

Bot gathers ephemeral nodes only and touches normal ones only. Normal nodes never despawn.
Just try my ephemeral scenario it works exactly like this.

he_le wrote:

Are you understanding why the bot may get stuck given the code and environment described in the previous post?

Yep.
– On first cycle scenario will gather(1) and despawn one node in the cluster. Then gatherTouch() second node.
– On second cycle scenario will gather(1) and despawn second node in the cluster. Then gatherTouch() has nothing left to touch.

[LyfoxParticipant]

Sorry i still dont understand why youre looking for a workaround for something that should never happen instead of trying to figure out what caused it. Theres probably a mistake in timing that made your bot to gather from a normal node when ephemeral wasnt active at all. The most logical thing to do is copy the message log into a text file and read it. Find the abnormal gather sequence which navigated to incorrect waypoint not connected to an ephemeral. If you dont figure out the real problem your workaround might break anyway.

You can show your scenario and log if you want and ill help you look for that problem.

[LyfoxParticipant]

Umm not really, if you gather(1) it will despawn it. And nodes are always randomized within each cluster.

There are usually three clusters with 4 nodes in each. Only 2 of 4 are spawned and those 2 will be different after relog. So if you put waypoints 1,2,3 above three clusters you have to make sure that all 12 nodes are linked to them. Like 4,5,6,7 for the first cluster then 8,9,10,11 for second and so on. Use 3d radar to link both spawned (green) and non-spawned (white).

Sorry if its the same as you asked i wasnt sure.

[LyfoxParticipant]

Gather preset contains rotation and grid both. Seems like you saved the same grid into each of your presets thats why it happens. So just select preset, select correct grid, click overwrite. Or simply swap functions in your scenario.

selectGatherPreset(wind crystal)
grid(abanian alumen)

To repair use repair() or repairNpc().

[LyfoxParticipant]

Hmm why exactly did cluster at waypoint 3 despawn? Did you gather it before? If you do only gatherTouch() it should not despawn on its own. You can relog to reset clusters if theyre messed up.

[LyfoxParticipant]

This is a scenario generator not a crafting rotation. But yea it uses crafting solver so if you setup it properly its always HQ.

[LyfoxParticipant]

What do you mean? Miqo never used compass for gatherTouch() she needs a node to be visible. It was always like that. What version do you use?

[LyfoxParticipant]

Its unlikely to be suspended for simple afking. People like me have auto afk icon disabled so it never comes up. Somebody can only report you for botting not for afking. And even then there has to be proof like running 24 hours non stop. Do you leave it running for the night?

[LyfoxParticipant]

If you still need help show the message log. I love helping but without knowing what Miqo says theres nothing i can do.

[LyfoxParticipant]

Use gather by name for hidden mats: https://miqobot.com/forum/forums/topic/help-gathering/#gather-by-name

mandrake seeds
shard

[LyfoxParticipant]

Ah ive seen this in a nearby thread. Is your camera reversed? Miqo doesnt support reversed camera yet.
System > Character Configuration > Camera Controls > 3rd Person Camera > Reversed Y/X-axis.

[LyfoxParticipant]

Its not all of it its only the last 8 lines. Something triggered a kill switch before and it was in the message log above these lines. You can scroll it up.

[Author]

Posts