Examples include training neural networks, adding lighting to all neon parts, tagging all interactable parts, reformatting large portions of data, etc. BytExecutor allows the user to skip this time waste.Īutomating large tasks is made easy with this plugin. Debugging can include long periods of testing and revising before a bug can be fixed that is often bottlenecked by the time it takes for Studio to start a test instance. Testing the functionality of a piece of code before implementation can be done easily without the command bar using BytExecutor. Fired just before termination (forced or not)ĪPI.BeforeTermination(reason: string): GoodSignal (these are pretty much the same as the API methods)
Gets the Byt address associated with the Byt nameĪPI.getAddressFromName(bytName: string): string Gets the BytObject associated with the Byt nameĪPI.getBytFromName(bytName: string): BytObject Useful for saving information generated by BytsĪPI.tableToModule(t: table, parent: Instance?): ModuleScript Byts may also have additional icons during execution if pausing/terminating scripts is enabled in the settings.īyts have an API that you can use to enhance their usefulness, such as executing Byts in parallel, defining external behavior, and exporting data. The play button executes the script, the pencil icon opens the script editor, the two paper icon exports that script, and the trash button deletes the script. To interact with the Byt script, hover the cursor over it. Note that BytExecutor only allows alphanumeric (as well as the space and underscore) characters to be used. To change the name of the Byt script, click its name. If you don’t want Byts to automatically open, you can change this in the settings. The plugin automatically opens the script using Studio’s native code editor. Currently, it is “not running”, but it can be in a variety of other states, such as “running”, “failed”, “terminated”, and “finished”. That is the execution status of the Byt script. The Byt script has a little clip board icon next to it. The settings button opens BytExecutor’s settings. The two paper icon exports all Byts the user has and parents them to the Instance they selected. When the user is not selecting any scripts, it is disabled. The one with a down arrow imports an external script the user has selected in the Explorer into the plugin. Clicking the button with the large plus sign creates our “Byt script”, which is what the plugin uses to run code.
The topbar has four buttons, 3 on the left and 1 on the right. Upon downloading the plugin, you will need to open the BytExecutor. It can create, run, and save your multi-lined code from within studio without having to rely on the command bar, sporting an incredibly easy-to-use interface that even a complete noob could understand.
BytExecutor is a in-studio code executor plugin suited as a free alternative to the more expensive InCommand.
0 kommentar(er)
