> For the complete documentation index, see [llms.txt](https://docs.sickscripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sickscripts.com/shared-framework/sickdirtycops-1/installation.md).

# Usage

Each Spot will have a check! You must complete a step before accessing some spots!&#x20;

Target is Disabled until you are done with animations to help prevent spamming&#x20;

Multiple checks for `if amount > money then` to make sure you aren't using an amount more than what you actually have! This also helps preventing players from starting a wash cycle and dropping the money. Server side checks right before payout make sure you actually have the amount in your Pockets. If not it will not continue if you do have the amount it will process the dirty money into clean money while applying a tax or "fee". Checks for money when washing to make sure you have that amount before starting the cycle.&#x20;

When first entering Money wash you will need to make sure to kick on the power to make the target points for the other steps!


---

# 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://docs.sickscripts.com/shared-framework/sickdirtycops-1/installation.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.
