> For the complete documentation index, see [llms.txt](https://conusyntax.gitbook.io/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://conusyntax.gitbook.io/products/widget-blueprints/wbp_dropdownbutton.md).
# WBP\_DropdownButton
Allows players to select from a predefined list of options.
#### Behavior
Each **Dropdown Button** is driven by a **Gameplay Tag** (e.g., `CharacterCreator.Gender`, `CharacterCreator.Race`, or `CharacterCreator.Groom.Hairstyle`). This tag serves two primary purposes:
1. **Automatic Initialization**: The dropdown reads the tag to determine which list of options to generate.
2. **Logic Execution**: It defines which internal function to trigger when the player selects an option from the list.
#### Initialization
The widget is set up in the Initialize **Dropdown Button** collapsed graph. During this phase, the system identifies the assigned Gameplay Tag and populates the dropdown with the corresponding data:
* **Gender**: Populates the list with Gender options.
* **Race**: Populates the list with Race options.
* **Hairstyle**: Populates the list with available Groom Assets.
#### Using the Dropdown Button
1. Place a **WBP\_DropdownButton** widget.
2. In the **Details**, go to **Button** ➞ **Attributes**.
3. **Set** **Gameplay Tag**: Assign the Gameplay Tag that corresponds to the data you want this dropdown to control.
{% hint style="warning" %}
If no Gameplay Tag is assigned, the dropdown will not be able to fetch data and will fail to function correctly.
{% endhint %}
### Available Functions
The blueprint contains a library of functions to support various data types. Ensure your Gameplay Tag is connected to the corresponding nodes in the **WBP\_DropdownButton** graph:
#### Set Functions (Execution)
These apply the selected data to the Character.
#### Initialize Functions (Setup)
These define what appears in the list.
