[Per SeParticipant]

I took a short break from the game, so if any of the below does not reflect the current state of Miqobot, I apologize. That said…

I do the same. In the past, I haven’t given it a chance for two reasons, one practical and one lazy: Firstly, since I can’t see Miqobot’s proposed solution before it is executed, I can’t verify against any sims (and since it operates determinisitcally on some branches, I couldn’t do that anyways), so in my mind I therefore potentially stand to lose valuable mats; secondly, I don’t feel like waiting for Miqobot to crunch the numbers every time I pull up a new craft, especially when it’s one I’ve done before at the same stats I presently have, when I could just use a set rotation.

The caveat to this is the admittedly painful process of programming in my rotations in the required format of a long comma-delimited string, which is prone to initial transcription error. If we could save rotations Miqobot has previously used (which I believe has been asked before, and I don’t remember the explanation given as to why that was impossible/extremely difficult to implement), or we had a better interface for entering custom rotations, it would be a non-issue.

I’m sure there’s a reason that we have to tell Miqobot the hotkeys we want used, as opposed to telling it the *abilities* we want used and having it execute them directly (which it already does when computing its own rotations), but I don’t know what that reason is.

By way of a parting comment, I don’t mean for any of the above to indicate that I don’t like Miqobot, or am not grateful for the benefits it provides us. I’m a happy repeat subscriber. 🙂

EDIT: If there’s a better way to run custom rotations, I would love to hear it. I rely on using custom rotations in the Solver, as opposed to keying macro hotkeys from a Scenario, as I very much like the Solver’s ability to stop every now and again to repair.

• This reply was modified 6 years, 1 month ago by  Per Se.

[Per SeParticipant]

Here you go!

This scenario fishes for Usuginu in two separate spots, each for 40 minutes, then heads over to Dawn Throne and fishes for collectible Sweatfish for 40 minutes. The scenario then repeats 4 times, or however many times you change the repeatAll() in the final chapter to.

The two separate spots are there to avoid the fish in either spot becoming Wary, and the Sweatfish chapter is there to avoid hitting the Wary state for the entire Usuginu fishing area. You can reduce the time on the Sweatfish if you don’t particularly care to grab many Everdeeps; I wouldn’t go lower than 5 minutes, just to ensure you land at least 2 fish in the event of hideously bad luck.

You could, of course, sub in any fish for that chapter, if you don’t want to carry a supply of Stonefly Larva.

Usuginu are pretty hard to find, though I feel like they might have stealthed in a buff to their rate of appearance recently. I use a 5-minute run of Usuginu catching to break the Wary state when I’m fishing specifically for Sweatfish, and in the space of 4 runs (so 20 minutes total), I got 9nq/6hq the other day. By comparison, the first time I successfully ran this scenario, I got 33 in the span of several hours.

Attachments:

You must be logged in to view attached files.

[Per SeParticipant]

Give me a minute to clean it up, then I’ll post it.

[Per SeParticipant]

Ah, I see the logic it’s using now. I’ll give that a whirl.

Thanks for the advice, Lyfox!

• This reply was modified 6 years, 9 months ago by  Per Se.

[Per SeParticipant]

Okay, well, new wrinkle. It stopped working with NQ Ruby Shrimp as well, so after trying multiple profile and scenario setting iterations — as well as restarting Miqo several times — I reverted to an older version of the preset file, with the EXACT SAME SETTINGS, and now it works with both NQ and HQ Ruby Shrimp.

I’m out of ideas. I’d like to go back to fleshing out the scenario, but now I’m afraid moving anything will break it!

[Author]

Posts