Redz Hub script compatibility: our 26 October 2026 check#
Redz Hub’s current loader routes to Blox Fruits and Meme Sea. A routing entry identifies the file selected for a game; the destination check tells you what that file contained. We fetch loaders as text and never run them, so a status is not proof a script works.
Our findings date to 26 October 2026. We read the global loader in the upstream tlredz/Scripts repository to map its game routes, then checked the destination files. The README tells you which games the developer names; the file checks show what was actually available behind those names.
The distinction matters most for Blox Fruits: a named game can remain in the routing table while its destination contains zero bytes. A broad supported-games label would hide that difference. The Redz Hub overview explains the loader and its source. Use this page when you want to compare a specific game or device claim against the files we checked.
Read the game list alongside the destination status: a README mention, a route and a downloaded file answer three different questions.
Which games appear in the current routing table?#
Blox Fruits and Meme Sea are the only games in the current upstream routing table. Grow a Garden, 99 Nights in the Forest, Fisch, Blade Ball, Brookhaven and RIVALS have no entry in that loader at our 26 October 2026 check.
| Game or claim | Evidence | Finding at 26 October 2026 | Compatibility limit |
|---|---|---|---|
| Blox Fruits named in README | Developer claim | README names Blox Fruits | A declaration does not establish runtime behavior |
| Blox Fruits loader path | Routing table | GameId 994732206 targets Games/BloxFruits.luau | Standard target was empty; status: dead |
| Meme Sea named in README | Developer claim | README names Meme Sea | A declaration does not establish runtime behavior |
| Meme Sea loader path | Routing table | PlaceId 10260193230 targets Games/MemeSea.luau | Obfuscated target; status: loader reachable |
| Grow a Garden | None in current upstream | No route; a look-alike adds one | Look-alike relationship is unverified |
| 99 Nights in the Forest | None | No current routing entry | No upstream compatibility evidence |
| Fisch | None | No current routing entry | No upstream compatibility evidence |
| Blade Ball | None in current upstream | No route; historical loader returned HTTP 404 | Historical loader status: dead |
| Brookhaven | None | No current routing entry | No upstream compatibility evidence |
| RIVALS | None | No current routing entry | No upstream compatibility evidence |
“None” in the Evidence column means we found no route in the current tlredz/Scripts loader. Other files may use the Redz Hub name, so check the repository owner before comparing claims. A missing route here tells you about this upstream loader, not every historical file carrying the same name.
The README names the same two games as the loader, so the declared scope and observed routing scope align. The destination files differ, however, which is why the Blox Fruits and Meme Sea findings need separate explanations.
Blox Fruits and Meme Sea destination evidence#
Blox Fruits has an upstream routing entry, but its standard target was empty. Meme Sea has an upstream routing entry and a fetched obfuscated target. For Blox Fruits, the selected file had no code. For Meme Sea, a file was present but its code was concealed by obfuscation.
The current global loader was readable and returned HTTP 200 with 3,106 bytes in our 26 October 2026 fetch. Reading that small file reveals routing decisions, settings forwarding and error handling. Start with the route, then open the exact filename it selects; stopping at main.luau misses the destination’s condition.
Why does Blox Fruits have a route but an empty target?#
The reason the Blox Fruits file was empty is unknown. Our check showed that GameId 994732206 selected Games/BloxFruits.luau, and that standard destination contained zero bytes. The global loader therefore had nothing in that file to run for Blox Fruits at our 26 October 2026 check.
The Blox Fruits target should be evaluated independently of surrounding repository content. Readable helper modules, translation resources and a README declaration do not populate an empty destination. A repository can contain Blox Fruits-related material while the loader’s selected entry file still lacks code.
The loader also includes an alternate BLOX-FRUITS-BETA.lua path when BETA_VERSION is set. Our check did not establish that destination’s contents or behavior. A beta filename alone gives you no reason to treat the branch as a fix for the empty standard file. Broader game-specific listings belong in the Blox Fruits script collection, where each entry needs its own source and status.
Meme Sea target and inspection limits#
The Meme Sea target was present and obfuscated at our check. The routing table matches PlaceId 10260193230 to Games/MemeSea.luau. The fetched target measured 814,514 bytes and was obfuscated, so the status vocabulary for that destination is loader reachable.
The Meme Sea target cannot be described as fully inspected merely because the routing file is readable. Obfuscation limits what the text review can establish about the downloaded payload. File size also cannot establish feature completeness, interface behavior or device support.
Keep four details together when comparing a Meme Sea claim: repository owner, PlaceId, selected file and file status. A claim that names only the game leaves out the source you need to assess it. The other game searches below have a more basic problem: no route in this loader.
Grow a Garden and other game-name searches#
Grow a Garden, 99 Nights, Fisch, Blade Ball, Brookhaven and RIVALS have no route in the current loader. Search results may point to historical loaders or a different repository. Check which source a page names before assuming its game list describes tlredz/Scripts.
Does Redz Hub support Grow a Garden?#
Current upstream support for Grow a Garden is not established. The tlredz/Scripts routing table has no Grow a Garden entry. A different repository, newredzv3/Scripts, adds GameId 10200395747 targeting Grow-a-garden.luau, but its relationship to the Redz developer is unverified.
The same look-alike adds a VoxSeas.luau route for PlaceId 104067066727140. Structural similarity between two loaders does not prove common ownership, maintenance or identical destination behavior. The look-alike is not offered as copyable by redzhub.dev, and its extra routes must not be imported into the current upstream’s supported-games list.
Readers researching the game rather than the Redz name can use the Grow a Garden script collection. Compare each listing’s source and status there. The collection covers the game’s indexed scripts; inclusion does not establish a connection to the Redz Hub developer.
Is there current support for 99 Nights or Fisch?#
No current upstream route is documented for 99 Nights in the Forest or Fisch. Our check found no route for either game; it did not identify a hidden version with extra support. Neither game should be added to the upstream compatibility list based on a search phrase or a page title.
The 99 Nights in the Forest script collection addresses that game’s listings independently. The Fisch script collection provides the equivalent game-specific destination. Use those pages to compare individual sources and their statuses. Keep the source attached to each entry: a script listed for Fisch or 99 Nights does not automatically belong to Redz Hub.
A search for “Redz Hub 99 Nights” therefore has a direct answer: no route in the checked upstream loader. That answer can coexist with a separate collection for the game without implying that the collection supplies a missing Redz build.
Blade Ball, Brookhaven and RIVALS evidence#
Blade Ball, Brookhaven and RIVALS have no current upstream route. Blade Ball also has a specific historical fetch result: the REDzHUB/BladeBall loader URL returned HTTP 404 at our 26 October 2026 check, making that historical loader dead.
The historical Blade Ball result should not be generalized into an invented HTTP result for Brookhaven or RIVALS. Our check established their missing current routes but did not include a corresponding raw-loader fetch for each name. For Brookhaven and RIVALS, the finding is “no current route.” For the historical Blade Ball URL, the finding also includes a specific HTTP response.
Our 26 October 2026 review found competitor pages promoting other games through old REDzHUB loaders that returned HTTP 404. Seven of ten distinct Redz Hub loader URLs in that competitor sample were dead. That sample explains why copied compatibility lists need source verification; it is not a measurement of every Redz-named URL on the internet.
Game identity is only one compatibility condition. A valid route would still leave the device and executor questions unresolved.
Mobile and PC compatibility depend on executor APIs#
Redz Hub mobile and Redz Hub PC execution compatibility remain unverified by redzhub.dev. The readable loader references identifyexecutor and conditionally uses queue_on_teleport. Those are third-party executor APIs in this loader’s environment, so a device label alone cannot establish that the required environment exists or behaves as expected.
The loader queues itself after teleport only if queue_on_teleport is exposed. Its error reporting uses identifyexecutor to include an executor name alongside errors. Observing those source references explains a dependency; it does not certify an executor, operating system or client build.
| Device or platform question | Evidence | Editorial conclusion |
|---|---|---|
| Android phone or tablet | No device execution check | Unknown; mobile compatibility is unverified |
| iPhone or iPad | No device execution check | Unknown; iOS compatibility is unverified |
| Windows PC | Executor API references, no execution check | Unknown; Windows client uses Roblox anti-cheat |
| macOS computer | No device execution check | Unknown; desktop wording does not establish support |
| Touch interface or keyboard controls | No interface interaction check | Layout and input behavior are unverified |
A mobile/PC label leaves several questions unanswered. Does the claim identify Android, iOS, Windows or macOS? Does it describe touch controls, a translation setting or actual execution? Compare the wording with the device table before drawing a conclusion. A phone-shaped graphic tells you nothing about the loader’s API dependencies.
Roblox’s Windows client uses anti-cheat. Roblox’s anti-cheat guidance also explains that modified clients and software that changes Roblox violate its rules and can lead to account restrictions. The existence of anti-cheat is policy and platform context, not a basis for predicting detection or suggesting a bypass.
Using third-party scripts or executors to exploit breaks Roblox’s Terms of Use; accounts can be banned. Roblox’s cheating and exploiting policy states that exploiting violates those terms. We fetch loaders as text and never run them, so a status is not proof a script works. redzhub.dev does not recommend executors; neither a mobile label nor a reachable file removes the account risk.
For players and parents reviewing a claim together, the useful next step is to read the source chain without executing its code.
How to read a compatibility claim without executing code#
A compatibility claim can be checked by reading the repository, route and destination file as text. Follow the source chain in that order, and write down what each step establishes. Keeping the owner, filename, response and date together makes it easier to spot a page that mixes findings from different loaders.
- Identify the repository. Check the owner and path named by the loader against the upstream documented here. Match both the owner and repository name, not just the filename. Our review found unrelated listings using “Redz Hub” in their titles, so a title match alone cannot identify the maintainer.
- Read the routing condition. Record the specific GameId or PlaceId and destination filename from the loader text. Look for the requested game’s actual routing entry. Keep the repository name beside it so you do not accidentally carry newredzv3’s extra routes into tlredz’s game list because the loaders look similar.
- Inspect the selected destination as text. Distinguish an empty response, readable content and obfuscated content. Write down the selected filename, response state and check date together. An HTTP 200 on main.luau says nothing about whether Games/BloxFruits.luau contains code; those are separate files and require separate checks.
- Keep platform claims separate. Record executor API dependencies without naming a device as compatible. Identify exactly what the source shows before accepting a platform claim. A desktop screenshot, phone-shaped graphic or mobile label does not resolve whether identifyexecutor or queue_on_teleport is available in that environment.
- Preserve uncertainty in the conclusion. Report only the finding the chain supports. Use specific wording: no current route, empty target or obfuscated target. Attach the check date to that finding. Avoid turning one file’s condition into a verdict about every historical loader or future repository change.
Source ownership disputes, mirrors and account history require a separate identity review. The Redz Hub source guide covers that adjacent question so compatibility findings do not depend on an assumed relationship between similarly named accounts.
Before reusing a compatibility claim, compare its check date and repository with the source being discussed now. A dated finding is useful only when you keep that context attached.
Limits of the Redz Hub script compatibility findings#
Redz Hub script compatibility findings on this page describe text evidence recorded on 26 October 2026. The repository can change after that check because the global loader downloads destination code at runtime. An unchanged loader line therefore cannot establish an unchanged payload, game list or device outcome.
The dated findings give you a concrete comparison point: two routing entries, an empty standard Blox Fruits target and an obfuscated Meme Sea target. For a later update claim, compare those exact destinations again. Interface quality, feature behavior, platform support and the reason for the empty file remain unknown.
The most useful compatibility summary keeps three statements separate: the developer names Blox Fruits and Meme Sea; the loader routes to those games; the fetched destinations have different states. Grow a Garden belongs to an unverified look-alike claim, while the other requested games lack current upstream routes. Future compatibility claims should be assessed against the same source, route and destination distinctions.