First of all, I will go over the original reason that RbxStu V3 was discontinued:
It was sadly discontinued due to internal changes in the engine. The changes broke many features. This included changing many internal functionalities, and overall it deviated from the original ‘run exploiter scripts’ into a more of a ‘run custom scripts in your game that modify the behavior of Roblox Studio.’
Here I will outline a few changes that have occurred internally:
- Rewrote the initialization of some features so it is much faster (mainly internal mode).
- No longer forces you to use DirectX 11, as ImGui is no longer used internally.
- Documented the ENTIRE API for RbxStu in its own standard.
This project does not support running exploiter scripts anymore, and you should not. The little retro-compatibility that remains is due to the useful tooling that exists, such as Hydroxide
, SimpleSpyV3
and other scripts.
RbxStu V4 does not attempt to limit you at all. You can execute everything and anything you want without constraints; this means that there are no in-place limitations or security of any kind, so execute carefully. You are unlikely to face issues by limiting yourself to public APIs that ROBLOX exposes by themselves.
New APIs are being constantly developed for this project. I intend it to mainly be about accessing, modifying, and overall making use of the Luau API that ROBLOX provides us as scripters without limits.
However, you must remember that modifications that directly modify Roblox Studio, like this kind, while not outright banned since they can be beneficial to the community, aren’t exactly something ROBLOX openly supports or will ever do. There are many risks, responsibilities, and promises that a tool like this would need; supporting a project like this is not really something they can do safely. But this is why we have come up with our own solutions to many things. No Luau signal API that’s sufficiently lightweight? No problem, Signal modules have you covered, for example.
When we, the community, are in need, we build the solution most of the time, and I believe this would be the case here.
Use case
RbxStu V4 has brand-new features that help you debug and modify the ROBLOX Luau API and, consequently, your game; you may even find internal crashes on functions by the methods of fuzzing the entire environment. This has, in fact been something exploits have been vulnerable to in the past, and even just the engine itself has these issues from time to time as seen in these two posts → Post 1, Post 2.
That is one use case, just finding bugs that you can report within the engine, although the API only seems to have issues on private segments of it (not something you can trip as a game developer yourself).
Another use case is also just debugging a game quickly. When you are commissioned for fixes in a game, combing through the code just to debug one feature is quite a task, more so when the game is fairly big and you’re on your own. Thanks to RbxStu V4, you can simply load a Remote Spy
, which is a tool that tracks remotes, the arguments that are fired with them, and other aspects, such as the script that called it. You use the ‘buggy’ feature, and because you are going to find the remote, finding the script on the server that uses such is a much more manageable task, overall helping you debug more than anything. This does not quite apply on games that use a Networking library, however…
Additionally, part of the pentesting feature set is still active and available and is actually being expanded actively with brand-new features. I have already released one post on how one could use these features to your advantage here. RbxStu was not explicitly required since some things you can achieve without it; however, it was recommended due to simply being the only true option that I could guarantee was
- safe.
- had little to no chance of flagging you, a developer, as a cheater.
- worked fine for dynamic analysis.
Regardless of all the previous, with RbxStu you can completely instrument and control the environment. You can make use of this for things such as tracking connections by hooking metatables and metamethods, and, upon exiting the DataModel, presenting a report of the numbers of connections that were disconnected and connected, for example.
That is simply one of the things you can do. RbxStu is extremely flexible due to the simple APIs in it. There is a myriad of things you can use it for as a developer, and I hope you find its value as I do when I make use of it on my own projects.
You may acquire RbxStu V4 on the new Discord server. Using GitHub releases made me have to duplicate the release notes every time, which was cumbersome and a bit annoying; I may change this and do GitHub releases given enough time; however, it is to be seen.
Frequently Asked Questions
- Is RbxStu V4 free?
- Always has been, because there is little chance someone pays for a Roblox Studio executor/modding platform, and I myself am not willing to bill anyone for such a thing.
- Is RbxStu V4 safe?
- It is safe, having released more than one post on the subject, as well as having enough time on the developer community. I believe that it goes without saying. This software has no means of tracking back to you on executions or anything.
Originally I intended to add a webhook for when exceptions were raised; however, it was discarded as the testers I had during development said it was not necessary, and I agreed.
- It is safe, having released more than one post on the subject, as well as having enough time on the developer community. I believe that it goes without saying. This software has no means of tracking back to you on executions or anything.
- What can RbxStu V4 run?
- RbxStu V4 can run anything as long as it uses the ‘
rSUNC
’ naming convention, which is its own naming convention, with open-source documentation here, with the published version over here. The documentation is open source; anyone can contribute to define new functions they themselves may find useful.
- RbxStu V4 can run anything as long as it uses the ‘
- Can I use this on …?
- All kinds of testing should be supported. You can use it on team tests, local tests, and normal testing.
- Who is behind this?
- Me, @roalex2008. I’m the only developer, with contributions from other external parties as times goes on.
- Can I teleport out of the-
- no.
- Will this be open-sourced?
- Open sourcing This tool was not useful at any point in any of its iterations. No one ever contributed to it. Only some friends I had made throughout the time of development, who already had source access, contributed. Many developers cannot contribute already because RbxStu requires you to know the engine more than just Luau. Base C++ knowledge also is not sufficient because of the design of it going over it (yes, I have improved since RbxStu V1). It also goes that they believe that because something is ‘Open source,’ it is ‘Safe,’ which is not the case (liblzma case, which had a backdoor, even when being in an open source project )
Ultimately, this is a tool for you, the developer; it is up to you how you make use of it or if you dismiss it entirely and use client cheats to achieve similar effects. The project is in constant development, and changes to it are communicated via the Discord server, I hope you can find usage for it
Notes and References:
- liblzma backdoor, XZ Utils backdoor - Wikipedia