Tag To

This function block is used to retrieve a value broadcast by a matching Tag From block elsewhere in the same scenario. It provides a simple text field to specify the shared tag name and exposes the received data through a generic socket.

📥 Inputs

This function block does not have any inputs.

📤 Outputs

Generic This socket outputs the value provided by the matching Tag From block.

🕹️ Controls

Tag Single-line text field where you enter the tag name that identifies which Tag From block to retrieve data from. The tag must exactly match the tag used in the corresponding Tag From block.

🎯 Features

• Simple variable exchange across the scenario using human-readable tags.

• Automatic lookup: when the block runs it searches for a Tag From block with the same tag and returns its current value.

• Visual feedback: if no matching Tag From block is found, the block reports an error and indicates an invalid state to help you spot configuration issues.

⚙️ Running mechanism

When executed, the block looks for a Tag From block in the same scene whose tag matches the text entered in the Tag control. If a matching Tag From is found, this block outputs the value provided by that Tag From. If no match is found, the block marks itself as invalid and logs an error to help you correct the tag pairing.

📝 Usage Instructions

1. Place a Tag From block where a value is created or stored.

2. In this block, enter the exact same tag string into the Tag field.

3. Use the block's Generic output to feed the retrieved value into downstream blocks.

This pattern is useful for passing data between different parts of a scenario without direct wiring.

💡 Tips and Tricks

• Always pair this block with Tag From. The two together let you move values across different branches or subsystems.

• Use descriptive tag names (for example, "last_count" or "camera_status") to avoid collisions and make scenarios easier to understand.

• Combine with Data Write Local / Data Read Local or Data Write Global / Data Read Global when you need shared state persistence beyond simple momentary transfer.

• Use Debug Input to inspect values produced by Tag From during development and troubleshoot mismatched tags.

🛠️ Troubleshooting

• If the block shows an error about a missing tag, verify that a Tag From block with the exact same tag string exists in the same scene.

• Ensure there are no extra spaces before or after the tag text in the Tag field.

• If multiple Tag From blocks share the same tag, the first matching block found will be used — keep tag names unique when possible to avoid ambiguity.