Roblox Nexus Sync

Displays Roblox Studio output to an output channel in Visual Studio Code, with added Rojo/Argon sourcemap support for click to open script functionality.

Useful for certain projects where you want to quickly open scripts that error without having to navigate through your folders and file structures.

Features

• Colorised output messages, formatted based on message type

• Connects automatically or manually via plugin settings

• Rojo/Argon support: clickable stack trace file sources

Installation

• Install the Visual Studio Code Extension from the marketplace or package it yourself
• Install the Roblox Plugin from Roblox or build it yourself using Rojo

Usage

1. Start the server by running the Nexus Sync: Start Server command
2. Navigate to View > Output, click on the dropdown, and select Roblox Studio
3. Next to the dropdown, click the settings cog icon and select Trace, then select Set As Default
4. Open your place in Roblox Studio, and you should be connected!

Automatically start output server on launch

If you want Nexus Sync to start automatically, right click the extension and select Extension Settings, then enable the Auto Start setting. It is recommended you enable this in your workspace settings only!

Important step when using VSCode output channels

Ensure you complete the following for stack traces to show in your output:

Set the "Roblox Studio" output channel log level to "Trace", then set this as the default log level like shown below:

Have traces but still missing/scrambled messages ?

This is a Roblox bug with LogService, sometimes it will fail to send output messages in chronological order or may leave out a few messages, even with :GetLogHistory() / .MessageOut

It should work to a satisfactory degree most of the time, but you may get the odd occurence. Once Roblox fixes this problem it will resolve on its own.

Limitations

If you are using Rojo or Argon

For Rojo and Argon users, this extension relies on your sourcemap file(s) to locate scripts that error, so if it does not exist, your output will not contain clickable output text for script errors.

Output Flooding

If the studio output is flooded with prints/errors etc in a very short period of time (i.e. RunService events) the plugin may throttle the messages sent because of HttpService constraints

Singular Channel

Currently there is only one Roblox Studio channel that all the output messages will be logged to. You can still however log multiple studio places.

Play Tests

As of this time there are no detections in place yet to clear the output whenever a test session is launched.