Is there any chance of an automatic reconnect feature?

[LazyF2P]

Hello, im interested in using this script since i dont really have that much time to farm embers for all of my SSRs, but my connection is kind of unstable, has the idea of an auto retry been said already?

PS: Is this still safe as of today with the new JP security updates and such?, much appreciated.

[29988122]

account security Sure.

https://news.fate-go.jp/ No security update recently btw.

I'm using it daily, just done farming today 2 hours ago using Nox emulator myself. No worries mate.

---

Automatic reconnect The point is, there's a bunch of different reconnect behavior. We'll have to "handle most of them" before implementing such a feature.

1. No response, retry or give up
2. There's a new update available. Click to return to main screen. 2.a. If download new data window appeared 2.b. If "you're still in battle, resume?" window appeared The list's not exhaustive, tho.

And we need ALL those screenshots from JP, TW, EN, CN server.

Yeah that's not easy...

That's why we ( namely @potchy @TryBane @ryuga93 @29988122 ) are trying to figure out a way to detect any irregular routine in general (when the unexpected window appeared), therefore we won't have to ask for screenshot everytime.

[TryBane]

A standard auto-reconnect should be easy to implement. We can simply insert a new check in the main loop for when it asks for a reconnect and have it click retry. Considering the way battle.lua works, this should not impede anything. I also believe this will not cause any problems with autoskill, but if it should we can always insert a check for the reconnect within the loop used to determine if a skill is clickable.

At the same time we can also insert a check for when you fail the mission if you want. That should also be fairly simple to implement. Just need a copy of the refill screen from in the battle, both with and without master seals available (since the button position is different in both cases) to click withdraw. Alternatively, we can simply make the program withdraw then stop altogether (in case losing was a result of forgetting to make a change to autoskill or something).

[potchy]

/\ there's already an issue opened for mission failure (#92), but I have no idea how's it going.