# Getting Started

This section introduces the core capabilities and directory layout of DLC Manager, and explains the common `dc` conventions used by configuration files.

## This Wiki only support Version `3.6.0` and above of DLC Manager.

## Introduction
DLC Manager allows modpack developers to manage mods, resource packs, data packs, and more via configuration files. It supports enable/disable, download and update workflows, plus presets, notices, and redirects. This documentation targets modpack developers and uses formal explanations with practical examples.

## Directory Layout
It is recommended to create a `DLC/` directory at the modpack root (can be changed in config):

```
DLC/
  remote/               # Remote DLC configs (auto-download)
  required/             # Required resources (forced/mandatory)
  preset/               # Preset configs
  info/                 # Info files (auto or manual)
  update/               # Update packages
  remote/redirect/      # Redirect configs (optional, not auto-created)
```

## Config Format (DC)
- `.dc` is the default config file extension for DLC content configs.
- Most configs are table-based (TOML-like), for example `[basic]`, `[DisplayName]`, `[tip]`.
- Keys are case-insensitive while loading.
- Multi-line strings are supported with triple quotes:

```dc
en_us = """Line 1
Line 2
"""
```

- DLC Manager runtime config files are also `dc`:
  - `config/dlc_manager/config.dc` (client)
  - `config/dlc_manager/config-server.dc` (server)

## Quick Start (Basic Usage)
1) Create `DLC/` under the modpack root (or set `dlcRoot` in config).
2) **Drag mod files directly** into `DLC/`.
3) Enter the game and open DLC Manager to apply and manage content.

## Key Concepts
- **identifier**: The primary logical identifier used by prerequisites, presets, and conflicts. Keep it stable.
- **file_name**: The DLC file name (including extension); can differ from display name.
- **DisplayName / tip**: Localized display text.
- **appliedTarget**: Target directory (e.g., `mods`, `resourcepacks`, `datapacks`, `tacz`) that determines the application location.

## FAQ
- **Why doesn’t a config take effect?**
  - Ensure the file extension is `.dc`.
  - Ensure the config is in the correct folder (`DLC/remote`, `DLC/required`, etc.).
  - Ensure `identifier` is not empty.
- **Why doesn’t the display name match my config?**
  - If DisplayName is missing or the language does not match, it falls back to the file name.

> For full configuration details, continue to the Basic and Advanced sections.