# Arg

### Signature

```
{arg:[id],[minChar],[minHPos]}
```

### Description

Displays the name of a character, action, item, and more.

The displayed text differs based on the `argXType` header option of a dialog entry.

```
{dialog 0, arg0type=8}
You have cast {arg:0,0,0}.
{/dialog}
```

This dialog could translate to `You have cast Cure.` where as the displayed action is determined by the function that retrieves this text while the arg type defines that the argument is an action.

For a full list of arg types, you can view the following page: [#arg-type](https://xeavin.gitbook.io/the-insurgents-handbook/formats/st2e8#arg-type "mention").

### Arguments

#### Identifier

The argument type identifier of the argument (0 -> 15).

#### Minimum Characters

If higher than 0, add `x - y` tabs (`\t`) after this tag where as `x` is the character count of the resolved character, action, etc. name and `y` is the value of this argument (0 -> 15).

#### Minimum Horizontal Position

If higher than 0, add [h-pos-min-cur](https://xeavin.gitbook.io/the-insurgents-handbook/text/text-tags/h-pos-min-cur "mention")(0) before and [h-pos-min-cur](https://xeavin.gitbook.io/the-insurgents-handbook/text/text-tags/h-pos-min-cur "mention")(x) after this tag where as x is the value of this argument (0 -> 127).

### Notes

{% hint style="warning" %}
This tag doesn't display the plural form of an object (e.g. item), use the [item](https://xeavin.gitbook.io/the-insurgents-handbook/text/text-tags/item "mention") tag for that instead.
{% endhint %}

{% hint style="info" %}
This tag is only usable in a text file with the format **st2e8** (e.g. battle messages).
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://xeavin.gitbook.io/the-insurgents-handbook/text/text-tags/arg.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.