rowikis

For developers

Connect your game and we build its wiki from your published place, drawn in your game's own UI.

What we read

Our script loads the ModuleScripts in ReplicatedStorage, ReplicatedFirst, ServerStorage and ServerScriptService and keeps the plain values they return: numbers, text, tables of stats, odds, codes and prices. That is where a game's units, maps and drops usually live.

  • It never reads script source and never saves anything. Roblox discards any change when the session ends.
  • It calls no DataStore or MemoryStore itself. A module of yours that reads one while it loads still will.
  • It skips installed libraries (anything under Packages, _Index or node_modules).

Read the exact script. It is the file we run, byte for byte.

An email for every run

You give us an email when you connect. We confirm it, and from then on every time we run Lua on your game you get a message like this:

We ran Lua on [BETA] Bizzare Last Survivor

Reason: Reading your game's data
Result: Read 399 ModuleScripts (1.6 MB)

Nothing runs until you've confirmed the email.

Make the key

The key needs one permission, luau-execution-sessions with read and write, restricted to your game. Make an API key walks through Creator Hub with screenshots.

Roblox warns that a key which can run Luau can reach your DataStores. That holds for any such key. Ours runs only the script above, and you hear about every run.

Connect your game

Stop at any time

Disconnect the game on the connect page, which deletes your key and email from our server, then delete the key in Creator Hub. Either one alone stops us.

A game connects to one Roblox account. If someone else connects it with a working key, we run the one-line key check (return game.GameId) with your key and email you the result. If Roblox refuses your key, the game moves to them; if it works, it stays yours.