[NekroParticipant]

acrazycyclist wrote:

if I’m lucky it downs the 1st boss in Holminster.

I had this problem once too, but that was just because I disabled my keybinds for strafe left/right. So I guessed that either those were disabled or maybe another action which has the same keybind in combination with maybe an ALT or SHIFT collides with the movement.

acrazycyclist wrote:

as I mentioned I’ve leveled stuff across a couple of accounts and this just started to be an issue recently

I think ffxiv saves configuration based on character, so I guessed there maybe was a conflict in your keybinds, which didn’t lead to problems until now.

If thats not the case, maybe it has to do with your class. I can think of that miqo might want to use some dash-related combat actions on your RDM which she doesn’t have access to, or the auto-target mob is turned off, but she still wants to do that, to reach the safe zone on the first boss.

I can’t think of anything else, which would result in your current problem. I ran holminster 2 times (with warrior) with the newest version (1.3.41) and I didn’t encounter this behaviour.

Probably need to wait for an answer from Miqo then.

[NekroParticipant]

acrazycyclist wrote:

Miqo will have my character stand in AOE’s and instead of moving out of the way it will jump or just stand still.

First thing, which will come to mind is that you don’t have all keybinds set for movement (especially look for strafe left and right I think), a conflict and/or not using the legacy movement type.

Might want to look up here for some general tips in that regard:
https://miqobot.com/forum/forums/topic/help-keybinds/

Or the quick setup, might have overseen some movement related stuff.
https://miqobot.com/#faq

[NekroParticipant]

Could you elaborate on what you were doing with miqo, when this error appeared?

By any chance: Did you try to use the crafting solver on the new expert recipes for ishgard? That is known to be a potential crash at the moment, til they updated the bot for it to work properly.

[NekroParticipant]

ExtraNatio wrote:

This thread was created to elicit an update from the Miqobot team on an important and time sensitive feature. I asked because nobody else seemed to be willing to do so, and the Miqobot team hadn’t volunteered updates on the progression of this feature update.

Thats totally fine and they answered aswell.

ExtraNatio wrote:

I will not be bullied by the Miqobot team, their simps or their apologists, for asking a question that is important to the community.

I actually didn’t read what seems to have been a wave of more aggressive posts (which are now removed), however I don’t see anything you describe currently in the thread here. Maybe before, but I don’t see anyone bullying. Only that the Thread slightly deviated to the topic, that it is questioned if there actually is more complexity and for this and just this topic I threw in my opinion aswell.

ExtraNatio wrote:

All I asked for was an update on the implementation of a feature, with reference to the developer’s own timeframe and game-relevant circumstances. Instead, the “development team” threw a tantrum, initiated a pity party, and branded me and others – the paying consumers of their product – as the problem for “expecting features to be available on day one”. Nobody said that and nobody seriously expects that. The inference that I draw from the Miqobot team’s responses is a disdain for their own paying customers. They throw thinly veiled insults at consumers because of their failings of reading comprehension and contextual interpretation. The behaviour expected from petulant children, really.

I mean, I actually don’t see that at all here, posts from you or referencing to you are just on the first page. As I said, I don’t see the removed posts, but as I can see it from the Thread right now, your question was answered and then you never got mentioned or “attacked” afterwards. Correct me if I am wrong here.
Edit: Yes the info “Please don’t expect new features on day one” is mentioned, however I don’t see this as an attack or implication that you said so, just a reminder in case you didn’t know.

• This reply was modified 3 years, 11 months ago by  Nekro.

[NekroParticipant]

I don’t know the exact details of the crafting solver process. But I think it was behaving like an AI, preprocessing the steps with your current stats and determining the best path to take, in order to put you in the best possible spot for the craft for the next step.
Determining what the “best possible” spot is, is probably the hardest part here.
Before, we had mostly reactive conditions, where if you get a condition you can make a decision on the fly, allowing to go for the general “health” of the craft, being durability, progress almost on max (one synth to finish), keeping CP high, etc. For example: For a centered you could just decide if you can go for a risky skill or not in this exact moment it pops up.

However now you kinda need to plan more ahead. With the new conditions, you kinda want to push the progress phase further into the rotation to take advantage of all the malleable. But probably just until you build up all your inner quiet stacks, as you then don’t want to be interrupted by the need to push progress in the quality phase, next to the danger of not completing the craft of course.
The same happens with the primed condition, while mathematically it might be not worth to get an extra 10 durability from manipulation for the full cost in comparison to a pliant manipulation, it might be worth it compared to no condition usage of it and then taking a full cost masters mend with only 30 durability restoration instead of the 50 it would’ve gained. Hence miqo needs to decide, if it wants to fish for pliant or not, etc.

While I don’t know (and I don’t need to know) if the developers need more time on those specific things, I definetly can see an increased complexity here.

[NekroParticipant]

malarkey wrote:

Late getting back to this as I just started gathering again but yes Miqo does use cordials while gathering in scenarios. I just watched her do it. You just need the “use cordial” box check in the gathering preset, save, and the cordials on a hotbar. I remember it being done before as well so /shrug

Well I remember it to not be working for botanist/miner. I tested it again and, as you said, miqo is using cordials now. It could be that it was fixed somewhere or I was just not overwriting the preset back then when I tried this feature. Thanks for the info.

Still prefer fishing over botanist/miner for those aethersands though.

[NekroParticipant]

dam10886 wrote:

i probably have something setup wrong it has been a year since i played but when i run the rotation it takes me all the way to the node it pops yield and pick clean and then stops like never collects anything just stares at the node doing nmothing.

You probably don’t have enough perception for pick clean to work. In that case Miqo will break.

Nekro wrote:

If you don’t have enough perception to have at least 1% chance to obtain the items in HQ, then Pick Clean wont work. In this case you need to adjust the Gathering Rotation for 750 GP to not have Pick Clean. For example: Yield+2, x1 Yield+1, Hit Once, x1 Yield+1, Hit Once (even if the adjusted rotation does not cost 750 GP, do not change the name of the rotation itself)

You can look at earleebyrds answer here: https://miqobot.com/forum/forums/topic/scenario-5-4-legendary-nodes-materials/#post-25339 how to remove pick clean from the 750GP rotation.

[NekroParticipant]

If I understood correctly you basically want to have a hook like function, to react to specific conditions in your scenario. So you can interrupt your current activity on a specific time to do something and then return to your old task.

I think your solution would be a little bit too specific and hardcoded to really be worth the effort taken to adjust the gathering presets. As the tabs like fishing, gathering, crafting etc. are there for a single task I guess. For everything else you have Scenarios.

In my opinion a new Scenario function would be better. I already suggested (and some others have too) the possibility to call specific chapters in a scenario from within a scenario (basically like functions, you can call everytime and everywhere you want).
A variation of that with an function like hookTime() would prove quite helpful not only in your case, but possibly in more cases like the old unspoiled nodes from Heavensward/Stormblood or others in the future aswell. The function would work like this:

hookTime(Scenario-Unspoiled-Node-8AM, 08:00et)
hookTime(Scenario-Unspoiled-Node-1PM, 13:00et)
hookTime(Scenario-Unspoiled-Node-4PM, 16:00et)
teleportIf(REGULAR NODE LOCATION)
gatherPreset(PRESET)
gather(999)

So it adds a condition which is periodically checked (like every second or so?) and once it matches a condition, the hook triggers the Scenario mentioned in the argument.

Lets first just assume that the hookTime() function returns to this Scenario and the same Chapter it was called from, but in the end it might need a system like the current koCheckpoint() mechanic where you can tell miqo which chapter she can re-enter on, once the linked Scenario was executed. Also it needs at least a limit how much you can nest those hooks, as in theory you could create a recursion of Scenario-Calls.

Thats just a rough idea, but would be probably more flexible and more useful in general. Also there could be more hooks in the future like hookWeather() which I would love to see, instead of the current skipBadWeather() function, cause it’s still executing the line under it for a minute, even if the weather is not good. Thats a bit clunky to use in my opinion.

• This reply was modified 4 years ago by  Nekro. Reason: wording, more specific examples

[NekroParticipant]

mik1312 wrote:

your scenario did work fine the last couple days until today, but for some reason i get stuck there sometimes now.

Well, I didn’t encountered this yet. And I let it run for almost 20-30 hours or so, but I made a quick fix where that shouldn’t be happening, you can import the new grid and delete the old one with the same name.

Attachments:

You must be logged in to view attached files.

[NekroParticipant]

PinHead wrote:

I tried the Robber Ball route and I disagree with you, using Versatile Lure + Cordials achieved the exact same results in a 30 minute time period and I didn’t have to buy the bait. Also, obtaining Cordials/Robber Balls is just another scenario so the cost of either is negligible due to Miqo doing the work. Time though; my cost of time is different when I am at the keyboard vs. not at the keyboard. I would never run this while I am at the keyboard due to the slow farm rate, however I would run this on my side desk while I’m working.

I tested this a lot aswell and I can’t really believe that, but nonetheless I tested it again.
Edit: Did you turn snagging on? Cause I don’t, maybe try robber ball without snagging.

Both tests during same time period, weather was luckily exactly the same, with the exception that one time it was clear (Robber Ball) and the other was fair (Versatile Lure), which is normally treated as exactly the same in 99% of fishing.

Stats:
~2120 Gathering
~1700 Perception
~890 GP

Robber Ball (Without Cordials) – 30min

-> Total Fish: 62, Collectables: 22

- Low Tier (below 100):  4 (85, 87, 88, 98)
- Middle T (below 200):  5 (113, 145, 146, 179, 192)
- High Tier (>= 200):   13 (200, 200, 201, 203, 204, 204, 206, 206, 206, 207, 209, 209, 209)

Result in Aethersand (59 Total):
-> (Low)   = 0, 0, 0, 0
-> (Middle)= 3, 4, 2, 2, 0
-> (High)  = 3, 3, 3, 3, 8, 4, 3, 4, 3, 3, 4, 4, 3

Bait used: 62 Robber Balls (310 Scrips)
Cordials used: 0

Versatile Lure (With Cordials) – 30min

-> Total Fish: 64, Collectables: 5

- Low Tier (below 100):  0 ()
- Middle T (below 200):  2 (112, 131)
- High Tier (>= 200):    3 (201, 208, 210)

Result in Aethersand (12 Total):
-> (Low)   = 
-> (Middle)= 0, 1
-> (High)  = 3, 4, 4

Bait used: 0 Versatile Lures
Cordials used: 9 (450 Scrips)

So while the final results of the extracted aethersands are not that useful, as that depends on your luck. In average this is the same everytime for me. You’ve the same pool, but the chances for specific fish vary a lot. And in my experience the robber balls are the better baits in all matters (scrips and efficiency). Also: The total fish counts also count in the fish that got away.

AzuraMage wrote:

m I doing something wrong maybe, or is it purply RNG not on my side.
I have 2091gathering, 1731Perception on my fisher, and (490HQ melded gear, with 475 relic) and I’ve been fishing for an hour, without a single fuchsia, get loads of HQ fish which it throws away, but… that’s not what I’m after :p

Well the fish doesn’t need a folklore book so that can’t be it. Ensure that you have the skill on your hotbar which enables collectable fishing and have the right bait in your bag. Of course you could be really really unlucky, but I never fished an hour for it without at least seeing the fuchsia once.

Edit:

AzuraMage wrote:

Edit: I removed snagging, and it worked fine.

Well ok, that could maybe explain that, cause I am not using snagging for it. The test results above are all without snagging.

• This reply was modified 4 years ago by  Nekro.

[NekroParticipant]

vega wrote:

am i missing something or is it normal that it takes like 4-5 fishes of other kind to catch a fuchsia, + with the robber balls always getting consumed despite releasing the not needed fishes, is this really an efficient way?

Fishing is purely RNG, you can increase the odds in your favor by choosing the correct weather, bait, time and some skills. That also means, that you might get a streak of no fuchsia fish, however you might also get multiple ones in a row. I think it’s the safest method for aethersand farming, because you rarely move.
If you are asking for efficiency, I say definetly. Sure you will use some robber balls, but you don’t need any cordials. The bait isn’t that expensive and you still can get up to 8 aethersands from a single fish (with the bonus).

PinHead wrote:

I used 100+ Hi-Cordial and received over 300 aethersand. This took hours of botting to achieve.

I would suggest going with the robber balls and ignoring the cordials. Fishing is the most GP efficient activity, when it comes to collectables. If you compare the cost of a cordial to a robber ball you burned trough cordials worth 1000+ baits, which you could have gotten way more than just 300 aethersand from, probably in shorter time too.

[NekroParticipant]

Trotski wrote:

The teleport locations are in german? How can I change that?

You can just rewrite them, however as the others already have pointed out: You don’t need to. The Scenario will still work regardless your client language. It might just impact you, if you want to read it.

craftlalaruler wrote:

I’m having issues with miqobot waiting longer than the advised ET.

Miqo will tell you how long she will wait in the logs. If you are waiting for more than around 300-360 seconds you might started the Scenario in the wrong chapter. Be aware that it uses the 24h format.

[NekroParticipant]

uwu wrote:

I got rid of the scenario clutter and teleporting back to the house after every chapter. Also optimized the gathering rotation to use Brute/Brunt Force after the 5th hit instead of pick clean if people want some HQ items

Nice, I will take over the 500GP Rotation, if I update it the next time. However, it will rarely be used, as you have enough refresh to reach the 750GP. Even, if you started 1min late. It seems, you have equalized both rotations, but I think, if you want to go for Quality, it’s better to include an HQ +30% after the Yield+2 (for the 750GP one), 800GP should be working aswell, once it’s in the cycle. For crafting, HQ Gathering Mats are hardly anything worth though.

The “clutter” is intentional. With the setup you can jump in anytime you want, without pressing the “next”-button. If it is for example 02:01 ET and you start the gathering Chapter (in this case Chapter 3), then you will need to press next for the afkUntil line, as it will wait for the next window. It’s more a thing of preference and I know some people didn’t like the teleport in between, so thanks for adjusting it for those 🙂
I also like that you are flying to the nodes a short time beforehand (I might use that aswell, if I update it again).

uwu wrote:

Guess materia extraction isnt working so you need to // it in chapter 1

Materia Extraction is working fine for me. Ensure that you have the icon on the bar. If it still doesn’t work and you fullfill the other requirements from the docs, it might be a language problem again. So you might want to share your client language. For german it is working fine.

• This reply was modified 4 years ago by  Nekro.

[NekroParticipant]

soccer09 wrote:

I see it happening only on the mining scenarios. that it will not auto gather, I have all folklore so i know that is not the issue at least. I have tp physically click through the mining spots, BTN seems to be working normal

So if I guess correctly: You go to the gathering point (it is showing up), then you press your skill for yield+2 and then it just stops and doing nothing?

If yes, please look into this and ensure you have enough perception on your miner or adjust the Gatherer-Rotation to exclude Pick Clean.

Nekro wrote:

If you don’t have enough perception to have at least 1% chance to obtain the items in HQ, then Pick Clean wont work. In this case you need to adjust the Gathering Rotation for 750 GP to not have Pick Clean. For example: Yield+2, x1 Yield+1, Hit Once, x1 Yield+1, Hit Once (even if the adjusted rotation does not cost 750 GP, do not change the name of the rotation itself)

Edit: As another fix, you could remove the line rotationIfGP(GR-Get_more-750GP) from all Gathering Chapters for miner (4,6,10,16,18,22)

[NekroParticipant]

Update:

Adjusted the grids to fix some problems like descending weirdly or flying head on against an aetheryte.

– If you have a previous version, you can just import the new grids from the “SC-5.4_Gathering-grid-update-1.txt” file (in opening post) and delete the old grids.
– If you don’t have a previous version, just download the full Scenario and ignore the hotfix file for the grids.

[Author]

Posts