Hello, I have recently created a ranking bot using an updated version of noblox.js, but I am not exactly a pro at this type of stuff, so I have no idea how to account for the fact that every 24 hours, my bot is down due to the fact that the cookie has expired. If anyone knows how this can be fixed, please let me know!
Here is a link to the git repository that I forked:
Is the cookie tied to an account that a human uses? Roblox cookies will expire and change every time certain things are done, like logging in and (maybe) logging out. Consider using a bot account that you do not have to manually log into.
No, the account is not touched at all, and whenever I fetch the cookie it is in an incognito browser and is closed immediately after retrieval.
Is your host restarting every 24 hours? I don’t know if this would cause issues with the bot’s code but it might
It’s hosted on heroku, and to my knowledge, it does not restart.
According to the docs for noblox.js, heroku is not supported and therefore the noblox.js server won’t work either.
Perhaps you could try using bloxy GitHub - affenity/bloxy: Interact with the Roblox website and API
Heroku doesnt support File writing (for noblox’s relog), So it would cause it to fail after 24 hours.
The only issue with bloxy is, There isnt many functions, Most of the time you would have to make HTTP requests directly to Roblox’s api. Even in the dev version its not exactly working, Most of the libs rn are outdated or they relog. It might be ideal for someone to code one that works fully.
Noblox seems to be in the process of discussing the removal of automatic cookie relogging regardless (or making it up to the user), so this may not even be a problem in the future
I’ve had the same issue too in the past, the bot would sometimes die randomly in the night and ROBLOX resetted the cookie, so I have to fix it manually.
Use this, the topic is pretty self-explanatory.
The issue with this topic is that he is using Heroku (that doesnt support file writing) so that wouldn’t work either, the user would have to buy a VPS Such as digitalocean, etc
I’m pretty sure Heroku does restart every 24 hours (even when you pay, there is a difference between a Dyno going to sleep & one restarting). Honestly the real problem here is that he uses Heroku and that is it.
Heroku always causes issues in this line of work from personal experience. I would recommend AWS or DigitalOcean.
All free hosts have catches, so it would be ideal to buy a VPS, (theres many out there) Instead of paying for many hosts for my bots i decided to use a pterodactyl panel, (Which separates 1 normal VPS into multiple slots) Currently Ive got them set at 50-75mb ram for each server (and theres about 60 servers)
(Offline ones are ones that arnt being used)
If your running multiple bots, this might be the way to go. (It has worked out for me and my other developers)
I’ve used glitch for some years and my cookie basically never expired except I made some major changes to my project. Just use uptimerobot to keep the project alive.
Recentlly Glitch has been banning users for hosting them with uptimerobot, So it wouldn’t be be ideal.
(Only had about 7 projects that where up with uptime robot) and i got all my stuff disabled for it.
I will try migrating to digitalocean, thank you for the insight on heroku.
Is the setup self-explanatory or is it something that an intermediate user would have problem setting up?
If so, could you provide a bit of insight since you seem to know what you are doing?
Oh. I didn’t notice that. Well yeah then it’s not that ideal.
I personally havnt used digitalocean since i moved to my own panel, But i would guess it would be easy,
And to stop relogging i ended up making my own lib for it.
Can I get banned for having 1 or 2 bots 24/7?
If they find out about it then yes.