Script Testing Policy
This policy explains what a "BobloScript Review" is, what each review result means, and — just as importantly — what it does not mean. It applies to any script page that shows a "BobloScript Review" block. Pages without that block have not been tested by our team; they are ordinary user-generated content under the Content Policy. By using BobloScript, you agree to this Script Testing Policy, the Editorial Policy, and the Disclaimer.
Last updated: August 20, 20261. What "Tested" means
A review records that a member of the BobloScript team ran the script, on the listed platform and executor, on the review date shown. It is a record of one test, not a continuous guarantee. The Functions list on the script page describes what the publisher says the script can do. The review describes what happened when we tested it: how many of those listed features we checked, whether any of them failed, and any notes from that session.
We deliberately avoid the word "Safe": most scripts on BobloScript load code from an external source the publisher controls, and that source can change at any time after we test it — including a minute later.
2. Review results
- Working during our test — the listed features we checked behaved as described at the time of testing. "Test coverage" shows how many of the script's listed functions we actually ran. Unchecked functions were not part of this test.
- Partially working during our test — some of the features we checked worked, and at least one did not. Failed features are named under "Issues found" because that is new information; working features are not listed again (they already appear under Functions).
- Broken during our test — the script did not function as described at the time of testing.
- Unable to verify — we could not reach a conclusion (for example, the source could not be reviewed, or the required game state could not be reproduced).
3. Scope of a review
A review only covers the listed features that were checked in that test, as shown under "Test coverage." It does not cover functions that were not checked, long-running or AFK use, every Roblox executor, every platform, or the script's behavior after a future Roblox or game update. "Known limitations" on the review block, when present, lists what we know we did not check. "Test notes," when present, record what we observed during the session — they are not a restatement of the Functions list.
4. External loaders and source changes
Many scripts on BobloScript load code from an external URL at runtime. A review reflects the source we observed at review time. If the publisher or a third party changes what that URL serves after our review, the script can behave differently from what we tested — including becoming broken or unsafe — without BobloScript's knowledge. We are working on automatic detection of this (comparing the loader source's hash over time); until that ships, a review's age is the best signal of how current it is — check the review date.
5. What a review is not
A review is not a safety certification, a malware scan, a legal guarantee, or a promise that the script will keep working. It does not mean BobloScript endorses the script's publisher or the linked game. It does not replace your own judgment about whether to run third-party code. See the Disclaimer for the full limitation of liability.
6. Re-testing and corrections
Reviews are not silently edited. If a script is re-tested, the new result is recorded as a new review and shown as the current one; the script's page history keeps a record that an earlier test happened. If you believe a review is inaccurate or outdated, contact support@bobloscript.com with the script URL.
7. Contact
For questions about how a script was tested, or to request re-testing, contact:
Email: support@bobloscript.com