This page explains the RobxScript workflow for reviewing a script's source, loader, visible functionality and publication information. A specific page's displayed status shows what was recorded for it.
A recorded full review includes the available links and generated code.
A script can execute successfully and still contain behavior that has nothing to do with the features shown to the user. That is why RobxScript does more than check whether a GUI opens.
The source, remote loader and actual in-game behavior are considered together before a script page is published.
Features listed on a RobxScript page are intended to describe the version that was reviewed. We also record useful context such as the developer, update information, key requirements and platform compatibility when available.
The workflow below describes how a submitted or discovered script can be examined for a finished RobxScript page.
The review starts with the script source, developer information and the page where the script was obtained. We check that the source matches the script being submitted and that the publication is not built around an unrelated or misleading download.
In a full review, raw links and remote code locations are checked to confirm that the URL points where expected and that the loadstring is not silently fetching an unrelated payload.
Readable Lua, generated loaders and loadstring targets are reviewed for unexpected behavior. Extra attention is given to hidden remote requests, secondary payloads and code that does not match the advertised script.
Where an in-game test is performed, the script is executed in the Roblox experience it was made for. The test checks whether the GUI loads, whether the main advertised functions work and whether observed behavior matches the description prepared for the post.
Visible functions are compared with the final Features section. Key requirements, mobile support, executor notes and other important limitations are checked so the post describes the script as accurately as possible.
For a recorded full review, the title, game, developer, source link, code, feature list and update information are considered together so the page describes the version reviewed on that date.
The review focuses on the parts of a Roblox script that can change what is actually executed on a user's device.
| Check | What we review | Result |
|---|---|---|
| Source link | Destination, raw endpoint and whether the linked source matches the submitted script. | Source destination check |
| Loadstring | The remote target used by the loader and whether it corresponds to the code being reviewed. | Target reviewed |
| Lua code | Unexpected remote calls, hidden secondary payloads and behavior unrelated to the advertised features. | Manual code review |
| In-game behavior | GUI startup, major advertised functions and obvious unexpected behavior during execution. | Functional test |
| Post information | Game, developer, feature list, key status, compatibility notes and update information. | Publication check |
RobxScript includes utilities for checking URLs and producing consistent Lua/loadstring output while preparing scripts for publication.
Used when working with transformed Lua and testing how prepared code behaves before it is shared.
Creates a clean loader from a reviewed raw URL so the remote target remains explicit and consistent.
Checks the raw source endpoint before it is used in a published loader or script page.
If the source, loader or observed behavior does not make sense, publication can be delayed until the script can be reviewed properly. The goal is for the final page to represent what was actually inspected and tested.
A review is a snapshot of the version available at the time of testing. Third-party scripts, raw files, executors and Roblox experiences can change later. No review can guarantee that a remote script will remain unchanged forever.
RobxScript reviews the source link, loader target and advertised functionality for the version available on the displayed review date. This review is not a permanent guarantee of safety or availability because third-party remote sources, executors and Roblox experiences can change after publication. Check the Last tested date and current source status before using a script.
Where a page has a recorded functional review, the main visible and advertised functions are checked in the relevant Roblox experience and the description is prepared to match what was observed on the displayed review date.
Roblox experiences, executors, remote loaders and script dependencies can change. A script that worked during review can later require an update from its developer.
The script can be held back from publication until the source, loader or behavior can be understood. A working GUI by itself is not enough reason to publish a script.
A script page contains the information and review status available for that specific publication.
