Closed Gutenhl closed 5 years ago
For the time being, I wouldn't use it until Masuzu gives us an update, or changes how Sarasabot joins raids. It's very likely that continued use of auto-join would get your account flagged.
I'll have to wait a bit to renew the license. I just hope there is a solution before finishing the magnafest.
Feels bad since I resubbed like yesterday.
@Masuzu Do you have any information on this, and whether we should temporarily not use Sarasa bot just in case?
same
I would wait too.
Sadly I renewed my license two days ago...
The discussion thread on reddit
https://www.reddit.com/r/Granblue_en/comments/b5a98p/viramate_20193241_update/
Not sure if it’s targeting Zooey/Sarasa
Zooey should be safe I guess?
Still interested to how Zooey refill AP without popping up refill window and clicking it tho... It’s the only behavior Zooey not working like a manually playing player?
We need to summon @Masuzu
Hello all, I am on it. ETA for a new version addressing this issue and not skipping the regular way of joining a raid (that is to say, going through the page where you are supposed to enter the raid ID): within 5-6 hours from now. In the worst case scenario, within 24 hours.
Thank you! Does this affect zooey in anyway?
Is there any precautions we should take with how it seems Cygames is dealing with certain things?
Zooey is not affected in anyway by recent changes.
@Alissa1122 As far as I know the AP and BP refill are still fine, but I may consider adding a different "slow" refill which goes to the supply screen later on. Please correct me if I am wrong.
The version 2.4.0 introduces changes regarding this topic. Should you encounter issues, feel free to continue the discussion on this thread. https://gbtools.azurewebsites.net/SarasaBot/en/Home/PatchNotes#2-4-0
Thank you again for bringing up this issue.
Amazing work as usual! Good job masuzu, I'll be sure to test it out soon once I get to my pc!
On Thu, Mar 28, 2019, 5:49 PM Masuzu notifications@github.com wrote:
The version 2.4.0 introduces changes regarding this issue. Should you encounter issues, feel free to continue the discussion on this thread. https://gbtools.azurewebsites.net/SarasaBot/en/Home/PatchNotes#2-4-0
Thank you again for bringing up this issue.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Masuzu/SarasaBot/issues/260#issuecomment-477784141, or mute the thread https://github.com/notifications/unsubscribe-auth/AXRag2v1LOxTLAEv0ay13BbnGweTRqwbks5vbTj9gaJpZM4cGCRV .
Since I used this bot during the last few days, I hope this won't make any problems...
Anyway, I got a problem with the new version. The bot successfully puts in the raid code, goes to the summon selection screen but then does not select a summon. It just goes back to the raid screen, even when the summons, hp percentage and amount of players are all correct. It's hard for me to see the reason for this happening, as the bot only gives the message "Failed to join raid."
Aside from that, is it really save for the bot to just automatically go to the raid ID screen, without clicking on the tab?
The version 2.4.1 includes a parameter ForceRaidJoining
under the debugging section. (If you keep your current SarasaBot.ini file, that parameter will be set by default to true even if it is not present in the file).
This will force Sarasa to join the raid after clicking on the "join raid" button and display an error message in the console if something went wrong in the way.
The click on the tab is actually registered as if it were a real click (or a tap on the tab if you were using a tablet). It is just that it is so fast that it is not noticeable. Currently there are no in-game checks related to this.
Sadly, 2.4.1 still gives me problems.
Compared to 2.4.0, the bot now actually clicks on the summon when everything about the raid is correct. This time however, it won't click on the "OK" button on the party selection screen. Instead it refreshes the summon selection screen twice (but still clicks on the correct summon each time) and then plays the captcha notification.
Edit: I seem to have fixed it by redownloading 2.4.1 and using a fresh SarasaBot.ini file.
Thank you for the feedback @UminekoScarlet. This behaviour was reverted in the version 2.4.2: https://github.com/Masuzu/SarasaBot/issues/261
Thinking about using this as viramate is being discontinued. From what I understand, this is a safe bot to run, as long as you're paying attention and don't overdo it?
@SeaOtter65 Yes it is. The bot will automatically stop whenever a verification screen or a captcha screen pop ups. There is also an option not to use Viramate shortcuts either, which will make it click manually on skills (click positions are randomized).
i heard it from viramate user. they're disabling auto-join on viramate newest update since the new anti-cheat update. is it still safe to use sarasabot? since sarasa also auto-join instead of copy pasting code