> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/troubleshooting/compiler-diagnostic-catalog/lexer-warnings-gpc10xx.md).

# Lexer warnings (GPC10xx)

### GPC1000 — Unexpected Character

```
Unexpected character '{char}' will be ignored.
```

**Severity:** Warning

The scanner encountered a character that is not part of any GPC token (for example a stray `@` or a non-ASCII symbol outside a string or comment). The character is skipped and scanning continues, so this alone never fails a build — but it usually points at a typo or pasted content that will also confuse the parser.

***

### GPC1001 — Number Will Be Truncated

```
The value '{value}' is out of range for integer values. It will be truncated to {truncated} after first having been rounded to {rounded}.
```

**Severity:** Warning

A floating-point literal (including scientific notation like `1e12`) rounds to an integer that does not fit the target integer width (16-bit or 32-bit depending on script mode). The compiler first rounds the value, then masks it down to fit, so the constant your script actually uses is `{truncated}` — usually not what was intended.

***

### GPC1002 — Number Will Be Rounded

```
The value '{value}' will be rounded to {rounded}.
```

**Severity:** Warning

GPC has no floating-point type. A decimal literal such as `1.5` is rounded to the nearest integer at scan time. If you need fractional precision, scale the value (e.g. work in tenths) instead.

***

### GPC1003 — Too Many Bits (16-bit)

```
Too many bits specified. Expected 1 - 16 got {count}. Value: '{value}'
```

**Severity:** Warning

A binary literal (`0b...`) in a 16-bit script specifies more than 16 binary digits. The value is still parsed if it fits numerically; otherwise GPC1108 follows.

***

### GPC1004 — Too Many Bits (32-bit)

```
Too many bits specified. Expected 1 - 32 got {count}. Value: '{value}'
```

**Severity:** Warning

Same as GPC1003, but for 32-bit scripts: a binary literal with more than 32 digits.

***

### GPC1006 — Unterminated String (End of File)

```
Unterminated string detected. The leading '"' character will be ignored: {text}
```

Or:

```
Unterminated string: {text}
```

**Severity:** Warning

The scanner reached the end of the file while inside a string literal — the closing `"` is missing. This is the warning-severity variant, emitted when the compiler can recover from the unterminated string; normally the error variant GPC1102 is emitted instead. In recovery mode the leading quote is discarded and scanning resumes right after it.

***

### GPC1007 — Unterminated String (Newline)

```
Unterminated string detected. The leading '"' character will be ignored: {text}
```

Or:

```
Unterminated string: {text}
```

**Severity:** Warning

Same as GPC1006, but the string was broken by a line break: GPC strings cannot span multiple lines. Warning-severity variant of GPC1103.


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/troubleshooting/compiler-diagnostic-catalog/lexer-warnings-gpc10xx.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.