This is really cool! I wonder if this can be used to give special perks in-game to Nitro boosters.
EDIT: just realized this might be against Roblox’s TOS lol. Still, amazing project nonetheless! ^^
2 Likes
Well it’s already possible using the function CheckForUserRole() as it returns true if the user has a role so just copy the id of the role you want to check for. Also if i’m correct using this for providing perks for nitro booster is against the tos
1 Like
Its simple and all, don’t get me wrong if it works it works, but maybe add a cooldown for an x amount of requests sent. Good work though
2 Likes
Thanks for your feedback. After fixing the current issue i will be working on the improvements and this was already in my mind but i didn’t list it.
1 Like
The issue has almost been fixed. The service should be back up online tomorrow.
Question. How will we know whether the user is on the server or not? Sorry if this was already been answered before, just out of curiosity. Nonetheless, awesome creation.
Also, when checking for the user (if in the server) method, do you mean their UserId?
The system checks for a user in the server with a nickname equal to the passed username. The method is a parameter needed for the system to run the correct function.
when i try the /view-token it returns “This interaction failed”
The bot is offline with all the system I was fixing an issue
Issue fixed
The issue that made the system being down for this time has been fixed.
What was the issue?
The bot was answering to commands 2 times and there was a little security problem. Everything has been solved.
You can invite the bot again as i made it leave every server to correctly sync with the database.
Database has been reset. Run the /setup command to set the system up correctly. Tokens will now be send in the channel that is created with the setup so if you demote a user from his charge of server manager he will not be able to look at the token anymore as before the person was able to look at it in DM.
If you downloaded the module you will need to redownload it again as it has been changed. It is now suggested to use the module to make requests as now the bot has 2 hosts in case one is down. The module automatically refers to the secondary host if the first one is unavailable.
Fixed right in time for Christmas, start awarding your players!
Changelog
Updates and news
After over one month and a half this system exited its beta status.
API rate limit
Rate limit system has been implemented. You can now make only 100 requests/60 seconds, basic plan is the only current one, others will be added in the next few days.
Exceeding the rate limit will make the experience banned from the API for 3 minutes and every request made during that period of time will receive an HTTP error 429 (Too many requests).
Requests are temporarily stored until the next minute of the hour comes.
Exceeding the rate limit too many times will result in all the experiences owned by the creator of the one which exceeded getting permanently banned from the API in the future.
API wrapper
The old API wrapper is half deprecated and it won’t really work without editing it. You can get the new one here. If you already own it download it again or download it here
N-RTD API Wrapper.lua (1.4 KB).
API’s changes
The API does not support requests sending parameters with wrong type anymore, doing so will result in HTTP error 400 (Bad request).
Host
This service is not hosted on Heroku anymore. Read more in the support server.
Status page
You can now monitor systems’ status here.
Upcoming features
In the next months this service will have a website which is already being worked on. Sessions handling only is left. The website will have a dashboard where you will be able to configure the settings for your server/experience. These includes, as it has been asked a lot, checking for a user with the option nickname is equal or nickname is equal or contains.
Downtimes
If you used this system for a while you probably know that there have been several downtimes, using the new system seems to have decreased these.
Code changes
Moved from CommonJS into ES6 modules;
Refactored code;
Splitted the bot and the API into separate projects hosted on different servers (same host) which should lower the ping.
More info in the support server.
Submit issues you encounter here.
1 Like
This seems useful, however does this require a bot? If not, how do I retrieve messages?
Yes it does and the bot is linked in the first post, it acts as a proxy between roblox and discord.
Is there any way we can host the bot ourselves? I just wanted to implement it into my server’s custom bot I made. (node.js)
No there is no way you can host it yourself currently, I may try to add it in the future after I finish the sessions handling for the dashboard
1 Like
Also how would you host it bry yourself? Do you mean making your bot responding to the commands instead of mine? If you want you can submit it as a feature request in the support server.
I just wanted like a GitHub repo of the command code, and I could input the code into my own command handler and such, and download all the required packages.
Changelog
Updates and news
The system got a website which is available here. The website has a dashboard where you can manage the service for your server and verify your account.
From now on you can change the API’s check method which means that if it is set to nickname is qual or contains the system will not check for a user that has the nickname equal to the passed username but for a user that has a nickaname containing the passed username this can be useful if you have people with nicknames like: Mod | NinjaFurfante07.
You will need to log in with your Discord account in order to access the dashboard.
Bot changelog
Updates and news
You can now verify your account by using the /verify command.
Upcoming changes to the API
Upcoming changes to API
Later this month the API will receive an important update. From that date on requests to the API will require an API key which you will be able to obtain on your developer page on the website.
You will be notified in the support server (the Discord server) 7 days before the change goes live. Once the update is up requests that provide an invalid API key will be rejected. This will help blocking access to the API to banned users.
Also comment below features you would like to see.