sentanos / roblox-js

!!!THIS PROJECT IS NO LONGER MAINTAINED!!! Execute ROBLOX website actions in node.js
MIT License
45 stars 45 forks source link

"Message failed, make sure you are logged in" #30

Closed Vritix closed 7 years ago

Vritix commented 7 years ago

This error keeps popping up every time I try to send a message, and yes I am logged in. I've made sure I was logged in by making the function wait until I was sure the bot was logged in and logging to the console, but it's still giving me this error.

Any help?

sentanos commented 7 years ago

Please put the following in the exact same place you are sending the message:

rbx.getCurrentUser().then(console.log);

To make absolutely certain you are logged in and using the correct jar file.

Vritix commented 7 years ago

Yep it's logged in. It's prints the correct information.

I added you on skype + discord so we can talk easier.

sentanos commented 7 years ago

Alright replace your message.js file with this and run message again. Tell me what it outputs.

Vritix commented 7 years ago

{ success: false, shortMessage: null, message: 'Captcha' } Also same, error : Message failed, make sure your are logged in.

sentanos commented 7 years ago

Yeah it looks like ROBLOX is requiring you to do a captcha challenge. I will say it was an issue that the correct error wasn't being thrown (it should tell you that captcha is the problem), but other than that there is no way to circumvent captcha restrictions and it cannot be a problem with ROBLOX.

This is related to #31 on roblox-js-server, it seems like ROBLOX is enforcing captcha for messages now, though it may be limited to accounts made after a certain date (as they did with the forums), or possibly from accounts that have been detected to be sending a lot of messages.

sentanos commented 7 years ago

I will close this once I fix the error issue.

Vritix commented 7 years ago

Alright, thanks for the information.

Vritix commented 7 years ago

SOLUTION:

After some testing different accounts I realized the main issue was that my account was too new. After realizing this I logged into an account I made in 2014 and it worked perfectly after that.

Hope this helps anyone! :)