> For the complete documentation index, see [llms.txt](https://drfx-store.gitbook.io/drfx-store-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://drfx-store.gitbook.io/drfx-store-docs/documentation/resources-and-guides/clean-posters-+18/scope-and-updates.md).

# Scope & Updates

What the cleanup covers and how future updates are handled.

### What the resource does

Clean Posters +18 removes a large number of inappropriate posters from the GTA V world by replacing supported map assets.

### Coverage

The package targets many known poster locations. Coverage can vary when another map resource replaces the same assets or when GTA V map content changes.

### Future updates

Additional posters may be removed in future releases. Check the DrFx store and Discord for release notes and updated downloads.

### Updating safely

1. Back up the installed resource.
2. Download the latest version through Tebex.
3. Replace the old resource files with the new package.
4. Keep the original folder name and ensure line.
5. Restart the server and verify several affected locations.


---

# 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://drfx-store.gitbook.io/drfx-store-docs/documentation/resources-and-guides/clean-posters-+18/scope-and-updates.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.
