Editorial Policy — How RageInject Reviews Content

Core Principles

RageInject publishes content based on three principles:

1. Say what we can verify. If we have not tested something, we say so. If a status is unknown, we mark it Unknown.
2. Say what we cannot verify. External scripts are clearly labeled. We do not pretend to have reviewed what we have not reviewed.
3. Never invent numbers. We do not publish download counts we cannot measure, ratings we did not collect, or quotes we did not source.

What We Publish

Script Pages

Every script page includes:

• The name of the script and the game it targets
• A description of what the script does
• Execution level and sUNC requirement, if known
• Status (Working, Broken, Detected, Unknown)
• A "Last Reviewed" date
• If hosted: a download link and a published SHA-256 hash
• If external: a link to the original source, with clear labeling

Executor Pages

Every executor page includes:

• The name and platform
• Current status as reported by third-party trackers (Rscripts, ScriptBlox)
• Price tier
• Whether RageInject hosts the file (we do not host executor binaries)
• Ban risk warning

Guides

Guides cite their sources when they make factual claims. Where information comes from public statements by Roblox, third-party trackers or security researchers, we identify the source. Where we do not have a source, we mark the claim as our own observation.

What We Do Not Publish

• Sponsored content. No executor vendor pays for placement. No script author pays for a review.
• Fake reviews. We do not publish ratings, testimonials or user quotes we have not collected from actual users.
• Unverifiable claims. We do not publish numbers, statistics or quotes without a source.
• Speculative malware accusations. When we flag a file or tool as a security concern, we cite the security researcher or public report that documented the concern.
• Ambiguous "best of" lists. When we rank executors, we explain what we ranked them on and disclose the criteria.

Review Process

When we receive a submission or discover a script through public sources:

1. Read the source. If we cannot read the code because it is obfuscated, we either reject it or label it as external.
2. Check for red flags. HTTP requests to unknown domains, requests for credentials, requests for Discord tokens — any of these is grounds for rejection.
3. Compute the hash. For hosted files, we compute the SHA-256 hash ourselves and publish it.
4. Write an original description. Descriptions are written by us, not copied from the script author's README.
5. Set a Last Reviewed date. This date reflects when we last confirmed the page's information is accurate.

Status Labels

Corrections

If you find an error in any page, use the Report button on that page and select "Outdated information." Describe the specific correction and cite your source. We update pages when information changes.

Contact

Editorial questions can be sent through the Contact page.