# Script Assets

![](https://3597805814-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3XSZSwWow0fDf6fQJobd%2Fuploads%2Fgit-blob-f8026e673fb0216332b8ec2e21dd7dd852a8f072%2Fscripteditor_assets.png?alt=media)

The Assets panel in the script editor is where you view and manage the various files and resources that are part of your script.

* Packaged scripts (those with a `.osp` suffix) support multiple script code files (each of which can contain embedded resources like dialogs and strings), and image and icon files.
* Single file scripts (i.e. a `.js` or `.vbs` file) supported embedded resources.

The panel has three tabs (two in the case of single file scripts):

* **Scripts**: Lists the individual code files that make up this script. For a single file script, this list will contain just a single item (the file itself). A packaged script can contain multiple code files, and they will be listed separately. Each individual code file can be split up into [modules](https://chaoses-ib.gitbook.io/directory-opus/manual/scripting/script_add-ins/modules), and these are shown indented under their primary file.
* **Resources**: Shows any dialogs or language string sets that have been embedded in any of the code files that make up the script.
* **Other**: For script packages, shows any icon sets or image files that the package contains.

To add or manage assets a script's assets, right-click on the item in question, or use the commands in the *Assets* drop-down menu.


---

# 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://chaoses-ib.gitbook.io/directory-opus/manual/scripting/script_editor/assets.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.