Open yuyik opened 3 years ago
Apparently it's due to a successive http network call. Just put a : await this.waitFor(1000) before the line 'raid/dig/${slotIndex}'
great, can you open PR for this?
From: Navid EMAD notifications@github.com Sent: Saturday, December 19, 2020 1:39 PM To: samuraitruong/coinmaster coinmaster@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [samuraitruong/coinmaster] Error 511 Network Authentication Required https://vik-game.moonactive.net/api/v1 /users/ror48__xxxxxxxxxxxx/raid/dig/3 (#39)
Apparently it's due to a successive http network call. Just put a : await this.waitFor(1000) before the line 'raid/dig/${slotIndex}'
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/samuraitruong/coinmaster/issues/39#issuecomment-748407395, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJA3IRAPBVVTBFXIOZKA4TSVQG75ANCNFSM4USFTJTQ.
I think it's due to the fact they were trying to fix an exploit on raid which makes people digging unlimited times when they were spamming one hole.
I think it's due to the fact they were trying to fix an exploit on raid which makes people digging unlimited times when they were spamming one hole.
can use waitFor time < 1000 ?
as I remember, this error usually related to too many requests in a short time.
From: T0NZ notifications@github.com Sent: Sunday, January 10, 2021 7:53 PM To: samuraitruong/coinmaster coinmaster@noreply.github.com Cc: Truong Nguyen samuraitruong@hotmail.com; Comment comment@noreply.github.com Subject: Re: [samuraitruong/coinmaster] Error 511 Network Authentication Required https://vik-game.moonactive.net/api/v1 /users/ror48__xxxxxxxxxxxx/raid/dig/3 (#39)
I think it's due to the fact they were trying to fix an exploit on raid which makes people digging unlimited times when they were spamming one hole.
can use waitFor time < 1000 ?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/samuraitruong/coinmaster/issues/39#issuecomment-757440889, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJA3ISNKEOUEQN2N6UCYQLSZFTIBANCNFSM4USFTJTQ.
as I remember, this error usually related to too many requests in a short time. … ____ From: T0NZ notifications@github.com Sent: Sunday, January 10, 2021 7:53 PM To: samuraitruong/coinmaster coinmaster@noreply.github.com Cc: Truong Nguyen samuraitruong@hotmail.com; Comment comment@noreply.github.com Subject: Re: [samuraitruong/coinmaster] Error 511 Network Authentication Required https://vik-game.moonactive.net/api/v1 /users/ror48__xxxxxxxxxxxx/raid/dig/3 (#39) I think it's due to the fact they were trying to fix an exploit on raid which makes people digging unlimited times when they were spamming one hole. can use waitFor time < 1000 ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#39 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJA3ISNKEOUEQN2N6UCYQLSZFTIBANCNFSM4USFTJTQ.
ok
Error 511 Network Authentication Required https://vik-game.moonactive.net/api/v1 /users/ror48__xxxxxxxxxxxx/raid/dig/3 { err: 'Invalid request', hash: 'b6c998b6a0c73f767fe6732c49a779fb' } (node:2060) UnhandledPromiseRejectionWarning: TypeError: Cannot destructure prop erty 'res' of 'response' as it is null. at CoinMaster.raid (C:\coinmaster\coinmaster.js:1104:9) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async CoinMaster.play (C:\coinmaster\coinmaster.js:896:17) at async C:\coinmaster\index.js:116:21 (node:2060) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termina te the node process on unhandled promise rejection, use the CLI flag
--unhandle d-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejectio ns_mode). (rejection id: 3) (node:2060) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre cated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.