> 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/thicc-pro/whats-new-in-thicc-pro.md).

# What's new in Thicc Pro?

Thicc Pro is the peptide-filled big brother of [Thicc Stroke](https://www.plugineverything.com/thiccstroke). We've injected the following features:

* Full 3D & Camera support
* Apply natively to text layers, masks and shape layers
* GPU accellerated MFR, realtime playback: 4k @ 30fps on Macbook M3
* Powerful inbuilt repeater, change any value per copy
* Flat or round pen shapes with round, projecting or butt cap styles
* Custom graph UI for fine-grained control over variable thickness
* 32bpc HDR colors, higher fidelity aliasing, corners & caps
* Dashes & gradients per dash, dots
* Robust handling of animated & overlapping paths


---

# 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/thicc-pro/whats-new-in-thicc-pro.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.