> For the complete documentation index, see [llms.txt](https://plugin-everything.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plugin-everything.gitbook.io/docs/contact-and-support.md).

# Contact & Support

If you require assistance with anything that’s not listed here, or something is not clear, feel free to contact us in the following ways

## Contact Us

<details>

<summary>I Need Technical Support</summary>

**Help us help you by including as much information as possible**

* `GPU hardware specs including driver version`
* `AE / AME version`
* `Operating System version`
* `Plugin version`
* [Error logs](#error-logging)

<div data-with-frame="true"><figure><img src="/files/4OagpOGcKy692h8mp8j2" alt="" width="375"><figcaption></figcaption></figure></div>

Please screenshot the `About & Support` group so we can see the plugin version, OS, GPU, and driver information.

{% hint style="info" %}
Images and video screen capture can also be very helpful for us to diagnose the issue, as well as the contents of your error log.
{% endhint %}

[Submit Support Ticket Here](https://aescripts.com/contact/) (enter any search term and click "no i want to open a ticket")

or

[Email Support Here](mailto:hello@plugineverything.com)

</details>

<details>

<summary>I Have a Feature Request</summary>

#### I Have a Feature Request

Send feature ideas, workflow questions, or result examples through [Plugin Everything contact](https://www.plugineverything.com/contact).

Screenshots, short videos, and example project descriptions are especially helpful when you are asking whether a specific look or workflow is possible.

</details>

## Error Logging

Thicc Pro writes local error reports to a file named `thicc_pro_error_log.txt`. If you're experiencing any issues with Thicc Pro such as instability or unexpected results, the log can be invaluable in diagnosing the cause.

* You can check the log is working by clicking `Create Test Error`
* Click `Open Log Directory` to view the location of the log
* Click `Open Error Log` to open the log with your default text editor
* Thicc Pro will never “phone home” or attempt to send logs over your network

<details>

<summary>Log Locations</summary>

#### Log Locations

On Windows, the log is stored here:

```
C:\Users\<YourUsername>\AppData\Local\PluginEverything\thicc_pro_error_log.txt
```

On macOS, the log is stored here:

```
/Users/<YourUsername>/Library/Logs/PluginEverything/thicc_pro_error_log.txt
```

Thicc Pro creates the `PluginEverything` folder automatically when it writes the first log entry.

</details>

<details>

<summary>Troubleshooting the Error Log</summary>

#### Troubleshooting the Error Log

If you can't find or open the log:

* Click `Open Log Directory` from `About & Support`
* Click `Create Test Error` to force Thicc Pro to create the log file
* Close the log in other apps if new entries stop appearing
* If `Open Error Log` does not open the file, use `Open Log Directory` and open it manually

Windows hides `AppData` by default. To show hidden items:

1. Open File Explorer
2. Click the `View` tab
3. Enable `Hidden items`

macOS hides `Library` by default. To show hidden files in Finder, press `Command` + `Shift` + `.`.

{% hint style="info" %}
Not every logged error is critical. Some entries are diagnostic context that helps support understand what happened.
{% endhint %}

</details>


---

# 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://plugin-everything.gitbook.io/docs/contact-and-support.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.