Type: Toolbox Explorer Element Container Service

Description:
RBLX-002 is a container service located within the 2012 ROBLOX Studio Client as an Explorer Element called the “Subspace.” It sits underneath its counterpart service, the “Workspace,” and functions relatively similarly. However, if the user deletes, disables or transfers the given Camera Element from the Workspace into the Subspace, as well as change the Subspace’s own sub-element (see RBLX-002-A,) then they will find themselves viewing a studio session of an ongoing ROBLOX server. This remains for as long as the Camera exists within the Subspace.

Anomalous real-time studio sessions allow the user precise manipulation over the ROBLOX Engine via its regular interface functions. Any action made by the user causes a reaction from their session’s attached server, acting almost like a one-sided portal. Models, scripts and other such services & elements are capable of being inserted and subsequently interacted with by the environment and surrounding players, if such elements are seen.

These elements – as well as the entire game file itself – can be copied and pasted into a separate studio session or saved to a hard drive, resulting in the potential theft of others’ assets, thereby directly bypassing ROBLOX’s built-in “Uncopylock” feature. However, any action the user makes will exist solely in that studio and server session. The game cannot be updated unless republished as its own.

When it comes to playtesting, the user will simply join the server like normal in a separate ROBLOX Player Instance and are able to subject themselves to the same real-time changes in their studio session alongside everyone else in the server. An ongoing server follows the studio session’s lifetime or its own, depending entirely on the user or those playing in a game instance. A server survives up until the moment it either:

1. Shuts down via outside interference, such as the ROBLOX Servers crashing, the Game Owner making a decision to close an ongoing instance, or the user themselves shuts it down from their ROBLOX Studio Client.

2. The user, or a player are the last to leave the server. This means that if the user remains until no players are left, the server session will collapse and vice versa.

3. The user or Game is terminated.


Type: Container Subservice

Description: RBLX-002-A is a sub-service element that appears in the Properties window when the Subspace Element is clicked. Specifically, it is a variable capable of being changed to match an existing ROBLOX Game’s ID. Upon doing so, its anomalous application surfaces by connecting the user’s studio session to an ongoing server associated with their chosen GameID. In essence, RBLX-002-A is the lifeline responsible for connecting and upholding both sessions together.

Through the user’s own means of experimentation, RBLX-002-A’s capabilities can be weaponised in various ways. Provided below are two methods:

1. By entering a GameID associated with a private game as long as a server session is active at the same time, the user can “playtest” in order to force themselves inside any ongoing server. Of course, with their access to the studio session as well, this invasion of privacy may allow ROBLOX Events to be leaked.

2. A user can also exceed the player-cap of any given server by “playtesting.”


Contributions: JPDexination (Author)