[okayParticipant]

r51093 wrote:

SLYG wrote:

Didn’t mean it with any ill will

no no your all good constructive criticism is always welcome but sugestions and ideas are always more welcome 😀

SLYG wrote:

Like mounting up to fly away from a node, only to fly right back to it. Or mounting up to ride to a node that is only a couple feet away.

Actually i have it mount up for the nodes intentionally it is stupid i agree however theres a bug in final fantasy were the game dose not properly close out the gathering window it happens frequently (the bug prevents you from being able to open the gatheirng window at the next node) but SE dont seam to care about it as it can be fixed easily by mounting up or preforming another action other then gathering, with out the mounting up in-between nodes you run the risk of your toon running 🏃 back and forth between the waypoint and the node none-stop 🛑

SLYG wrote:

It also manually flies between the islands rather than using the wind currents, and that seems awkward too.

this is also intended XD the vortexes actually tend to screw with miqobot the only way to ensure that the toon runs into the vortex is to palce a waypoint right in the middle of said vortex ( thats hard to do with out notepad++ to manually adjust the X,Y,Z cords of the waypoint ) and going from a higher island 🏝 to a lower one is easy going from a lower island 🏝 to a higher one is not as your toon will tigger the vortext but often wont get close enough to trigger miqobot that you passed it and this will cause miqobot to fly back down to said waypoint where you will get stuck in that loop untill miqobot kill switches and you get kicked for being AFK and several other similar issues arise from trying to use the vortexes ( the grid was originallymade to use them then i quickly found out it’s way to buggy to use them ) besides that i talked with the community and i as well as alot of people rarely use the vortexes as its often times faster to fly right to the next node then to use them especially if said node is two island’s 🏝 over the vortexes are only really in the diadem for people who have not yet unlocked flying ✈

thies issue’s have been discussed in length with the community in previous post and while they are not the most ideal thies are the best solution’s we have to thies issue’s

Ah okay I see, apologies then.

[okayParticipant]

r51093 wrote:

bluefantasi wrote:

Hey I just downloaded this preset and for some reason when I start the scenario but for some reason everything works but my character isn’t going to the NPC to enter into diadem.

I checked through the saved presets and only removed NPC repair and MIN turn ins for the botanist only scenario. I didn’t touch any of the presets for chapter 1, unless I’m missing something @_@

dose miqobot give any error’s in the log?

SLYG wrote:

A lot of this grid looks very unnatural. Movements are super bot like, a lot of redundant movement, and pretty noticeable. I’d be careful using it for extended periods of time. Otherwise pretty good.

im sorry you feel that way 😿 . This is the first complaint i have heard about it being bot 🤖 like unfortunately i dont know how i could possibly make it look less like a bot 🤖 but if you have sugestions im all ear’s 👂 😀

Didn’t mean it with any ill will, but there’s a handful of places on the grid it takes really awkward looking movements. Like mounting up to fly away from a node, only to fly right back to it. Or mounting up to ride to a node that is only a couple feet away. It also manually flies between the islands rather than using the wind currents, and that seems awkward too.

But aside from that it’s fine, I didn’t mean to sound pretentious or anything. Above all else it at least doesn’t get stuck somewhere in a tree and just spazz out.

• This reply was modified 3 years, 9 months ago by  okay.

[okayParticipant]

A lot of this grid looks very unnatural. Movements are super bot like, a lot of redundant movement, and pretty noticeable. I’d be careful using it for extended periods of time. Otherwise pretty good.

[okayParticipant]

okay wrote:

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 own

Attachments:

You must be logged in to view attached files.

[okayParticipant]

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.

• This reply was modified 4 years, 2 months ago by  okay.

[Author]

Posts