How To Create Plugins: Difference between revisions

From Resonite Wiki
m Paradox19 moved page How To Write Plugins to How To Create Plugins: Reword for generalization
m fix broken links due to page movement
Line 13: Line 13:
#* <translate>During installation, ensure to select .NET desktop development which will give you the .NET Framework development tools, which are required to compile the plugin</translate>
#* <translate>During installation, ensure to select .NET desktop development which will give you the .NET Framework development tools, which are required to compile the plugin</translate>
# <translate>Create a new project using the <code>Class Library</code> template (please ensure it is the C# option). Guidelines follow:</translate>
# <translate>Create a new project using the <code>Class Library</code> template (please ensure it is the C# option). Guidelines follow:</translate>
## <translate>The project name ''should'' be the name of your plugin, same with the ''solution name''. It is recommended to '''not''' check the box for ''Place solution and project in the same directory'', as you may have multiple parts to your plugin, such as a [[How_To_Write_Plugins/ProtoFlux_Binding|ProtoFlux Binding]] generator.</translate>
## <translate>The project name ''should'' be the name of your plugin, same with the ''solution name''. It is recommended to '''not''' check the box for ''Place solution and project in the same directory'', as you may have multiple parts to your plugin, such as a [[How_To_Create_Plugins/ProtoFlux_Binding|ProtoFlux Binding]] generator.</translate>
## <translate>Select the default framework, we'll be manually editing this later.</translate>
## <translate>Select the default framework, we'll be manually editing this later.</translate>
# <translate>Add references to the following libraries by right clicking on <code>Dependencies</code>, clicking <code>Add Project Reference</code> and then <code>Browse</code>.</translate>
# <translate>Add references to the following libraries by right clicking on <code>Dependencies</code>, clicking <code>Add Project Reference</code> and then <code>Browse</code>.</translate>
Line 23: Line 23:
# <translate>Change Your Assembly Info file to tell [[FrooxEngine]] what type of plugin you are making.</translate>
# <translate>Change Your Assembly Info file to tell [[FrooxEngine]] what type of plugin you are making.</translate>
## <translate>Create a folder inside your project called</translate> <code>Properties</code>
## <translate>Create a folder inside your project called</translate> <code>Properties</code>
## <translate>Create a file called</translate> <code>AssemblyInfo.cs</code> <translate>which contains the line</translate> <code><nowiki>[assembly: DataModelAssembly(t)]</nowiki></code><translate>, where</translate> <code>t</code> <translate>is a [[How_To_Write_Plugins/DataModelAssemblyType|DataModelAssemblyType]].</translate>
## <translate>Create a file called</translate> <code>AssemblyInfo.cs</code> <translate>which contains the line</translate> <code><nowiki>[assembly: DataModelAssembly(t)]</nowiki></code><translate>, where</translate> <code>t</code> <translate>is a [[How_To_Create_Plugins/DataModelAssemblyType|DataModelAssemblyType]].</translate>


{{Note|<translate>The framework</translate> <code>net462</code> <translate>(step 4) is going to be changed in the future, this will most likely happen with the switch from Unity to [[Sauce]]</translate>|warning}}
{{Note|<translate>The framework</translate> <code>net462</code> <translate>(step 4) is going to be changed in the future, this will most likely happen with the switch from Unity to [[Sauce]]</translate>|warning}}
Line 29: Line 29:
<translate>You're now ready to start writing plugins!</translate>
<translate>You're now ready to start writing plugins!</translate>
<translate>Please see the following pages for in depth guides on how to code individual parts of plugins:</translate>
<translate>Please see the following pages for in depth guides on how to code individual parts of plugins:</translate>
* <translate>Creating custom [[How_To_Write_Plugins/Creating_Components|Components]]</translate>
* <translate>Creating custom [[How_To_Create_Plugins/Creating_Components|Components]]</translate>
* <translate>An introduction to creating custom [[How_To_Write_Plugins/Creating_ProtoFlux_Nodes|ProtoFlux]] nodes</translate>
* <translate>An introduction to creating custom [[How_To_Create_Plugins/Creating_ProtoFlux_Nodes|ProtoFlux]] nodes</translate>
* <translate>Creating a [[How_To_Write_Plugins/Creating_Bindings|ProtoFlux Binding]]</translate>
* <translate>Creating a [[How_To_Create_Plugins/Creating_Bindings|ProtoFlux Binding]]</translate>
''<translate>Please note: you are not limited to these guides, you may use any C# syntax.</translate>''
''<translate>Please note: you are not limited to these guides, you may use any C# syntax.</translate>''


Line 40: Line 40:
! <translate>Description</translate>
! <translate>Description</translate>
|-
|-
| [[How_To_Write_Plugins/Custom_Components|Components]]
| [[How_To_Create_Plugins/Custom_Components|Components]]
| <translate>Used to create custom components</translate>
| <translate>Used to create custom components</translate>
|-
|-
| [[How_To_Write_Plugins/DataModelAssemblyType|DataModelAssemblyType]]
| [[How_To_Create_Plugins/DataModelAssemblyType|DataModelAssemblyType]]
| <translate>The type of assembly you are making. Used in your</translate> <code>AssemblyInfo.cs</code> <translate>file.</translate>
| <translate>The type of assembly you are making. Used in your</translate> <code>AssemblyInfo.cs</code> <translate>file.</translate>
|-
|-
| [[How_To_Write_Plugins/ObjectFunctionNode|ObjectFunctionNode]]
| [[How_To_Create_Plugins/ObjectFunctionNode|ObjectFunctionNode]]
| <translate>A ProtoFlux Node which returns a singular object</translate>
| <translate>A ProtoFlux Node which returns a singular object</translate>
|-
|-
| [[How_To_Write_Plugins/ProtoFlux_Binding|ProtoFlux Binding]]
| [[How_To_Create_Plugins/ProtoFlux_Binding|ProtoFlux Binding]]
| <translate>The binding for a ProtoFlux Node. Without this, a node cannot be loaded into Resonite.</translate>
| <translate>The binding for a ProtoFlux Node. Without this, a node cannot be loaded into Resonite.</translate>
|-
|-
| [[How_To_Write_Plugins/ValueFunctionNode|ValueFunctionNode]]
| [[How_To_Create_Plugins/ValueFunctionNode|ValueFunctionNode]]
| <translate>A ProtoFlux Node which returns a singular value</translate>
| <translate>A ProtoFlux Node which returns a singular value</translate>
|-
|-
| [[How_To_Write_Plugins/VoidNode|VoidNode]]
| [[How_To_Create_Plugins/VoidNode|VoidNode]]
| <translate>A ProtoFlux Node which doesn't use</translate> <code>return</code> <translate>to give an output. Used for nodes with multiple outputs.</translate>
| <translate>A ProtoFlux Node which doesn't use</translate> <code>return</code> <translate>to give an output. Used for nodes with multiple outputs.</translate>
|-
|-

Revision as of 17:44, 15 July 2024

This page may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details.

Plugins are used to add more Components and ProtoFlux nodes to Resonite by programming them using C#. They are not to be confused with Mods which do not add things into the Data Model.

This page is about writing plugins and should not be confused with the Plugin overview page.

Please see the plugin guidelines before getting started, to familiarize yourself on what is and is not allowed.

Getting started

You will need to know the basics of the C# Programming Language to write plugins.

  1. Download Visual Studio Community edition, which allows for easier programming and compilation of plugins. However, you can use your favourite code editor as long as you know how to compile C# into a .dll
    • During installation, ensure to select .NET desktop development which will give you the .NET Framework development tools, which are required to compile the plugin
  2. Create a new project using the Class Library template (please ensure it is the C# option). Guidelines follow:
    1. The project name should be the name of your plugin, same with the solution name. It is recommended to not check the box for Place solution and project in the same directory, as you may have multiple parts to your plugin, such as a ProtoFlux Binding generator.
    2. Select the default framework, we'll be manually editing this later.
  3. Add references to the following libraries by right clicking on Dependencies, clicking Add Project Reference and then Browse.
    1. FrooxEngine.dll - Found in Resonite/Resonite_Data/Managed/FrooxEngine.dll
    2. Elements.Core.dll - Found in Resonite/Resonite_Data/Managed/Elements.Core.dll
  4. Change the referenced framework to net462. To do this:
    1. Double click on your project name, this will be under your solution
    2. Change the line <TargetFramework>whatever_you_selected_earlier</TargetFramework> to <TargetFramework>net462</TargetFramework> and save the file
  5. Change Your Assembly Info file to tell FrooxEngine what type of plugin you are making.
    1. Create a folder inside your project called Properties
    2. Create a file called AssemblyInfo.cs which contains the line [assembly: DataModelAssembly(t)], where t is a DataModelAssemblyType.
The framework net462 (step 4) is going to be changed in the future, this will most likely happen with the switch from Unity to Sauce

You're now ready to start writing plugins! Please see the following pages for in depth guides on how to code individual parts of plugins:

Please note: you are not limited to these guides, you may use any C# syntax.

Object Reference

Object Description
Components Used to create custom components
DataModelAssemblyType The type of assembly you are making. Used in your AssemblyInfo.cs file.
ObjectFunctionNode A ProtoFlux Node which returns a singular object
ProtoFlux Binding The binding for a ProtoFlux Node. Without this, a node cannot be loaded into Resonite.
ValueFunctionNode A ProtoFlux Node which returns a singular value
VoidNode A ProtoFlux Node which doesn't use return to give an output. Used for nodes with multiple outputs.

See also