> 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/products/drfx-visual-fivem-server-graphics-pack/included-modules.md).

# Included Modules

What each DrFx Visual module changes.

DrFx Visual is delivered as a modular graphics package. Enable the modules that match the look you want for your server.

### DrFx\_Visual

Core visual and timecycle adjustments that define the main DrFx look.

### DrFx\_Clouds

Cloud and sky enhancements for a more consistent atmosphere.

### DrFx\_Grounds 1 & 2

Terrain and ground texture improvements across supported parts of the map.

### DrFx\_LARoads 1–4

Custom road textures split into multiple resource folders for coverage and easier management.

### DrFx\_Lights

General lighting adjustments for supported world and environmental lighting.

### DrFx\_Streetlights

Streetlight changes designed to improve the nighttime appearance of the map.

### Choosing modules

Test the full package first. If another map or visual resource conflicts with a specific module, disable only the overlapping module and test again.


---

# 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/products/drfx-visual-fivem-server-graphics-pack/included-modules.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.