> For the complete documentation index, see [llms.txt](https://docs.vezel.dev/novadrop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vezel.dev/novadrop/tools/rc.md).

# novadrop-rc

```
novadrop-rc <command> <arguments...> [options...]
```

The novadrop-rc tool allows manipulation of TERA's resource container files. It supports the following tasks:

* Extraction of files contained within resource container files.
* Packing of files to a fresh resource container file usable by the client.
* Format integrity verification of resource container files, optionally with strict compliance checks.

## novadrop-rc pack

```
novadrop-rc pack <input> <output> [options...]
```

Packs the files in a directory to a resource container file.

The `input` argument specifies a directory containing files. The `output` argument specifies the path of the resulting resource container file.

| Option                   | Description                                                     |
| ------------------------ | --------------------------------------------------------------- |
| `--encryption-key <key>` | Specifies an encryption key (defaults to the latest known key). |

## novadrop-rc repack

```
novadrop-rc repack <input> <output> [options...]
```

Repacks a resource container file without unpacking to disk. This command is primarily useful for development of novadrop-rc.

The `input` argument specifies the input resource container file. The `output` argument specifies the path of the resulting resource container file.

| Option                   | Description                                                           |
| ------------------------ | --------------------------------------------------------------------- |
| `--decryption-key <key>` | Specifies a decryption key (defaults to the latest known key).        |
| `--encryption-key <key>` | Specifies an encryption key (defaults to the latest known key).       |
| `--strict`               | Enables strict format compliance checks while reading the input file. |

## novadrop-rc unpack

```
novadrop-rc unpack <input> <output> [options...]
```

Unpacks the files in a resource container file to a directory.

The `input` argument specifies the input resource container file. The `output` argument specifies the path of the directory to extract files to.

| Option                   | Description                                                           |
| ------------------------ | --------------------------------------------------------------------- |
| `--decryption-key <key>` | Specifies a decryption key (defaults to the latest known key).        |
| `--strict`               | Enables strict format compliance checks while reading the input file. |

## novadrop-rc verify

```
novadrop-rc validate <input> [options...]
```

Verifies the format integrity of a resource container file. This means loading all contained files into memory and verifying that no errors occur.

The `input` argument specifies the input resource container file.

| Option                   | Description                                                           |
| ------------------------ | --------------------------------------------------------------------- |
| `--decryption-key <key>` | Specifies a decryption key (defaults to the latest known key).        |
| `--strict`               | Enables strict format compliance checks while reading the input file. |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vezel.dev/novadrop/tools/rc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.