com.unity.visualscripting@1.9.10

## [1.9.10] - 2026-02-23
### Changed
- Replaced internal use of InstanceIDs with the new EntityId (Unity 6.4+).
- Migrate Mono APIs to CoreCLR-compatible APIs available in Unity 6000.5 and above.
### Fixed
- Fixed loading icon showing on the Visual Scripting components in the inspector during play mode when the editor is compiling.

Author: Unity Technologies

.attestation.p7m

@@ -1 +1 @@
-{"timestamp":1749648028,"signature":"quvgEbmSibZAe6PBeTGnH5nstPG4HukUr2se553hY1NNjh0N7CZszSbLtW/icObS2gd3spEVhGdpxAA/kj9ubsu0AKzRi5GMK1LcvwVfWaGEu2OhyA9mAsRY0paNrd3WSAednsHytimbT00A32ixSg/5oBOviyK680XMBd5WRX7QxYK41zVy3H+tr2yyVcgx1IcN6TkCUhcvzuPCRZLzY3f228AwgHzXEx7LZ2hheIXx68+qdgo6Vha2frhAL1eyPZVfBZrL9LUgrrhsl3XONdht75q01PK0dgk7vlA3ILqrglN7K2UIVT+dvWEXy+b/0vaTps6vPSdXZdqZfZZTdpQgpneKHWlkLLSn3S+zZrJJCwelQ5dMrOBJ7DrRmu0hQLrRiR/HrgSziLz70Ou3ZH4kJMeVcRDPRBJ1Md2prdcBFqgTMQJrhi+DlDz0+7gFBN8fqXZUE/0mYfSBproCyFHODlm/pCk40WxusXVYs1lIC0LEf8ywh1jiMLOy5gnn","publicKey":"LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0KTUlJQm9qQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FZOEFNSUlCaWdLQ0FZRUFzdUhXYUhsZ0I1cVF4ZEJjTlJKSAordHR4SmoxcVY1NTdvMlZaRE1XaXhYRVBkRTBEMVFkT1JIRXNSS1RscmplUXlERU83ZlNQS0ZwZ1A3MU5TTnJCCkFHM2NFSU45aHNQVDhOVmllZmdWem5QTkVMenFkVmdEbFhpb2VpUnV6OERKWFgvblpmU1JWKytwbk9ySTRibG4KS0twelJlNW14OTc1SjhxZ1FvRktKT0NNRlpHdkJMR2MxSzZZaEIzOHJFODZCZzgzbUovWjBEYkVmQjBxZm13cgo2ZDVFUXFsd0E5Y3JZT1YyV1VpWXprSnBLNmJZNzRZNmM1TmpBcEFKeGNiaTFOaDlRVEhUcU44N0ZtMDF0R1ZwCjVNd1pXSWZuYVRUemEvTGZLelR5U0pka0tldEZMVGdkYXpMYlpzUEE2aHBSK0FJRTJhc0tLTi84UUk1N3UzU2cKL2xyMnZKS1IvU2l5eEN1Q20vQWJkYnJMbXk0WjlSdm1jMGdpclA4T0lLQWxBRWZ2TzV5Z2hSKy8vd1RpTFlzUQp1SllDM0V2UE16ZGdKUzdGR2FscnFLZzlPTCsxVzROY05yNWdveVdSUUJ0cktKaWlTZEJVWmVxb0RvSUY5NHpCCndGbzJJT1JFdXFqcU51M3diMWZIM3p1dGdtalFra3IxVjJhd3hmcExLWlROQWdNQkFBRT0KLS0tLS1FTkQgUFVCTElDIEtFWS0tLS0tCg"}
+{"timestamp":1771623724,"signature":"sQCS2yw17Pttk29Qux8Y/VlcQ/uiZaVGgOhkvKUxbOyHfxXAPTmWV18RRPLPU6NO+ZV8HjCqNpbLlTTMuw/81Mx5e/yWdXQ26Ay8jcNwyFWj/PXmL1Z9f6OS1xp2irIHjdLN9ga/9x5S1um/gj7d8LhMNK7Rgzdc7FS+0du/McMHLhGD7kpOOw0czsGmjwXWrUaPK57ZCRlut2ZXz+4UiDdmhILiygpKxYrDJ4HQVLmbsSLj6ryyRkYeWYsVon9qYhL2QYXTwjYAeR2yUI6VvusUUixPz00fyC1O0F5yHOpDSJ9sCV29cGo0Fn+mRQWV1LhMOQcpRb1yi9I68NNPqc6ZsDOjenL39xXT4H0pWWLESOYPvAFXKaqglSPvlnU0Peduwa4q6CUMXOddSeUOFpTxDdpz3l5cgvjN106B0J45+NqPZ+0nrsV9SwjDno3Y76vAtcWDz/3V7tawWs9sQUWagoRblIdDnoa8ItnZIQq4kjZhjAR8JBpxmXLwtRyQ","publicKey":"LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0KTUlJQm9qQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FZOEFNSUlCaWdLQ0FZRUFzdUhXYUhsZ0I1cVF4ZEJjTlJKSAordHR4SmoxcVY1NTdvMlZaRE1XaXhYRVBkRTBEMVFkT1JIRXNSS1RscmplUXlERU83ZlNQS0ZwZ1A3MU5TTnJCCkFHM2NFSU45aHNQVDhOVmllZmdWem5QTkVMenFkVmdEbFhpb2VpUnV6OERKWFgvblpmU1JWKytwbk9ySTRibG4KS0twelJlNW14OTc1SjhxZ1FvRktKT0NNRlpHdkJMR2MxSzZZaEIzOHJFODZCZzgzbUovWjBEYkVmQjBxZm13cgo2ZDVFUXFsd0E5Y3JZT1YyV1VpWXprSnBLNmJZNzRZNmM1TmpBcEFKeGNiaTFOaDlRVEhUcU44N0ZtMDF0R1ZwCjVNd1pXSWZuYVRUemEvTGZLelR5U0pka0tldEZMVGdkYXpMYlpzUEE2aHBSK0FJRTJhc0tLTi84UUk1N3UzU2cKL2xyMnZKS1IvU2l5eEN1Q20vQWJkYnJMbXk0WjlSdm1jMGdpclA4T0lLQWxBRWZ2TzV5Z2hSKy8vd1RpTFlzUQp1SllDM0V2UE16ZGdKUzdGR2FscnFLZzlPTCsxVzROY05yNWdveVdSUUJ0cktKaWlTZEJVWmVxb0RvSUY5NHpCCndGbzJJT1JFdXFqcU51M3diMWZIM3p1dGdtalFra3IxVjJhd3hmcExLWlROQWdNQkFBRT0KLS0tLS1FTkQgUFVCTElDIEtFWS0tLS0tCg"}

.signature

@@ -2,6 +2,13 @@
 All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 
+## [1.9.10] - 2026-02-23
+### Changed
+- Replaced internal use of InstanceIDs with the new EntityId (Unity 6.4+).
+- Migrate Mono APIs to CoreCLR-compatible APIs available in Unity 6000.5 and above.
+### Fixed
+- Fixed loading icon showing on the Visual Scripting components in the inspector during play mode when the editor is compiling.
+
 ## [1.9.8] - 2025-06-11
 ### Fixed
 - Fixed broken links to example codes in API documentation.

CHANGELOG.md

@@ -1,9 +1,6 @@
 ---
 title: nodes-input-output-trigger
 ---
-
-<tr>
-<td><strong>Trigger</strong></td>
-<td>Output Trigger</td>
-<td>The control output port. Make a connection to specify what Visual Scripting should do after the configured Input event occurs in your application.</td>
-</tr>
+| **Name** | **Type** | **Description** |
+| :--- | :--- | :--- |
+| **Trigger** | Output Trigger | The control output port. Make a connection to specify what Visual Scripting should do after the configured Input event occurs in your application. |

Documentation~/snippets/input-manager/nodes-input-output-trigger.md

@@ -1,9 +1,6 @@
 ---
 title: nodes-coroutine
 ---
-
-<tr>
-<td><strong>Coroutine</strong></td>
-<td>Toggle</td>
-<td>Enable <strong>Coroutine</strong> if you want Visual Scripting to run this node and any of its connected nodes as a coroutine. Coroutine nodes don't execute all their code in a single frame, so they can spread an effect over several frames. Coroutines can also help optimize your code. For more information on coroutines, see the Unity User Manual section on <a href="https://docs.unity3d.com/Manual/Coroutines.html">Coroutines</a>.</td>
-</tr>
+| **Name** | **Type** | **Description** | 
+| :--- | :--- | :--- |
+| **Coroutine** | Toggle | Enable **Coroutine** if you want Visual Scripting to run this node and any of its connected nodes as a coroutine. Coroutine nodes don't execute all their code in a single frame, so they can spread an effect over several frames. Coroutines can also help optimize your code. For more information on coroutines, refer to the Unity User Manual section on <a href="https://docs.unity3d.com/Manual/Coroutines.html">Coroutines</a>. |

Documentation~/snippets/nodes-coroutine.md

@@ -29,7 +29,7 @@ To add an existing graph file as a Subgraph in a Script Graph:
 > [!NOTE]
 > You can't nest a Script Graph as a Subgraph in its own graph file. 
 
-1. [!include[vs-with-graph-open-ff](./snippets/vs-with-graph-open-ff.md)]. Go to **Nesting** and select **Subgraph**. 
+1. [!include[vs-with-graph-open-ff](./snippets/vs-with-graph-open-ff.md)] Go to **Nesting** and select **Subgraph**. 
 
 2. In the Graph Inspector, set your **Source** to **Graph**. 
    <br/>

Documentation~/vs-add-subgraph.md

@@ -5,34 +5,41 @@
 
 To create a basic Script Graph that uses the Input Manager to capture input: 
 
-<ol>
-<li><p><a href="vs-open-graph-edit.md">Open</a> or <a href="vs-create-graph.md">create</a> a Script Graph attached to the GameObject that you want your users to move.</p></li>
-<li><p>If there isn't an <strong>On Update</strong> or similar Event node in your graph:</p>
-    <ol type="a">
-        <li><p>[!include[vs-open-fuzzy-finder](./snippets/vs-open-fuzzy-finder.md)]</p></li>
-        <li><p>Go to <strong>Events</strong> &gt; <strong>Lifecycle</strong>, or enter <strong>On Update</strong> in the search field.</p></li>
-        <li><p>Select the <strong>On Update</strong> Event node to add it to the graph.</p></li>
-    </ol>
-</li>
-<li><p>[!include[vs-open-fuzzy-finder](./snippets/vs-open-fuzzy-finder.md)]</p></li>
-<div class="TIP"><h5>TIP</h5><p>If you right-click and the context menu appears, select <strong>Add Node</strong> to open the fuzzy finder.</p></div>
-<li><p>Go to <strong>Codebase</strong> &gt; <strong>Unity Engine</strong> &gt; <strong>Input</strong>, or enter <strong>Get Axis</strong> in the search field.</p></li>
-<li><p>Select <strong>Get Axis (Axis Name)</strong> to add the Get Axis node to the graph.</p></li>
-<li><p>Repeat Steps 3 through 5 to create a second <strong>Get Axis (Axis Name)</strong> node.</p></li>
-<li><p>On the first Get Axis node, in the <strong>Axis Name</strong> input field, enter <code>Horizontal</code>.</p></li>
-<li><p>On the second Get Axis node, in the <strong>Axis Name</strong> input field, enter <code>Vertical</code>.</p></li>
-<div class="NOTE"><h5>NOTE</h5><p>If an Axis Name doesn't match the name in the Input Manager's Project Settings, Visual Scripting displays an error in the Graph Inspector. When you enter Play mode, the Unity Editor also displays an error in the Console window.</p></div>
-<li><p>[!include[vs-open-fuzzy-finder](./snippets/vs-open-fuzzy-finder.md)]</p></li>
-<li><p>Go to <strong>Codebase</strong> &gt; <strong>Unity Engine</strong> &gt; <strong>Transform</strong> or search for <strong>Translate</strong>.</p></li>
-<li><p>Select <strong>Translate (X, Y, Z)</strong> to add a Translate node to the graph.</p></li>
-<li><p>Select the <strong>Result</strong> float output port on the <code>Horizontal</code> Get Axis node.</p></li>
-<li><p><a href="vs-creating-connections.md">Make a connection</a> to the <strong>X</strong> input port on the <strong>Translate</strong> node.</p></li>
-<li><p>Select the <strong>Result</strong> float output port on the <code>Vertical</code> Get Axis node.</p></li>
-<li><p><a href="vs-creating-connections.md">Make a connection</a> to the <strong>Z</strong> input port on the <strong>Translate</strong> node. <br/>The finished graph looks similar to the following image:</p></li>
-<p><img src="images/vs-input-old-system-example.png" alt="An image of the Graph window, that displays the final result of a simple input capture graph using the Input Manager. An On Update node connects to the Trigger input port on a Transform Translate node. The Result port on an Input Get Axis node with an Axis Name of Horizontal connects to the X input port on the Translate node. The Result port on another Input Get Axis node with an Axis Name of Vertical connects to the Z input port."></p>
-<li><p>To enter Play mode, select <strong>Play</strong> from the <a href="https://docs.unity3d.com/Manual/Toolbar.html">Unity Editor's Toolbar</a>.</p></li>
-<li><p>While in the <a href="https://docs.unity3d.com/Manual/GameView.html">Game view</a>, press a key mapped as a <strong>Negative Button</strong> or <strong>Positive Button</strong> from the <a href="https://docs.unity3d.com/Documentation/Manual/class-InputManager.html">Input Manager's virtual axes</a>.</p></li>
-</ol>
+1. [Open](vs-open-graph-edit.md) or [create](vs-create-graph.md) a Script Graph attached to the GameObject that you want your users to move.
+1. If there isn't an **On Update** or similar Event node in your graph:
+   
+   1. [!include[vs-open-fuzzy-finder](./snippets/vs-open-fuzzy-finder.md)]
+   1. Go to **Events** > **Lifecycle**, or enter **On Update** in the search field.
+   1. Select the **On Update** Event node to add it to the graph.
+    
+1. [!include[vs-open-fuzzy-finder](./snippets/vs-open-fuzzy-finder.md)]
+
+    > [!TIP]
+    > If you right-click and the context menu appears, select **Add Node** to open the fuzzy finder.
+
+1. Go to **Codebase** &gt; **Unity Engine** &gt; **Input**, or enter **Get Axis** in the search field.
+1. Select **Get Axis (Axis Name)** to add the Get Axis node to the graph.
+1. Repeat Steps 3 through 5 to create a second **Get Axis (Axis Name)** node.
+1. On the first Get Axis node, in the **Axis Name** input field, enter `Horizontal`.
+1. On the second Get Axis node, in the **Axis Name** input field, enter `Vertical`.
+
+    > [!NOTE]
+    > If an Axis Name doesn't match the name in the Input Manager's Project Settings, Visual Scripting displays an error in the Graph Inspector. When you enter Play mode, the Unity Editor also displays an error in the Console window.
+
+1. [!include[vs-open-fuzzy-finder](./snippets/vs-open-fuzzy-finder.md)]
+1. Go to **Codebase** &gt; **Unity Engine** &gt; **Transform** or search for **Translate**.
+1. Select **Translate (X, Y, Z)** to add a Translate node to the graph.
+1. Select the **Result** float output port on the `Horizontal` Get Axis node.
+1. [Make a connection](vs-creating-connections.md) to the **X** input port on the **Translate** node.
+1. Select the **Result** float output port on the `Vertical` Get Axis node.
+1. [Make a connection](vs-creating-connections.md) to the **Z** input port on the **Translate** node. 
+    
+    The finished graph looks similar to the following image:
+
+    <img src="images/vs-input-old-system-example.png" alt="An image of the Graph window, that displays the final result of a simple input capture graph using the Input Manager. An On Update node connects to the Trigger input port on a Transform Translate node. The Result port on an Input Get Axis node with an Axis Name of Horizontal connects to the X input port on the Translate node. The Result port on another Input Get Axis node with an Axis Name of Vertical connects to the Z input port.">
+1. To enter Play mode, select **Play** from the [Unity Editor's Toolbar](https://docs.unity3d.com/Manual/Toolbar.html).
+1. While in the [Game view](https://docs.unity3d.com/Manual/GameView.html), press a key mapped as a **Negative Button** or **Positive Button** from the [Input Manager's virtual axes](https://docs.unity3d.com/Documentation/Manual/class-InputManager.html).
+
 
 The GameObject moves along the X or Z axis in the Game view, based on the key pressed and the [Input Manager Project Settings](https://docs.unity3d.com/Documentation/Manual/class-InputManager.html). 
 

Documentation~/vs-capturing-player-inputs-old.md

@@ -12,59 +12,16 @@ To open your Project Settings:
 
 You can find the following configuration options in your Visual Scripting Project Settings. To use Visual Scripting in a project for the first time, you must [regenerate your Node Library](#Regen), as described in the table below. 
 
-<table>
-<thead>
-<tr>
-<th><strong>Option</strong></th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td><strong><a name="Initialize">Initialize Visual Scripting</a></strong></td>
-<td>You must select <strong>Initialize Visual Scripting</strong> the first time you use Visual Scripting in a project. Initialize Visual Scripting to parse all assemblies and types for the Visual Scripting Node Library. After you initialize Visual Scripting, regenerate your Node Library. See <strong><a href="#Regen">Regenerate Nodes</a></strong>, below.</td>
-</tr>
-<tr>
-<td><strong>Type Options</strong></td>
-<td>Use the Type Options list to add or remove types for your node inputs and outputs. After you add or remove a type, you must regenerate your Node Library. See <strong><a href="#Regen">Regenerate Nodes</a></strong>, below. <br/>For more information on how to add or remove types, see <a href="vs-add-remove-type-options.md">Add or remove types</a>.</td>
-</tr>
-<tr>
-<td><strong>Node Library</strong></td>
-<td>Use the Node Library list to add or remove nodes and their assemblies in Visual Scripting. You must add any new types to your Type Options after you add new nodes to Visual Scripting. You must also regenerate your Node Library after you add or remove nodes. See <a href="#Regen"><strong>Regenerate Nodes</strong></a>, below. <br/>For more information on how to add or remove nodes from your Node Library, see <a href="vs-add-remove-node-library.md">Add or remove available nodes</a>.</td>
-</tr>
-<tr>
-<td><strong><a name="Regen">Regenerate Nodes</a></strong></td>
-<td>Regenerate your Node Library to make all nodes available for use in a project. <br/>To use Visual Scripting for the first time in a project, you must <strong><a href="#Initialize">Initialize Visual Scripting</a></strong> and regenerate your Node Library. <br/>To regenerate your Node Library: 
-<ol>
-    <li><p>Select <strong>Regenerate Nodes</strong>.</p></li>
-    <li><p>Select <strong>OK</strong>.</p></li>
-</ol>
-<div class="NOTE"><h5>NOTE</h5><p>You must regenerate your Node Library in the following circumstances: 
-<ul>
-<li>Before you use Visual Scripting in your project for the first time.</li>
-<li>After you add or remove nodes from your Node Library.</li>
-<li>After you add or remove types from your Type Options.</li>
-<li>After you change the inputs or outputs for a Custom C# node.</li>
-</ul></p></div></td>
-</tr>
-<tr>
-<td><strong>Generate</strong></td>
-<td>To generate required property provider scripts for custom drawers, select <strong>Generate</strong>. <br/>These scripts are necessary for Unity to use custom drawers for custom classes and script variables inside Visual Scripting. To assign a default value to a custom variable type through the Unity Editor’s Inspector, you must either have access to the source code for the class, or provide a custom PropertyDrawer. For more information, see <a href="vs-custom-types.md">Custom types</a>.</td>
-</tr>
-<tr>
-<td><strong>Create Backup</strong></td>
-<td>To create a new backup of your Visual Scripting graphs and settings, select <strong>Create Backup</strong>. <br/> For more information about backups, see <a href="vs-create-restore-backups.md">Create or restore a backup</a>.</td>
-</tr>
-<tr>
-<td><strong>Restore Backup</strong></td>
-<td>To open the folder where Visual Scripting stores your backups, select <strong>Restore Backup</strong>. <br/>For more information about backups, see <a href="vs-create-restore-backups.md">Create or restore a backup</a>.</td>
-</tr>
-<tr>
-<td><strong>Fix Missing Scripts</strong></td>
-<td>To correct any issues that might occur after migration from the Unity Asset Store version of Visual Scripting to the package version, select <strong>Fix Missing Scripts</strong>. This resolves any missing references to Visual Scripting Script Graphs and State Graphs in Script Machine or State Machine components.</td>
-</tr>
-</tbody>
-</table>
+| Option | Description |
+|---|---|
+| Initialize Visual Scripting | You must select **Initialize Visual Scripting** the first time you use Visual Scripting in a project. Initialize Visual Scripting to parse all assemblies and types for the Visual Scripting Node Library. After you initialize Visual Scripting, regenerate your Node Library. Refer to **<a href="#Regen">Regenerate Nodes</a>**, below. |
+| Type Options | Use the Type Options list to add or remove types for your node inputs and outputs. After you add or remove a type, you must regenerate your Node Library. Refer to **<a href="#Regen">Regenerate Nodes</a>**, below. <br/>For more information on how to add or remove types, refer to <a href="vs-add-remove-type-options.md">Add or remove types</a>. |
+| Node Library | Use the Node Library list to add or remove nodes and their assemblies in Visual Scripting. You must add any new types to your Type Options after you add new nodes to Visual Scripting. You must also regenerate your Node Library after you add or remove nodes. Refer to <a href="#Regen">**Regenerate Nodes**</a>, below. <br/>For more information on how to add or remove nodes from your Node Library, refer to <a href="vs-add-remove-node-library.md">Add or remove available nodes</a>. |
+| Regenerate Nodes | Regenerate your Node Library to make all nodes available for use in a project. <br/>To use Visual Scripting for the first time in a project, you must **<a href="#Initialize">Initialize Visual Scripting</a>** and regenerate your Node Library. <br/>To regenerate your Node Library: <br/> 1. Select **Regenerate Nodes**. <br/> 2. Select **OK**.<br/> You must regenerate your Node Library in the following circumstances: <br/> * Before you use Visual Scripting in your project for the first time. <br/> * After you add or remove nodes from your Node Library. <br/> * After you add or remove types from your Type Options. <br/> * After you change the inputs or outputs for a Custom C# node. |
+| Generate | To generate required property provider scripts for custom drawers, select **Generate**. <br/>These scripts are necessary for Unity to use custom drawers for custom classes and script variables inside Visual Scripting. To assign a default value to a custom variable type through the Unity Editor’s Inspector, you must either have access to the source code for the class, or provide a custom PropertyDrawer. For more information, see <a href="vs-custom-types.md">Custom types</a>. |
+| Create Backup | To create a new backup of your Visual Scripting graphs and settings, select **Create Backup**. <br/> For more information about backups, refer to <a href="vs-create-restore-backups.md">Create or restore a backup</a>. | 
+| Restore Backup | To open the folder where Visual Scripting stores your backups, select **Restore Backup**. <br/>For more information about backups, refer to <a href="vs-create-restore-backups.md">Create or restore a backup</a>. |
+| Fix Missing Scripts | To correct any issues that might occur after migration from the Unity Asset Store version of Visual Scripting to the package version, select **Fix Missing Scripts**. This resolves any missing references to Visual Scripting Script Graphs and State Graphs in Script Machine or State Machine components. |
 
 >[!NOTE] 
 > If your settings don't apply after you make a change, [report a bug through the Unity Editor](https://unity3d.com/unity/qa/bug-reporting).