Closed Silph-Road closed 8 years ago
Please do not disable this discord channel. Also, it seems 0.37 is not enforced to update yet. Do we need to disable so early?
Discord channel will not be disabled. The problem is that if they force apps to update, we cannot detect that and they still let us connect to old API, every single account will get flagged or banned, since they know its not the real app playing. After that, they will switch API permanently.
Most ppl don't check the issues page and will keep trying to bot and will end up getting a ban, cuz they didn't stop in time.
Just a question: I had already installed on my phone the latest 0.37 version but I have used bot till some hour ago, should I wait to get banned sooner or later?
Renton,
They will just assume it is an UN-Updated device.... So you should be good...
Keep in mind the way this works,
***We don't know when they will force update App, so best not to use an old API bot. What is best is for the bot to be updated to the new API, then we run no risk of getting flagged. I recommend you stop botting, you are okay now but in any amount of time from now you may not be when they force update.
Sorry for the dumb question but even if I have played some times on my phone, using 0.37 version, and some times by the bot, which has the same device configuration of my phone, I might sleep sweet dreams?
oops, did'nt see that post by @Renton91, disregard my last two posts @tws101
@Renton91 that is a possibility if the device ID were the same, but it is not guaranteed i assume you used .37 APK (manually installed) and one can always roll back to official play store APK .35 and still be legit.
@Silph-Road thanks for the answers! I hope it will be so!
@Silph-Road This is making sense. Will it be a killswitch? But please let me know how to turn off killswitch. I want to try my luck before they force 0.37.
I would prefer warning us to use at our own risk instead of forcing us to stop botting
@ValorRed @mkcs121 There is a way to disable the killswitch, just try to search for it, It was even done when Necrobot was first killed.
still using 0.33 on my android phone without any issue ;)
Which limit? both of these? "PokeStopLimit": 1998, "PokeStopLimitMinutes": 1470
@ValorRed you need hex editor, and edit/alter a bit codes on necrobot binary.
not run bot
With NecroBot2 v0.9.9.2 you can now bypass the kill switch. You will be prompted to override on startup. Bot at your own risk! You have been warned!
We might have been over panic. See this: From https://www.reddit.com/r/pokemongodev/comments/52hfcl/opinion_how_safetynet_will_kill_apis_and_possible/
You also don't have to emulate SafetyNet. What you need to do is send a Valid SafetyNet request to the Google servers, which will then send you back the response that you have to give to Niantic's servers. Which then checks if that response is valid by sending it to Google. All you need is what the REST API for SafetyNet. And know what is sent.
I do not care whether my account will be banned or not. Since I had no respect with Pokemon Go since they released version 0.37.0 which can not be used on Rooted Device. And I would not UnRoot my device just to play Pokemonshit. So now I will just ... .. BOT BOT BOT ... ... all of my account. If my account is banned ... will create a new account and then BOT again .. and so on .... hell yeah ..
I want to ask, how do I get when star Necrobot2 do not need to type "Y" to continue the program?
thank you
You type y to continue
@aryaputrapande calm down please. Dev here are doing a great job, one push is not much for us. Be considerable for the average users.
I think Niantic roll this version out just to try the water. It's pretty obvious, it won't block much on bot, but spoofer might be. But they will get a big drop of users. Let's all go to google play to put 1 star review and complain about not supporting root or custom ROM devices. Such a wide spread game shall not make this wrong turn.
Dear @jjskuld , I used task to run necrobot scheduled. Run every windows on for 1 hour... then close for 15minutes... then run again for 1hour... looped until computer shutdown. So, how do Necrobot can run automatically without any confirmation request from the bot by pressing 'y'?
or is there another way?
@ValorRed don't worry bro... i am still calm and cool... :)
True. A command line argument shall be a reasonable request, for the old school boys.
I have add an cmd line option to disable the kill switch #134
Are we clear to bot under 9.9.3? all updated to new API?
@tws101 We are NOT updated to the API yet, so bot at your own risk if you want to override the kill switch.
still using 0.9.7, feel it's the most stable version.
jjskuld notifications@github.com于2016年9月14日周三 14:30写道:
@tws101 https://github.com/tws101 We are NOT updated to the API yet, so bot at your own risk if you want to override the kill switch.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Necrobot-Private/NecroBot/issues/121#issuecomment-247161244, or mute the thread https://github.com/notifications/unsubscribe-auth/AVESRBBN46ARzkjj026Q5VoxU4vgIOoSks5qqGeNgaJpZM4J8BNL .
@zc3721 same here :)
This raises an interesting question for me. Those that wish to bot at their own risk right now seem to be doing so at their own peril. i.e. - if they get banned, they get banned. Why should I care? However, could these risky botters be hurting the community as a whole by tipping Niantic off to other signatures of bots? May be @samuraitruong @jjskuld @Silph-Road @ntatoo or others can answer this question: If these botters get banned as described (using an old API when a new one has been forced, if it has yet), are there other things that Niantic could learn by looking at their actions to identify other bots?
In a way yes they are hurting since this bot is not meant to be abused to "stick it" to niantic and it only helps to not use a bot when they do make the API change, as they will know that those players we in fact botting, from that point on they could try to isolate behaviors or specifics of the API calls that all/majority of these users are using, that in turn can essentially allow them to create filters that can be used to identify others, but it's a speculation on how bad they want to find botting accounts.
Keep in mind we don't want this bot to be published or become the "popular" bot as we don't benefit from that, it's supposed to be fun and not to profit from or to be abused in order to facilitate any hate towards the game maker.
@Silph-Road Fine line to walk, having a bot good enough to do what it is asked, without becoming "popular." Also hard to watch users put your (general "your") work in jeopardy for selfish goals (I say that with no malice, really. And I don't mean to single anyone out). On the one hand you sort of need the kind of large community that can provide feedback to tweak the bot, on the other it becomes a Roman Empire problem, too big to succeed. A sticky situation all the way around.
I just hope ppl stop botting when .35 phone apps are force to update to latest .37 app.
FYI: Right now .33 apps are being forced to update.
@ajns73 That was happen last time. we try to protect but you can use at your own risk. last time when they force app update, we still using old API, at that day milion bot account was killed. did you play bot on that day?
@samuraitruong No, and I haven't botted since the Killswitch. It seems to me that if we are going to use this "issues" page to make suggestions, reports, and sometimes demands, on developers we should probably respect their decision to use the killswitch. It makes more sense to me to stop for a week and be able to bot for 6 more months, than try to slam in as much botting as possible before a ban.
to what samuraitroung mentioned, he is referring to the last time they changed API, early in August.
Thats exactly what happened, the users that are using the bot right now.... could also end up loosing their other accounts if niantic wants to get creative and examine info that can link all other accounts botted on the same computer and then check them and then ban all those accounts.
sorry, I am a bit lost, What wrong here, I thought we activated killswitch, then people ask we give option to bypass it. so what we are complaining about . I didn't focus on this issue .
But @Silph-Road is correct, one they identity you are bot by connect using old API, they will learning you data and identity other player data has same pattern.
If I am niantic staff, I will 95% of bot accounts by scripting . They didn't do that because it low priority atm, so using bot just for short time, in long times when ninantic have that item "Kill bot accounts" move from backlog to ready. we will be swiped out.
@samuraitruong Not complaining at all. Just observing that there is more to botting through the killswitch than meets the eye.
I, for one, am fine with stopping for the time being. Obviously the killswitch was implemented for a reason. As you have said, this puts users who choose to bot at greater risk of being banned. My point originally was that these users are actually risking more than just their own accounts. Perhaps my account will get banned even though I choose not to use the bot now because of things that Niantic learns from people who are botting now. But that is a risk that I must live with.
Think of it this way, if you drive drunk you are risking the lives of all those in the car. If you crash, you hurt not only yourself but your passengers. However, it was always their decision to get in the car with you drunk in the first place. So, while they may not exactly deserve their fate, they have to acknowledge their role in it.
people in community are very complicated, They have difference expectation. very hard to make them happy at all, but we try to do a best for community.
@samuraitruong Complicated indeed! :) As they say, you can't please all of the people all of the time.
here we go, the update push is online, so probably good time to stop botting :)
What version .35 to .37 is being forced now?
Or .33 to .35?
They did .33 to .35 about 12 hours ago.
I had 0.33 on my phone and I was pushed to update to be able to play now running on 0.37 (latest on google play)
got 0.37 today... app run snappy and faster, but every time I visit gyms, app crashed and closed. blahh!
Closed. See #285
We are disabling the bot, to protect your accounts.
Stay tuned.