> For the complete documentation index, see [llms.txt](https://tutorial.feuniverse.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorial.feuniverse.us/nightmare/appendix.md).

# Appendix: Nightmare Module Format

NMM format: # at line\[0] means comment, ignore it. blank lines are ignored also. decimal is assumed, 0x for hex, 0 for octal (0b for binary?)

```
Line 1: file version, ignore it.
Line 2: file description, ignore it.
Line 3: address of table, no 0800:0000h
Line 4: number of entries Line 5: length of each entry
Line 6: text file of entry names, might be useful. Default to numbers if not found
Line 7: tbl file for text, ignore it.
```

Entry format:

```
Line 1: Description (use as header row?)
Line 2: Offset
Line 3: Length in bytes
Line 4: Type of data (Only care about H or DU/DS imo)
Line 5: Text file for descriptions, ignore it for now.

NEHU: Numeric Editbox Hexadecimal Unsigned
NEDU: Numeric Editbox Decimal Unsigned
NEDS: Numeric Editbox Decimal Signed
NDHU: Numeric Dropdown Hexadecimal Unsigned
NDDU: Numeric Dropdown Decimal Unsigned
```


---

# 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://tutorial.feuniverse.us/nightmare/appendix.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.