> 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/installation.md). # Installation Install Clean Posters +18 on a FiveM server. ### 1. Download the resource Get Clean Posters +18 from the DrFx Tebex store using your CFX account. ### 2. Upload the files Extract the download and upload the resource folder into your server's resources directory. Keep the supplied folder name. ### 3. Start the resource Add the resource to server.cfg using an ensure line that exactly matches the installed folder name. ### 4. Restart the server Restart the server completely instead of restarting only the resource. ### 5. Verify the result Visit several locations that previously displayed inappropriate posters and confirm the replacement is active. Check the client and server consoles if an asset does not load. --- # 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/installation.md?ask=&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.