> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/script-type-function-block-commands/script-type-function-block-command-comment.md).

# Script Type Function Block Command: Comment

### Command Description

Comments are used to describe the behavior of other commands or portions of a function block script. They are useful for making a script more readable and can be helpful in debugging. Comments are always shown in green for greater visibility.

While listed with other commands, they do not actually cause Vehicle Spy to take any action, and are simply skipped when encountered. Comments are also added to a script in a special way: you enter them in the special **Comment** column, rather than selecting **Comment** in the **Description** column.

There are two types of comments: those that document other commands, and standalone comments that appear by themselves on a line. Comments on other commands are typically short and explain what that step does; examples can be seen in steps 1, 3 and 4 in Figure 1. Standalone comments describe or visually separate blocks of commands in large scripts, like step 2 in the figure.

![Figure 1: Comments on commands and standalone comments.](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/of1l9NgQBENLMiSep6wB/spyFBComment.gif)

### Entering a Comment on Another Command

To add a comment to another command, simply enter it into the **Comment** field of that command. The "//" prefix visually separates the comment and is added automatically by Vehicle Spy.

### Entering a Standalone Comments

To create a standalone comment, enter it into the **Comment** field of a blank step. When you are finished, Vehicle Spy will add the "//" prefix and then move the comment over to the **Description** field, showing that the step is only a comment with no other command. Note that if you want to edit the comment, double-click in the **Comment**field for the step, not the **Description** field.

If you edit the **Description** column of a step that has a standalone comment in it in order to choose a different command, then rather than deleting the existing comment, Vehicle Spy will move it to the **Comment** column for you.

### Value Field Parameters

None.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/script-type-function-block-commands/script-type-function-block-command-comment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.