Glitch and Replit both hide environment variables. Besides, the client token is decided based on the connection made from the Roblox side. That means the only place the token is available is in memory, nowhere else. Not even environment variables.
I have removed this post, Sorry about that.
Does onShout grab the current group’s shout? Doesn’t seem to be printing anything
Sorry, I completely didn’t see this! It does not, but I believe you can get that info by the “getGroupInformation” method for groups. The “:onShout” should update in near live time when a group shout is made mid-game.
Seems the bot cookie is constantly invalidating itself seamingly twice a day.
Is there any keep-alive methods in place?
Oh? Are you logging back into the account or logging out or anything? I usually create an account, fetch the cookie, and then close the browser and it doesn’t invalidate.
I’ve had to add a persistent keep-alive that somehow resolved the cookie from expiring on Roblox’s end, nearly after 6 hours of a cookie not having activity, trying to use the cookie again resulted in fails.
Could probably have something to do with the adjusted way Roblox is handling cookies? If this could use a cookie jar file, including the numerious other cookies Roblox has like RBXIDCHECK or _vs, both being marked as ‘secure’ samesite=none could have to do with it?
function BotCookieRefresh() {
request.body={}
console.log(apiRequest("https://users.roblox.com/v1/users/authenticated", request, reply, true));
}
setInterval(BotCookieRefresh, 120000);
Might need to adjust your own apiRequest function with a fourth variable to add the bot cookies to the request also.
Ever since adding this, the bot never ‘{failed:true}’
I know Promise.fromEvent() resolves during sn event so maybe you could use that. If the module doesn’t automatically parent Promise, then I would manually move Promise somewhere in ReplicatedStorage.
Here is more information on Promise.fromEvent().
thanks for the github page btw