TestBot.html throwing an error

tailuge / bot-o-tron

Try out lichess' bot interface

https://bot-o-tron.onrender.com/

GNU General Public License v3.0

39 stars 24 forks source link

TestBot.html throwing an error #27

Open ajm2017 opened 3 years ago

ajm2017 commented 3 years ago

https://tailuge.github.io/bot-o-tron/dist/testBot.html

Hello - I was testing my new token and I am getting an error in Chrome. Console says:

Uncaught (in promise) TypeError: this.api.accountInfo is not a function at t.exports.start (library.js:2) at start (testBot.html:69) at HTMLButtonElement.onclick (testBot.html:76)

I wrote my own engine in JS and am trying to figure out how to make a bot account at lichess; I was very interested in seeing your API implementation!

Ty!!

tailuge commented 3 years ago

Hi its designed to work in node not chrome.

good luck

On Wednesday, 3 November 2021, 03:26:36 GMT, ajm2017 @.***> wrote:

https://tailuge.github.io/bot-o-tron/dist/testBot.html

Hello - I was testing my new token and I am getting an error in Chrome. Console says:

Uncaught (in promise) TypeError: this.api.accountInfo is not a function at t.exports.start (library.js:2) at start (testBot.html:69) at HTMLButtonElement.onclick (testBot.html:76)

I wrote my own engine in JS and am trying to figure out how to make a bot account at lichess; I was very interested in seeing your API implementation!

Ty!!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

ajm2017 commented 3 years ago

Ok, I see. I've got everything installed in node - I'm using my token and the chess.js engine in your package (I haven't subbed my engine in yet) and the server is listening on 5000. But, the bot account doesn't seem to be accepting any challenges and I don't see anything coming through on the server. I have my firewall off and port forwarding on my router to 5000 on my machine.

Sry to bug you :) -- thx so much for any help!!

ajm2017 commented 3 years ago

I determined that "setx API_TOKEN xxxxxxxxxx" was not accessible by "process.env.API_TOKEN" so I just hard coded my token and - IT's WORKING! :)

ajm2017 commented 3 years ago

I found this! https://stackoverflow.com/questions/35347451/why-is-setx-path-not-working

the setx var is not accessible in the current command window. But in subsequent windows it's available.

tailuge commented 3 years ago

Nicely worked out. I'm not used to windows

Thanks.

On Thursday, 4 November 2021, 02:41:28 GMT, ajm2017 @.***> wrote:

I found this! https://stackoverflow.com/questions/35347451/why-is-setx-path-not-working

the setx var is not accessible in the current command window. But in subsequent windows it's available.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android .