---
title: Add a setting
product: Advanced Framework Pro
version: 1.0
engine: Unreal Engine 5.8
updated: 2026-10-05
canonical: https://docs.human-codeable.com/workflows/add-setting.html
---

# Add a setting

By the end of this you will have a new entry on a settings page, reading and writing a value of your own.

## Steps

1. Pick the base class matching your value type: `BP_Value_Settings_Bool`, `_Float`, `_Integer`, `_Name`, or one of the console-variable variants such as `BP_Value_Settings_Integer_Console`.
2. Create a Blueprint deriving from it, in your own project content.
3. Set **Name** and **Caption** — these become the label and helper text on the row.
4. For a console-variable setting, set the console variable name and the value mapping.
5. Open the settings page the entry belongs on: `WBP_Settings_Desktop_Graphics`, `WBP_Settings_Desktop_Sound` or `WBP_Settings_Desktop_Gameplay`.
6. Add the row widget matching your value type — `WBP_SettingItem_Boolean_Toggle`, `WBP_SettingItem_Float_Slider`, `WBP_SettingItem_Integer_Selector`, `WBP_SettingItem_Name_DropDown` or `WBP_SettingItem_Color_Picker` — and place it in the page's vertical box alongside the existing rows.
7. Select the row and set its **Settings** class to the Blueprint from step 2. This is the step that connects the two: leave it unset and the row has nothing to read from or write to.
8. Optionally set **Slot Horizontal Alignment** on the row to control how its control sits beside the title and caption.

[![A settings preset asset](../images/howto_addsetting_01-1600.webp?v=f1a3f8b8)](../images/howto_addsetting_01-1600.webp?v=f1a3f8b8)

A settings preset asset

[![The row placed on the graphics page with its Settings class picked](../images/howto_addsetting_02-1600.webp?v=76cc6471)](../images/howto_addsetting_02-1600.webp?v=76cc6471)

The row placed on the graphics page with its Settings class picked

[![The new setting in the menu](../images/AFM_Settings_result-1600.webp?v=cb64a40d)](../images/AFM_Settings_result-1600.webp?v=cb64a40d)

The new setting in the menu

## Notes

### There is no separate registration step

The row's **Settings** class *is* the registration. `BPC_GameState_Settings.getObjectForSettings` builds the value object the first time a row asks for that class, runs its `Init`, and caches it — so two rows pointing at the same class share one object and stay in sync without any wiring.

The component's own `Settings` map is that runtime cache, not an authoring list. There is nothing to fill in on the game state.

### Pick the row subclass yourself

Nothing infers the control from the value type. A boolean needs `WBP_SettingItem_Boolean_Toggle`, a float needs `WBP_SettingItem_Float_Slider`, and pairing a float value with a toggle row simply gives you a row that cannot represent its own value.

### One set of pages serves both menus

The shipped pages are named for the desktop — `WBP_Settings_Desktop_Graphics` and its siblings — but both the VR and the desktop menu build themselves from the same `Pages` list on `BPC_Pawn_Menu`, so a row you add once appears in both. A new category is more work: it means adding a page widget to `WBP_Settings_Desktop` and a tab button to switch to it.

Tip

Look at the assets under `AFM_Settings/Blueprints/Presets` for worked examples of every value type, and at `WBP_Settings_Desktop_Graphics` for how a page of rows is laid out.

Warning

Persistence is not automatic. `LoadSettings` has to be called as play begins, and values reach the save slot only when `SaveAllSettings` runs — the save button on `WBP_Settings_Desktop` is an empty handler in the shipped widget. `ApplyDefaultsOnStartup` on the settings component is also inert: nothing reads the list, so filling it in has no effect on its own.