toc restructure

Author: jankrassnigg

pages/docs/custom-code/visual-script/nodes/vscript-nodes-blackboard.md

@@ -2,7 +2,7 @@
 
 ## Blackboards
 
-[Blackboards](../../misc/blackboards.md) are shared data storage systems that allow different game objects and components to communicate by reading and writing named values. The blackboard nodes in visual scripts provide access to blackboard entries for reading and modifying shared state.
+[Blackboards](../../../misc/blackboards.md) are shared data storage systems that allow different game objects and components to communicate by reading and writing named values. The blackboard nodes in visual scripts provide access to blackboard entries for reading and modifying shared state.
 
 ## See Also
 

pages/docs/custom-code/visual-script/nodes/vscript-nodes-component.md

@@ -2,12 +2,12 @@
 
 ## Component
 
-Component nodes provide access to functionality shared by all [components](../../runtime/world/components.md). These are essential nodes for interacting with the component system and navigating the object hierarchy.
+Component nodes provide access to functionality shared by all [components](../../../runtime/world/components.md). These are essential nodes for interacting with the component system and navigating the object hierarchy.
 
 Common component operations:
 
-* `GetOwner`: Returns the component's owner [game object](../../runtime/world/game-objects.md)
-* `GetWorld`: Returns the [world](../../runtime/world/worlds.md) that the component belongs to
+* `GetOwner`: Returns the component's owner [game object](../../../runtime/world/game-objects.md)
+* `GetWorld`: Returns the [world](../../../runtime/world/worlds.md) that the component belongs to
 
 Additionally, each component type has its own specialized nodes available in the sub-menus, providing access to component-specific functionality. Use these together with [property nodes](vscript-nodes-property.md) to read and modify component state.
 
@@ -16,7 +16,7 @@ Additionally, each component type has its own specialized nodes available in the
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [Components](../../runtime/world/components.md)
+* [Components](../../../runtime/world/components.md)
 * [Game Object Nodes](vscript-nodes-game-object.md)
 * [World Nodes](vscript-nodes-world.md)
 * [Property Nodes](vscript-nodes-property.md)

pages/docs/custom-code/visual-script/nodes/vscript-nodes-cvar.md

@@ -2,7 +2,7 @@
 
 ## CVar
 
-CVar nodes allow you to read and write [console variables (CVars)](../../debugging/cvars.md) from within visual scripts. CVars are configuration values that can be modified at runtime through the console, making them useful for debugging, testing, and exposing tunable parameters.
+CVar nodes allow you to read and write [console variables (CVars)](../../../debugging/cvars.md) from within visual scripts. CVars are configuration values that can be modified at runtime through the console, making them useful for debugging, testing, and exposing tunable parameters.
 
 Use CVar nodes to:
 
@@ -18,4 +18,4 @@ CVars are particularly useful during development for tweaking gameplay values, e
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [Console Variables](../../debugging/cvars.md)
+* [Console Variables](../../../debugging/cvars.md)

pages/docs/custom-code/visual-script/nodes/vscript-nodes-debug.md

@@ -2,7 +2,7 @@
 
 ## Debug
 
-Debug nodes provide functionality for [debug rendering](../../debugging/debug-rendering.md), allowing you to visualize information directly in the game viewport. These nodes are invaluable for understanding game logic, troubleshooting issues, and verifying that scripts are working as expected.
+Debug nodes provide functionality for [debug rendering](../../../debugging/debug-rendering.md), allowing you to visualize information directly in the game viewport. These nodes are invaluable for understanding game logic, troubleshooting issues, and verifying that scripts are working as expected.
 
 Common debug rendering operations:
 
@@ -11,7 +11,7 @@ Common debug rendering operations:
 * **Visualize vectors** - Show directions, normals, and rays
 * **Temporary visuals** - Create visual aids that only appear during development
 
-Debug rendering is visible in both the editor and game viewports and can be toggled on/off through the [debug rendering system](../../debugging/debug-rendering.md). Use debug nodes liberally during development to visualize raycasts, AI decisions, trigger volumes, or any other abstract concepts that are hard to understand without visual feedback.
+Debug rendering is visible in both the editor and game viewports and can be toggled on/off through the [debug rendering system](../../../debugging/debug-rendering.md). Use debug nodes liberally during development to visualize raycasts, AI decisions, trigger volumes, or any other abstract concepts that are hard to understand without visual feedback.
 
 Combine debug nodes with [logging nodes](vscript-nodes-log.md) for comprehensive debugging capabilities.
 
@@ -20,5 +20,5 @@ Combine debug nodes with [logging nodes](vscript-nodes-log.md) for comprehensive
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [Debug Rendering](../../debugging/debug-rendering.md)
+* [Debug Rendering](../../../debugging/debug-rendering.md)
 * [Logging Nodes](vscript-nodes-log.md)

pages/docs/custom-code/visual-script/nodes/vscript-nodes-events.md

@@ -2,7 +2,7 @@
 
 ## Event Handlers
 
-Event handlers are nodes that get executed when a certain [message](../../runtime/world/world-messaging.md) is sent to any of the objects that this script is responsible for. All event handlers are *entry points* into the script and most scripts will only execute as a reaction to an event.
+Event handlers are nodes that get executed when a certain [message](../../../runtime/world/world-messaging.md) is sent to any of the objects that this script is responsible for. All event handlers are *entry points* into the script and most scripts will only execute as a reaction to an event.
 
 ## See Also
 

pages/docs/custom-code/visual-script/nodes/vscript-nodes-game-object.md

@@ -2,7 +2,7 @@
 
 ## Game Object
 
-[Game object](../../runtime/world/game-objects.md) nodes provide functionality for working with game objects in the scene hierarchy. These nodes allow you to navigate the object tree, manipulate transforms, and access components.
+[Game object](../../../runtime/world/game-objects.md) nodes provide functionality for working with game objects in the scene hierarchy. These nodes allow you to navigate the object tree, manipulate transforms, and access components.
 
 Common game object operations:
 
@@ -19,7 +19,7 @@ Game object nodes are fundamental to most visual scripts, as they allow you to l
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [Game Objects](../../runtime/world/game-objects.md)
+* [Game Objects](../../../runtime/world/game-objects.md)
 * [Component Nodes](vscript-nodes-component.md)
 * [Prefab Nodes](vscript-nodes-prefabs.md)
 * [Spatial Nodes](vscript-nodes-spatial.md)

pages/docs/custom-code/visual-script/nodes/vscript-nodes-log.md

@@ -2,7 +2,7 @@
 
 ## Log
 
-Logging nodes output messages to the [engine's log system](../../debugging/logging.md), allowing you to track script execution, debug issues, and monitor runtime behavior. These nodes are essential for understanding what your scripts are doing and troubleshooting problems.
+Logging nodes output messages to the [engine's log system](../../../debugging/logging.md), allowing you to track script execution, debug issues, and monitor runtime behavior. These nodes are essential for understanding what your scripts are doing and troubleshooting problems.
 
 Logging features:
 
@@ -18,6 +18,6 @@ Example: A log message with format string `"Player health: {0}, position: {1}"`
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [Logging](../../debugging/logging.md)
+* [Logging](../../../debugging/logging.md)
 * [Debug Nodes](vscript-nodes-debug.md)
 * [String Nodes](vscript-nodes-string.md)

pages/docs/custom-code/visual-script/nodes/vscript-nodes-messages.md

@@ -9,17 +9,17 @@ Message delivery modes:
 * **Direct to component** - Send a message to a specific component
 * **Broadcast to object** - Deliver to all components on a game object
 * **Recursive broadcast** - Send to an entire sub-tree of objects and components
-* **Event mode** - Deliver *upwards* along the parent chain to the closest handler (see [event messages](../../runtime/world/world-messaging.md#event-messages))
+* **Event mode** - Deliver *upwards* along the parent chain to the closest handler (see [event messages](../../../runtime/world/world-messaging.md#event-messages))
 
 The `Send Mode` property controls how messages propagate through the hierarchy. When set to *Event*, messages travel upward through parent objects until a component handles them, enabling event bubbling similar to UI event systems.
 
-Message nodes are essential for decoupled communication. Instead of directly calling functions on other components, you send messages that any component can choose to handle. This keeps scripts flexible and reusable. See the [world messaging documentation](../../runtime/world/world-messaging.md) for a comprehensive guide to the messaging system.
+Message nodes are essential for decoupled communication. Instead of directly calling functions on other components, you send messages that any component can choose to handle. This keeps scripts flexible and reusable. See the [world messaging documentation](../../../runtime/world/world-messaging.md) for a comprehensive guide to the messaging system.
 
 ## See Also
 
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [World Messaging](../../runtime/world/world-messaging.md)
+* [World Messaging](../../../runtime/world/world-messaging.md)
 * [Event Handler Nodes](vscript-nodes-events.md)
 * [Game Object Nodes](vscript-nodes-game-object.md)

pages/docs/custom-code/visual-script/nodes/vscript-nodes-physics.md

@@ -2,7 +2,7 @@
 
 ## Physics
 
-Physics nodes provide access to the [Jolt physics engine](../../physics/jolt/jolt-overview.md) from within visual scripts. These nodes allow you to perform physics queries, apply forces, and interact with physics actors and shapes.
+Physics nodes provide access to the [Jolt physics engine](../../../physics/jolt/jolt-overview.md) from within visual scripts. These nodes allow you to perform physics queries, apply forces, and interact with physics actors and shapes.
 
 Common physics operations include:
 
@@ -11,12 +11,12 @@ Common physics operations include:
 * **Force application** - Apply forces and impulses to dynamic physics actors
 * **Physics queries** - Query physics properties and collision information
 
-These nodes are essential for gameplay mechanics that involve physics interactions, such as shooting, throwing objects, detecting ground contact, or implementing custom physics-based behaviors. Use them in combination with [dynamic actors](../../physics/jolt/actors/jolt-dynamic-actor-component.md), [triggers](../../physics/jolt/actors/jolt-trigger-component.md), and [collision shapes](../../physics/jolt/collision-shapes/jolt-shapes.md).
+These nodes are essential for gameplay mechanics that involve physics interactions, such as shooting, throwing objects, detecting ground contact, or implementing custom physics-based behaviors. Use them in combination with [dynamic actors](../../../physics/jolt/actors/jolt-dynamic-actor-component.md), [triggers](../../../physics/jolt/actors/jolt-trigger-component.md), and [collision shapes](../../../physics/jolt/collision-shapes/jolt-shapes.md).
 
 ## See Also
 
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [Jolt Physics Overview](../../physics/jolt/jolt-overview.md)
-* [Jolt Actors](../../physics/jolt/actors/jolt-actors.md)
+* [Jolt Physics Overview](../../../physics/jolt/jolt-overview.md)
+* [Jolt Actors](../../../physics/jolt/actors/jolt-actors.md)

pages/docs/custom-code/visual-script/nodes/vscript-nodes-prefabs.md

@@ -2,7 +2,7 @@
 
 ## Prefabs
 
-[Prefabs](../../prefabs/prefabs-overview.md) are reusable templates for game objects. Prefab nodes provide functionality to dynamically instantiate prefabs at runtime from within visual scripts.
+[Prefabs](../../../prefabs/prefabs-overview.md) are reusable templates for game objects. Prefab nodes provide functionality to dynamically instantiate prefabs at runtime from within visual scripts.
 
 
 Common use cases include spawning enemies when a player enters an area, creating projectiles when a weapon fires, or instantiating effects like explosions and particles. Combine prefab spawning with [game object nodes](vscript-nodes-game-object.md) to further manipulate the spawned instances.
@@ -12,5 +12,5 @@ Common use cases include spawning enemies when a player enters an area, creating
 * [Visual Script Class Asset](../visual-script-class-asset.md)
 * [Visual Script Overview](../visual-script-overview.md)
 * [Script Component](../script-component.md)
-* [Prefabs Overview](../../prefabs/prefabs-overview.md)
+* [Prefabs Overview](../../../prefabs/prefabs-overview.md)
 * [Game Object Nodes](vscript-nodes-game-object.md)