To answer your first reply, thats completely true, but the only way the bot stays online is from requests by the roblox server, so unfortunately even if it was sql you’d have the same issue of the bot not being online.
To the second reply, those numbers are from the api limits by the glitch server, not roblox. Since the glitch server has a tighter call limit, the roblox servers have to abide by the node’s limits, which is why I made the anti-API exhaust.
To the third reply, the way it works is roblox sends a request to the server and if there is any bans waiting to be processed the node will send back the bans via response json, the response from the roblox server is sent via headers in the initial get request, which is why it takes a few seconds for the bot to reply.
You bring fair points to my attention though and its appreciated.
How would this work? im using your script, but how will this reachh the place? you dont have anything in the code saying that it would actually go to the place except for the liveapp in the script
Will there be more implementations to the default script in the bot coding portion?
E.X: Kicking Players, When A User Gets Banned It Kicks Them Rather Than Waiting On Them To Leave, And Making It Easier For Developers To Add Their Own Roblox Code And Commands Allowing Users To Do All Kinds Of Crazy Stuff To Users From Discord.
Just some extra ideas, although kicking and ban kick would be the best. I would love to see better tutorial recourses for new developers to make their own commands and functions through the bot with ease. Thank you for the contribution and I love the thing itself.
Not quite. Glitch did change their system to make it so you only have 1000 project hours a month without the paid version, but thats more than enough to keep a bot online 24/7 for an entire month as there is only around 730 hours a month.
The bot is kept online by the Roblox servers, as long as there is a Roblox server online the glitch app will stay online too. I developed this system to ensure the bot stays online without needing to pay for the service. This is done without using any weird tricks such as self pings.
The way this works is glitch apps come online once they receive a packet from an external server. The server proceeds to stay online until it hears no more packets, then after 5 minutes(?) it will turn back off. Since the system is reliant on getting data from Roblox’s servers, the external server pinging the glitch one is Roblox.