Skip to content

Latest commit

 

History

History
94 lines (63 loc) · 4.87 KB

File metadata and controls

94 lines (63 loc) · 4.87 KB

Developing and building the plugin

Fork the repository if you need to

If you have write access to DialogueMaker/plugin, skip to the next step. If you don't, you're going to have to fork the repository. This essentially creates a sandbox environment for you to make your changes without affecting others.

Recursively clone the repository

This repository use a git submodule to include the Dialogue Maker Client script in the plugin. This helps if you want to make quick edits to how that script works while also giving you control over the plugin code.

In this case, you should recursively clone the repository using the terminal or your favorite code editor.

Using the terminal

Move to a comfortable folder where you can put your repositories, then run this command in your terminal after replacing <REPOSITORY_NAME> and <REPOSITORY_OWNER>.

git clone --recurse-submodules -j8 git://github.com/<REPOSITORY_OWNER>/<REPOSITORY_NAME>.git

This should create a folder for you.

Using Visual Studio Code

If you're using Visual Studio Code, open the Command Palette (CTRL+SHIFT+P or CMD+SHIFT+P) and press the "Git: Clone (Recursive)" option.

A popup window with a button labeled "Git: Clone (Recursive)" selected.

Select "Clone from GitHub".

A popup window with a button labeled "Clone with GitHub" selected.

Select your repository. If you don't have write access to DialogueMaker/plugin, you need to select a fork.

A popup window with a button labeled "DialogueMaker/plugin" selected.

After you select the repository, your file explorer should open for you to choose a place to put your repository.

Tip

If the DialogueClientScript directory shows up empty after cloning the repository, open the terminal in the folder and run this command to populate the DialogueClientScript:

git submodule update --init --recursive

You may need to run this again later. Submodules are kinda quirky.

Install pesde and packaged tools

To develop with the plugin, you'll have to install some third-party tools. First up, pesde: This is used for installing packzages that the plugin uses, such as Rojo and React Lua. It's also used to install packages that the client uses. Be sure to use v0.7.0-rc3 or above because earlier versions of pesde require admin access. You can learn more about pesde here on their website.

After installing pesde, you can run the following command to install the remaining tools:

pesde install

Install the Rojo Roblox Studio plugin

The Rojo Roblox Studio plugin is used to sync your changes between your code editor and Roblox Studio.

Using the terminal

rojo plugin install

Using Visual Studio Code

If you have the Rojo extension, you can add the Roblox Studio plugin using the GUI.

alt text

alt text

Open up the local Rojo server

After installing the tools, you should be able to use Rojo. Serve development.project.json to develop with the plugin.

Using the terminal

rojo serve development.project.json

Using Visual Studio Code

Warning

You may have an issue with closing and re-opening the server normally with Rojo's extension. Consider using the terminal for the time being.

alt text

alt text

Make and test your feature

Save DialoguePluginScript as a local plugin on Roblox Studio to test your changes. You need to do this every time you save changes to the code.

Commit your changes

Remember to regularly commit your changes with meaningful messages. This will help you remember what you did, and help others do the same.

Submit a pull request when you're ready

Whenever you're ready, make a pull request from your local repository to the DialogueMaker/plugin repository. Mark it as a draft if you aren't finished with it.


Documentation writers: Christian Toney