Contact ScriptsRBX

Three addresses, each for one kind of mail. Using the right one is the difference between an answer today and an answer after the queue clears — takedowns and credit fixes are handled first, broken script reports next, everything else after.

Which address

• Broken scripts and general questions: support@scriptsrbx.com
• Submitting a script you wrote or found: scripts@scriptsrbx.com
• Credits, takedowns, copyright and business: contact@scriptsrbx.com

Reporting a broken script

These are the most useful mail the site gets, and they get acted on before anything else that is not a takedown. To be actionable first time, include:

1. The post link — the page on this site, not the loader URL.
2. Your executor and, if you know it, its version. Scripts are tested here on Delta; a script that works on one executor and not another is a real report, but a different one.
3. What actually happened. Nothing loads, the menu opens but a feature does nothing, an error message — paste the exact text if there is one.

If the developer has already patched it, the post gets updated to the new loader. If the script is dead, the post gets marked as such rather than left to waste the next reader’s time. Either way you will not hear “works for me” without it having been run in-game again.

One shortcut worth knowing: the developer’s Discord linked on each post usually has the fix before this site does. For a game that updated today, that is the faster route.

Credits and takedowns

If a script of yours is posted here with the wrong credit, in an outdated form, or you would rather it were not here at all, write to contact@scriptsrbx.com with a link to the post and something showing it is yours — a Discord server, a GitHub account, an earlier release under your name. Credit corrections and removals are handled before anything else on the list.

For formal copyright notices and counter-notices, the DMCA & Trademark page sets out exactly what a complete notice contains. An email that meets those points is acted on as a takedown; one that does not is still read, and usually still acted on.

Submitting a script

Scripts from readers are accepted on the same terms as everything else here: it has to work, it has to be safe, and it goes through the same checks — run in-game on Delta, loader read at the source, key system noted — before it appears. Send scripts@scriptsrbx.com:

• the game it is for, with the Roblox link;
• the loader, as plain text — not a shortener, not a locked paste;
• whether it needs a key;
• your Discord or GitHub, if you want it credited to you.

Anything wrapped in a link shortener or an ad locker is not looked at. The whole point of this site is that the loader sits in plain text on the page.

Business and advertising

Sponsorship, advertising and anything commercial goes to contact@scriptsrbx.com. The site does not sell placements inside posts and does not accept payment to list a script — every script here is on the page because it passed the checks, and that is worth more than any one deal.

Community

For day-to-day script updates and questions, the Discord server is where the conversation happens, and new script showcases go up on the YouTube channel. Neither is a support queue — a broken script report sent by email is tracked; one dropped in a Discord channel may not be.

What to expect

ScriptsRBX is run by one person, and this is not a company with a support desk. Mail is read daily. Takedown and credit requests are acted on as soon as they are read. Broken script reports are re-tested in-game before a reply, so those take as long as that takes. Everything else is answered in turn. If you have not heard back in a week on something that matters, send it again — it is far more likely to have been missed than ignored.

For what this site is and how scripts are checked before they go up, see the About page.