|
Post by pimpis on May 11, 2019 13:49:37 GMT
Thank you for making this bot it works great. I did have it stop but it was because the optimization was enabled and disabling it worked. I was wondering if this bot has anti ban features? I am not familiar with if they are necessary, but having randomized clicks and avoiding bot like behavior such as the fleet reselect every map start would be safer. Again, thank you for your time. The only reason why people get banned in the game is if they are modifying the APK. Bots are safe. Botting is against the game ToS and there have been a few cases of botters being banned. Although at the moment the game doesnt have any anti-bot detection, if you blatantly bot(like doing an absurdly high amount of attacks in a small period of time or getting to top ranks in events) and get reported or flagged, you will be manually checked by the game staff and you will get the banhammer. So it depends on how much you abuse it, but still not completely safe.
|
|
|
Post by liaoz2511969 on May 11, 2019 14:29:24 GMT
Thank you for making this bot it works great. I did have it stop but it was because the optimization was enabled and disabling it worked. I was wondering if this bot has anti ban features? I am not familiar with if they are necessary, but having randomized clicks and avoiding bot like behavior such as the fleet reselect every map start would be safer. Again, thank you for your time. The only reason why people get banned in the game is if they are modifying the APK. Bots are safe. Botting is against the game ToS and there have been a few cases of botters being banned. Although at the moment the game doesnt have any anti-bot detection, if you blatantly bot(like doing an absurdly high amount of attacks in a small period of time or getting to top ranks in events) and get reported or flagged, you will be manually checked by the game staff and you will get the banhammer. You're probably mixing this up with Kancolle Yes botting is against ToS, but tracing user behavior on screen and report it back without user's consent is a violation of Google Play's ToS and Apple App Store's ToS (especially Apple bc they are bananas about this couple of times before). Also the recording the api onTouchEvent() for detection(link) is resource consuming and if YoStar is not reporting it back to their server, the only thing they can do is to do manual calculation client-side for bot detection, which is another overhead cost. On the otherhand, if they actually implement that, it is still easy to circumvent this by implement Region(x,y,w,h) from the native Ankulua call to random click (which this script is already doing). Also, It seemed like you have no idea of how botting works and how it is different from hacking/sniffing. Hacking and sniffing packets to change the damages output is what made those bastards banned. Moral of the story: if you are not ranking and not affecting anyone (aka playing this game as a single player game), you will not get banned. Anti-bot detection is basically self-destruction for mobile game (mobage) since most client-side devices will not be able to cope up with it, and spending time to event code it is just a waste of time and resource while you can spend on improve gameplay, content and bug fixing. Back to kancolle, yes they do have bot detection, but it is laughably easy to get around (there's only 3 methods that they used to detect botting: detect unauth API calls (auto ban), detect clicking position (if click 1 spot everytime -> catbomb soft ban 1 month), detect play time (a little bit more complicated with maths, but basically if you play more than 18-20 hrs per day -> catbomb soft ban 1 week)). Instead of working on improve the damn game the KC dev just spent months to muster up a not-even-decent bot detecting mechanism... (god damn useless KC devs). However, this bot detection make sense since KC have a rewarded ranking table for those who grind so botting is ruining it for others. And back to AL, there's no awarded leaderboard for grinding so bot detection doesn't make any remote sense. The only way that YoStar can kill botting is to implement root detection and app detection, but hey Magisk on android exist... And also it will pissed off many people who need roots for their devices (and again, even without magisk root detection can still be circumvented - looking at Love Live SIF) Sorry for lengthy post, but here's the TLDR: Yes, botting is violating ToS (just like any games), but anti-bot feature is not coming (any time soon) and easy to get around, so you (99%) will not get banned for botting. Also FUCK KANCOLLE.
|
|
|
Post by pimpis on May 11, 2019 14:46:45 GMT
Botting is against the game ToS and there have been a few cases of botters being banned. Although at the moment the game doesnt have any anti-bot detection, if you blatantly bot(like doing an absurdly high amount of attacks in a small period of time or getting to top ranks in events) and get reported or flagged, you will be manually checked by the game staff and you will get the banhammer. You're probably mixing this up with Kancolle Yes botting is against ToS, but tracing user behavior on screen and report it back without user's consent is a violation of Google Play's ToS and Apple App Store's ToS (especially Apple bc they are bananas about this couple of times before). Also the recording the api onTouchEvent() for detection(link) is resource consuming and if YoStar is not reporting it back to their server, the only thing they can do is to do manual calculation client-side for bot detection, which is another overhead cost. On the otherhand, if they actually implement that, it is still easy to circumvent this by implement Region(x,y,w,h) from the native Ankulua call to random click (which this script is already doing). Im not mixing stuff, there are botters who have been manually banned in AL, though all of them were blatant cases. In fact all the bans they do are manual, even for the people who use modded APKs. They stated in their discord a few months ago that they were working on adding powerful "anti-hack" measures to the game, especially aimed to people who used mods, although botting was also mentioned, but for now nothing has changed.
|
|
|
Post by averlite on May 12, 2019 10:46:12 GMT
hello sir why the winrar always getting error when i extracted it? thank you
nevermind its fix now
|
|
|
Post by justsomegamer on May 16, 2019 11:46:19 GMT
Hi, tried your bot and i must say it runs nice. Did you by chance implement a routine for 7-2? I saw the bot move to the 4 locations the ?-Nodes spawn at - even when there was no ?-Node cause it collected it before. thats awesome! Is repair kit usage implemented - would be great to have a routine or option like "use repair kit after x fights" Good job keep it up i like the bot! edit: Can you give us a option to select up to what rarity the bot is allowed to scrap ships if we run out of dock space ? edit2: bot "finally" threw an error imgur.com/a/PhfoQPQ But i guess it has more to do with me running out of oil.. edit3: A few things i noticed while the bot ran. If a enemy is on A1 the bot trys to click it but ends up clicking the info symboles on the top, like Threat level, ammo effect or formation effect. - Formation is not kept, bot changes back to single line, why? On getting ?-nodes, the bot sometimes clicks the item it got, which causes delay.. maybe adjust that click area bit? If you want I can make a recording and get it to you?
|
|
|
Post by Hikaro on May 17, 2019 12:39:58 GMT
Hi, tried your bot and i must say it runs nice. Did you by chance implement a routine for 7-2? I saw the bot move to the 4 locations the ?-Nodes spawn at - even when there was no ?-Node cause it collected it before. thats awesome! Is repair kit usage implemented - would be great to have a routine or option like "use repair kit after x fights" Good job keep it up i like the bot! edit: Can you give us a option to select up to what rarity the bot is allowed to scrap ships if we run out of dock space ? edit2: bot "finally" threw an error imgur.com/a/PhfoQPQ But i guess it has more to do with me running out of oil.. edit3: A few things i noticed while the bot ran. If a enemy is on A1 the bot trys to click it but ends up clicking the info symboles on the top, like Threat level, ammo effect or formation effect. - Formation is not kept, bot changes back to single line, why? On getting ?-nodes, the bot sometimes clicks the item it got, which causes delay.. maybe adjust that click area bit? If you want I can make a recording and get it to you? Yes, I will be grateful
|
|
|
Post by caminio on May 20, 2019 11:21:31 GMT
The bot is completely broken with the UI update.
Are you planning to update it, or if not, will you release the source code on the future?
|
|
|
Post by justsomegamer on May 20, 2019 16:43:42 GMT
Of Course the bot is broken with the UI update. Everything looks different. give the guy a break and check back in a week.
People and their expectations...
|
|
|
Post by gamer9001 on May 20, 2019 20:04:04 GMT
Of Course the bot is broken with the UI update. Everything looks different. give the guy a break and check back in a week. People and their expectations... Yeee, and considering it literally just came out and people are already expecting it to work, or for OP to update is lickity split
|
|
Hex
New Member
Posts: 3
|
Post by Hex on May 20, 2019 21:48:12 GMT
Really nice bot, could you give us an updated discord link? The last one expired
|
|
|
Post by niersama on May 21, 2019 1:32:22 GMT
it was a good script, I could only use it for 1 day but it was incredible. Good luck if you continue with your project.
|
|
|
Post by Hikaro on May 21, 2019 3:29:30 GMT
Hello commanders! I appreciate your expectations. The update will be released this week, so stay tuned. (updated link to Discord)
|
|
|
Post by suwintzi on May 21, 2019 17:53:58 GMT
@hikaro Thanks, I literally just got to use both yours and the other 3-4 bot for an hour before the update hit and everything broke.
|
|
|
Post by takori on May 23, 2019 17:33:58 GMT
Is it possible to add Bismarck event support before it ends?
|
|
|
Post by suwintzi on May 24, 2019 6:21:43 GMT
takori I'd rather he prioritize getting the bot working again instead
|
|