Roblox Script Executor (rsexec) is a command-line interface that primarily uses the WeAreDevs API to run scripts on the Rōblox client. Sister repository to Personal Roblox Client Scripts.
To run my program, make sure Python is installed and that you're using Windows.
pip install -r requirements.txt
python src/main.pyI used JJSploit for a few years and found that having to deal with GUIs there when most of my other workflows live in PowerShell isn't great for productivity. It was a hassle for me to open a new file-selector window and modify a few initial values just to get a script I saved to run. Too many clicks!
To solve that problem, I had to iterate. I started out with adding a global function getrenv().exec which passes in a file path, relative to /workspace and a few other parameters. Then I had to modify existing scripts to work with my parameterisation system. I made sure that scripts could also return in case they needed t. This transformed my rudimentary script hub into an extensible function library!
I wasn't done yet! I wrote a Python program to hook the WeAreDevs DLL through finj.exe and connected with named pipes from the comfort of my terminal. The output was still printed onto the developer console, which still required mouse intervention -- so I wrote clunky wrapper code that pipes module output into the console (and not using rconsoleprint). It has since improved drastically.
The commands shown do not reflect whatever is available in the Lua getrenv() or getfenv() environments.
Commands consist of two main parts: the head and the body.
The head is the substring ranging from the first non-whitespace character to the first space after it.
The head often points to an alias which is a file in the following format:
${ROOT_FOLDER}/workspace/${BASE_NAME}.luaThe body is everything after it.
Some commands (such as find) split the body further into distinct parameters using a space delimiter. Others (such as output) treat the entire body as a single argument.
Commands are prefixed by either ; or :, as neither are used to begin a statement in Lua(u).
> ;output 6+4
10
> ;output "string"
string
> ;output workspace
game.Workspace
The prefix output can be substituted for o.
It is possible to store multi-value tuples into Lua variable _E.OUTPUT in a workspace script (see 'Output Formatting'). The generated output from multiple return values is separated by ;. The string.gsub() function in Lua for example always returns a tuple consisting of (string, number):
> ;output (string.gsub("abb", "b", "c"))
acc; 2
> ;chat "I'm exploiting and probably will catch someone's attention!" 6
If /workspace/chat.lua exists, it will be executed, with global table _E.ARGS initialised as:
{"I'm exploiting and probably will catch someone's attention!", 6}Some scripts return stuff.
> ;plr 'vis'
game.Players.VisualPlugin
Like any good script execution platform, rsexec should be able to run scripts from the internet. The name loadstring is misleading here because unlike its Lua counterpart, it also grabs Lua code from a provided URL. Note that the URL is not wrapped in quotes, as it is not parsed from a Lua object.
> ;ls https://raw.githubusercontent.com/EdgeIY/infiniteyield/master/source
This works more-or-less the same as:
loadstring(game:HttpGet('https://raw.githubusercontent.com/EdgeIY/infiniteyield/master/source'))()
The prefix ls can be substituted for loadstring.
Code blocks without a command prefix will be passed in as-is to the evaluator.
> game.Players.LocalPlayer.Character.Humanoid.Health = 0
> ;snippet game.Players.LocalPlayer.Character.Humanoid.Health = 0
Your character should die either way.
Alternatively, you can use prefix snippet.
The prefix snippet can be substituted for snip or s.
Multi-line snippets keep accepting input up to the first empty line. Useful for prototyping ... I guess?
> ;multiline
game.Players.LocalPlayer.Character.Humanoid.Health = 0
> ;o 6
6
That's another way your character can die. It also prints 6 to promote distinguishability.
The prefix multiline can be substituted for ml or m.
> ;del [[tree game.Workspace:GetDescendants()]]
From /workspace/tree.lua, returns a list of all objects in your Workspace.
Then, from /workspace/del.lua, deletes everything in the list.
To produce human-likeable output, some workspace scripts print a custom string when called at the top level. These callee scripts initialise an optional _E.OUTPUT table near the end of the body.
Many of those custom outputs use ANSI colour codes to improve readability.
> ;tree game.ReplicatedStorage
[02] game.ReplicatedStorage.EmoteBar {ModuleScript}
[03] game.ReplicatedStorage.EmoteBar.clientConfig {ModuleScript}
[03] game.ReplicatedStorage.EmoteBar.emotes {ModuleScript}
[03] game.ReplicatedStorage.EmoteBar.enums {ModuleScript}
...
However, this behaviour is not applied when done from a nested call. The following snippet will print a machine-readble Lua table:
> ;output [[tree game.ReplicatedStorage]]
{
game.ReplicatedStorage.EmoteBar,
game.ReplicatedStorage.EmoteBar.clientConfig,
game.ReplicatedStorage.EmoteBar.emotes,
game.ReplicatedStorage.EmoteBar.enums,
...
Rsexec runs Remote Spy immediately once it is injected. Events sent to the client vía OnClientEvent are also received, unlike other advanced implementations of Remote Spy. There are no GUIs are there to clutter the screen. Remotes do however fill up in /workspace/_rspy.dat on a per-session basis. Rsexec offers a way to dump Remote Spy logs to the console, as shown below. Executing dump starts the file pointer from the end of the previous read, per file name:
> dump rspy
> ;tree game.workspace [[function return a1.Parent.Name == 'Head']]
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.Head {WrapTarget}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.NeckRigAttachment {Attachment}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.FaceFrontAttachment {Attachment}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.HatAttachment {Attachment}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.HairAttachment {Attachment}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.FaceCenterAttachment {Attachment}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.Neck {Motor6D}
...
The result of /workspace/tree.lua here is every object in the Workspace whose parent's name is 'Head'.
The string:
[[function return a1.Parent.Name == 'Head']]
...is substituted with:
(function(a1, a2, ...) return a1.Parent.Name == 'Head' end)
The prefix function can be substituted for func or f.
Lambdas are useful for writing dynamic one-liners that take advantage of other features of the rsexec language. I personally use it a lot for the tree command.
> ;tree game.workspace [[lambda a1.Parent.Name == 'Head']]
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.Head {WrapTarget}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.NeckRigAttachment {Attachment}
[06] game.Workspace.InteractiveModels.AvatarEditorModel.NpcModel.Head.FaceFrontAttachment {Attachment}
...
Lambdas work similarly to the f prefix, but adds the return keyword prior to the function body.
The string:
[[lambda a1.Parent.Name == 'Head']]
...is replaced with:
(function(a1, a2, ...) return a1.Parent.Name == 'Head' end)
The prefix lambda can be substituted for l.