GUIDE

Start here.

Four steps to running it, then the answers to everything that commonly goes wrong. If you've never used a script before, read the whole page -- it's short.

loadstring 
loadstring(game:HttpGet("https://rvhub.wtf/loader.lua"))()
SETUP

Running it, start to finish.

  • RV Hub is a script, not an application. An executor is the program that runs it inside Roblox. Without one there is nothing to paste the line into.
  • The executors page covers what they are, what the pricing models mean, and which ones people use on each platform.
  • Install it and confirm it works on its own first. If your executor can't run print("hi"), no script will fix that.
  • Check the games page for what's supported. Each game has its own hub with its own controls.
  • Wait until you're fully loaded in -- character spawned, UI showing -- before running the script. Several features look for things that don't exist during the loading screen.
  • Running it in an unsupported game does nothing harmful. The loader checks where you are and stops with a message rather than injecting the wrong script.
  • Copy the line at the top of this page into your executor and press Execute.
  • It's the same line for every supported game. The loader looks up which game you're in and fetches the right hub -- there's nothing to swap out when you move between them.
  • Because it fetches on every run, you always get the current version. There's no "update" step and no reinstalling after a patch.
  • A key screen appears the first time you run it in a session. Get the current key from the key page and paste it in.
  • The key rotates daily on UTC, and it's the same key across every game -- one key unlocks all of them.
  • Once unlocked, re-running the script in the same session skips the key screen and goes straight to the panel.
HOW IT WORKS

What that one line actually does.

Worth understanding, because it explains most of the behaviour people find surprising.

One loader, every game

  • The loader holds a list of place IDs mapped to hub scripts.
  • It reads the place you're in, finds the match, and fetches that script.
  • No match means a clean "not supported yet" warning rather than a crash.

Nothing is installed

  • The script is fetched into memory and run. It writes no program files.
  • Close Roblox and it's gone entirely.
  • The only thing kept on disk is a small settings file so your toggles survive a re-run.

Always current

  • Every run fetches fresh, so a fix pushed today reaches you on your next execute.
  • A long session won't notice a new version, so the panel shows an update notice when one lands.
  • Re-running the same line is the update.
TROUBLESHOOTING

When something doesn't work.

These cover the overwhelming majority of reports.

  • Test your executor by itself first with a one-line print. If that produces nothing, the executor is the problem, not the hub.
  • Check you're actually in a supported game. In an unsupported one the loader deliberately stops.
  • Make sure you're fully loaded in. Executing during the loading screen can miss objects the hub waits for.
  • Roblox updated recently? Executors break on Roblox patches and stay broken until they ship their own update. This is normal and not something a script can work around.
  • Working as intended -- the loader didn't find your place ID in its list.
  • Watch for lookalike places. Popular games have copies and private servers with different place IDs, and the hub is written against the specific one listed on its game page.
  • Compare the ID on the game's page here with the one in your Roblox URL.
  • Keys rotate daily on UTC, not on your local midnight. If you're near your own midnight the key may have already rolled -- reload the key page for the current one.
  • Copy it fresh rather than reusing yesterday's from your clipboard history.
  • Stray spaces from a sloppy copy are the single most common cause.
  • Press the keybind to toggle it back (Left Alt by default, changeable in Settings).
  • If you hit the X, just execute the line again -- it rebuilds, and your saved toggles come back with it.
  • Re-running is always safe. The hub shuts down any previous instance of itself before starting, so you never end up with two copies fighting.
  • Check the STATS tab first -- it shows what the hub currently thinks is going on, which usually explains it immediately.
  • Many features are gated on something the server decides: a cooldown, an unlock you don't have, or nothing being available to claim yet. Those are refusals, not failures.
  • Features that need an in-game prerequisite say so on the game's page. Alchemy needs a marked recipe; egg buying needs inventory space.
  • Roblox disconnects idle clients after about 20 minutes. It counts real input only -- a script sending network traffic doesn't reset that timer.
  • Turn on Anti-Idle. It sends a harmless synthetic input on Roblox's own idle event, which is the sanctioned way to keep a session alive.
  • Error Code 277 or 279 is a network drop on your end, not the script.
FAQ

Questions people actually ask.

  • Yes. Roblox prohibits this and enforces it, and individual games run their own detection on top of that. Nobody can honestly promise you otherwise.
  • The hubs avoid the crude things that get people caught -- they don't teleport where the game checks position, and they respect the request limits the games enforce.
  • That reduces risk. It doesn't remove it. If losing the account would genuinely bother you, use a different one.
  • Yes. Every hub here is free, and the key is free -- it exists to keep the scripts from being lifted and rehosted, not to sell you anything.
  • You will still need an executor, and most decent ones cost money. That's a separate purchase from a separate company.
  • It's one page and one paste, once per session, and the same key works across every game.
  • It rotates daily, which means a copy scraped and rehosted elsewhere stops working almost immediately.
  • Yes -- toggles, sliders and text fields persist per game, and a toggle you left on resumes what it was doing on the next run.
  • One deliberate exception: anything that risks your whole balance always starts off, so a fresh execute can never begin gambling before you've looked at the screen.
  • Settings live in a small file your executor manages. An executor without file access still runs everything, it just won't remember between sessions.
  • Games get added when there's a hub worth shipping, not to pad the list. Each one is written against that game's own code.
  • That's why the supported list is short. A generic script claiming fifty games is a script that works properly in none of them.
  • It never asks for your Roblox password, because it has no use for one. Anything that asks is stealing your account -- from us or from anyone else.
  • Nothing is installed and nothing runs in the background after Roblox closes.
  • See Privacy for specifics on what is and isn't recorded.
READY

Grab the key and go.

One key, one loader, every supported game.

Get Key Browse Games