> For the complete documentation index, see [llms.txt](https://luffyyy.gitbook.io/beardlib/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://luffyyy.gitbook.io/beardlib/modules/dlcmodule.md).

# DLC

Updated for version 3.38.

This page is incomplete.

## Module Definition

The module is inherited from [ModuleBase](https://luffyyy.gitbook.io/beardlib/modules/modulebase). So base parameters can be found there.

Let's you make a DLC.

### Module name

The name of the module you use as the meta of the module definition is 'DLC' or 'DLCModule' if `_force_search` is set to true in the module definition.

### XML Structure

```markup
<DLC id>
    <content loot_global_value>
        <loot_drops/>
        <upgrades/>
    </content>
</DLC>
```

#### `<DLC id>`

| Parameter | Type   | Description       |
| --------- | ------ | ----------------- |
| id        | String | The ID of the DLC |

#### `<content loot_global_value ...>`

| Parameter           | Type   | Description                           |
| ------------------- | ------ | ------------------------------------- |
| loot\_drops         | Table  | Items that can drop (use value\_node) |
| upgrades            | Table  | ...                                   |
| loot\_global\_value | String | The global value of this DLC.         |

### Example

This example is what you would put inside your main node within your [mod config](https://github.com/GreatBigBushyBeard/PAYDAY-2-BeardLib/wiki/Module-Config)

```markup
<DLC id="beard"/>
```

This will add a DLC named beard.


---

# 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://luffyyy.gitbook.io/beardlib/modules/dlcmodule.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.