Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account getting banned #50

Closed
nocomp opened this issue Mar 6, 2018 · 25 comments
Closed

Account getting banned #50

nocomp opened this issue Mar 6, 2018 · 25 comments

Comments

@nocomp
Copy link

nocomp commented Mar 6, 2018

ola,
here is a new type of error i get often after running the bot quite a bit, 3-4 hours

19:31:53 - warn: Unhandled object in map update: FQuestUpdate
19:32:04 - error: Error: Error from server: 412 - Precondition Failed
at Client.call (C:\snapshot\dracowalker\node_modules\draconode\bin\index.js:143:19)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
19:32:04 - error: __type=FServiceError, args=[], cause=SESSION_GONE
PS D:\docs\dracowalker>

@niicojs
Copy link
Contributor

niicojs commented Mar 6, 2018

It seems the session has been invalidated by the server.
This can happend if bot is running too long or if you log in elsewhere (on your phone for example).

I'll put on my todo list to do auto relogin.

@nocomp
Copy link
Author

nocomp commented Mar 6, 2018

hmm good thought, i never used my bot accounts on mobile, so surely it s cause of too long connection.
mays be a schedduler would be great.
thxx for the effort

@xandymp
Copy link

xandymp commented Mar 6, 2018

I'm getting this error too. Started this morning after doing some tests with the ui item use.

@xandymp
Copy link

xandymp commented Mar 6, 2018

I think I found out the problem.
screenshot_20180306-101916

@nocomp
Copy link
Author

nocomp commented Mar 6, 2018

weird, none of mine are banned, i ll check in the coming days what happend

@xandymp
Copy link

xandymp commented Mar 6, 2018

Just because I had a Keeper with IV 6/6 and CP 2970.
Guess I'll need to start over and lookout for the way I use the bot.

@xandymp
Copy link

xandymp commented Mar 6, 2018

I created a new account and after 20min I got this message
error: Error: Error from server: 412 - Precondition Failed at Client.call (C:\snapshot\dracowalker\node_modules\draconode\bin\index.js:143:19) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7)
error: __type=FServiceError, args=[AutoBySuspicion], cause=USER_BANNED

@nocomp
Copy link
Author

nocomp commented Mar 7, 2018

maybe since they changed api bottting is flagged.
i ll try with new account

@nocomp
Copy link
Author

nocomp commented Mar 7, 2018

3:19)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
00:17:04 - error: __type=FServiceError, args=[AutoBySuspicion], cause=USER_BANNED
00:17:04 - error: Too much errors,

it s official now , botting is flagged :'(

i guess last update changed something

@niicojs
Copy link
Contributor

niicojs commented Mar 7, 2018

After how many time do you see that for a new account?

@nocomp
Copy link
Author

nocomp commented Mar 7, 2018

10 min

@niicojs niicojs changed the title Preconditions failed Account getting banned Mar 7, 2018
@niicojs
Copy link
Contributor

niicojs commented Mar 7, 2018

could you test last version?

@nocomp
Copy link
Author

nocomp commented Mar 7, 2018

I ve used last linux64 released got banned after 10 min

@niicojs
Copy link
Contributor

niicojs commented Mar 9, 2018

I published a new dev version if you have an account to spare

@nocomp
Copy link
Author

nocomp commented Mar 9, 2018

oki i ll try this evening
thxx a lot

@nocomp
Copy link
Author

nocomp commented Mar 9, 2018

can t download https://ci.appveyor.com/api/buildjobs/vik90ndml95d856d/artifacts/dist%2Fdracowalker-win-x64.exe it says failed ntwork error

always get these error on this host

@niicojs
Copy link
Contributor

niicojs commented Mar 9, 2018

appveyor does that something, you just have to wait and keep trying

@nocomp
Copy link
Author

nocomp commented Mar 9, 2018

ok

@nocomp
Copy link
Author

nocomp commented Mar 9, 2018

running since 20 mins, logs so far
PS E:\dracowalker> .\draco.exe .\data\config.yaml

16:47:18 - info: App starting...
16:47:18 - info: Launched from binary, version dev-1.0.74
16:47:30 - info: Go to http://ui.dracoapi.ml/ for ui
16:47:33 - info: Client started...
16:48:13 - info: Stop spun!
16:48:50 - info: Potty caught!
16:51:04 - info: Stop spun!
16:51:56 - error:  RequestError: Error: connect ETIMEDOUT 104.20.230.58:443
    at new RequestError (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\errors.js:14:15)
    at Request.module.exports.plumbing.callback (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\plumbing.js:87:29)
    at Request.RP$callback [as _callback] (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\plumbing.js:46:31)
    at Request.init.self.callback (C:\snapshot\dracowalker\node_modules\request\request.js:186:22)
    at Request.emit (events.js:159:13)
    at Request.onRequestError (C:\snapshot\dracowalker\node_modules\request\request.js:878:8)
    at ClientRequest.emit (events.js:159:13)
    at TLSSocket.socketErrorListener (_http_client.js:389:9)
    at TLSSocket.emit (events.js:159:13)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
16:52:01 - error:  RequestError: Error: connect ETIMEDOUT 104.20.230.58:443
    at new RequestError (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\errors.js:14:15)
    at Request.module.exports.plumbing.callback (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\plumbing.js:87:29)
    at Request.RP$callback [as _callback] (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\plumbing.js:46:31)
    at Request.init.self.callback (C:\snapshot\dracowalker\node_modules\request\request.js:186:22)
    at Request.emit (events.js:159:13)
    at Request.onRequestError (C:\snapshot\dracowalker\node_modules\request\request.js:878:8)
    at ClientRequest.emit (events.js:159:13)
    at TLSSocket.socketErrorListener (_http_client.js:389:9)
    at TLSSocket.emit (events.js:159:13)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
16:55:29 - info: Stop spun!
16:55:35 - info: Berrydillo caught!
16:55:41 - info: Start hatching a 5km egg.
16:55:51 - info: Stop spun!
16:56:25 - info: Stop spun!
16:56:31 - info: Potty caught!
16:56:47 - info: Stop spun!
16:58:39 - info: Potty caught!
17:00:02 - info: Potty caught!
17:01:12 - info: Rabby caught!
17:02:17 - info: Chest found!
17:04:03 - info: Stop spun!

@nocomp
Copy link
Author

nocomp commented Mar 9, 2018

after 1h15 it frozed, no error log, ctrl c and resart, so far so good

@nocomp
Copy link
Author

nocomp commented Mar 9, 2018

hmm gets frozen again, need to restart it, weird

@niicojs
Copy link
Contributor

niicojs commented Mar 9, 2018

frozen how?

@nocomp
Copy link
Author

nocomp commented Mar 10, 2018

peg not moving, no more action log like creature caught or stop spun.
just checked now it has work almost all nite froze at 5 am

@nocomp
Copy link
Author

nocomp commented Mar 10, 2018

other log just happening now

08:33:54 - error:  RequestError: Error: connect ETIMEDOUT 104.20.230.58:443
    at new RequestError (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\errors.js:14:15)
    at Request.module.exports.plumbing.callback (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\plumbing.js:87:29)
    at Request.RP$callback [as _callback] (C:\snapshot\dracowalker\node_modules\request-promise-core\lib\plumbing.js:46:31)
    at Request.init.self.callback (C:\snapshot\dracowalker\node_modules\request\request.js:186:22)
    at Request.emit (events.js:159:13)
    at Request.onRequestError (C:\snapshot\dracowalker\node_modules\request\request.js:878:8)
    at ClientRequest.emit (events.js:159:13)
    at TLSSocket.socketErrorListener (_http_client.js:389:9)
    at TLSSocket.emit (events.js:159:13)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

@niicojs
Copy link
Contributor

niicojs commented Mar 10, 2018

the last one is a network issue on your side (or on your proxy side).
I'll think about the frozen thing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants