Modular Options Menu by KarlRamstedt - 1

Games & Projects

A menu template and underlying system for use in the game engine Unity.

Unknown VersionGNU General Public License v3.0Updated 1 day agoCreated on January 10th, 2020
Go to source

Modular Options Menu

A menu template and underlying system for use in the game engine Unity.

This project aims to help users avoid the pain often involved in haphazard, hardcoded menu systems developed due to time-constraints or lack of interest.


  • Fully modular - All options can be used by themselves or in any combination, without the need to ever touch the code.
  • Easy to use - Editor scripting automatically assigns variables for you and displays data in a user-friendly way.
  • Flawless performance - Entirely event-based. No part in the project has continuous execution (like Update()).
  • Flexible menu template - Easily changed and expanded. Adding a new option can be completed in seconds!
  • Full controller and keyboard & mouse support - All parts of the system support navigation in whichever way the user finds suitable.
  • Lots of included options - About 30 reference option implementations provided in the package.
  • Easily extensible - New option scripts can be created with just a few lines of code. Literally 1 line of code (excluding class and function declaration) if you don’t need references!
  • Supports external Assets - All options support TextMeshPro and reference option implementations are included for PostProcessingStackV2 and Aura.
  • Support for URP and HDRP - Reference implementations for most of the post-processing effect controls are included.
  • Lots of utility scripts - UI interaction sounds, slider value display, scene reference attribute and more included.


Just add the project folder to your Assets folder.

Supported Unity versions

The MenuTemplate uses Unity’s new prefab system, which requires 2018.3 to function. Other than that most of the scripts should work all the way back to even version 5.

Supported Render Pipelines

Both Universal and HighDefinition Render Pipelines are supported. Not all options are exposed to scripting (I assume they will be, Render Pipelines are still in active development), but reference implementations of most of the available options are included.

External asset support

CheckForExternalAssets.cs checks if external namespaces exist and compiles scripts accordingly. The moment you add any of the supported assets the options should recompile to support them. Currently supported assets:

How to use

Most information can be gleaned from the MenuTemplate prefab, so it’s highly recommended to give that a look.

All the option classes can be added through the “Add Component” Menu, under “Modular Options”.

The option classes should be added on the same GameObject as the UI-element they are supposed to work with. Then just add any external references needed by the option (e.g. PostProcessing options require references to profile assets containing option data). That’s it. You now have a working option. Configure the values presented to the user through the UI-element class(e.g. Dropdown) itself, and set the default value in the option class, along with any potential option-name changes you wish to make.

If you wish to include added options in the Restore Defaults Button you can either manually add these or clear and automatically add options by clicking the cog-icon on the RestoreDefaultsButton and clicking “Auto-Fill Parent-Sibling Options” (success depends on menu hierarchy; it will work on the MenuTemplate).

Now for the more fancy part: OptionPresets allow you to change any number of options through a single one. All options (except a few screen-related ones intentionally excluded) can be added to OptionPresets. Set up your options as you normally would, then reference all the Options you wish to control with the preset. The menu template contains a graphics preset you can look at for illustrative purposes. The OptionPreset class has a custom Editor to make keeping track of values easier. It exclusively uses SerializedProperties, and should handle data like any native Unity property in the Editor. Example images of the custom Editor:

Tips & Tricks

  • Changing color of your UI-elements is easy if you’re using the included option template prefabs; Just change the color settings on the UI-element component on the Option prefab and it’ll apply to all elements using that prefab!
  • Setting up explicit navigation is recommended if you have enough options to make menus activate scrolling as Unity’s Automatic navigation can be wonky.

Changing save-system

The system uses Unity’s PlayerPrefs by default. This can be swapped by changing the contents of the class OptionSaveSystem found at the bottom of OptionBase.cs.

Extending the option system

If you already have public properties or functions for manipulating the option values in your scripts you can make use of the ExternalOptions. The only requirement is that the function/property accepts the data-type used by the UI-element as input (float for Sliders, int for Dropdowns and bool for Toggles). Just click the + button on the ExternalOption, drag a reference to the class you wish to modify and select the function that modifies the option, just make sure you’re using the Dynamic float/int/bool version of the function to properly pass on the input value.

If you lack these public properties/functions or simply wish to have dedicated option classes, you can easily extend the system by inheriting from one of the 3 option base classes: SliderOption, DropdownOption and ToggleOption (all part of the ModularOptions namespace). Which is done by replacing MonoBehaviour in the script with one of those 3.

Basic structure of an option script:

public ClassToModify reference; //Assigned through the UnityEditor

protected override void ApplySetting(float _value){
	reference.value = _value;

If you need to grab the reference through code you should do so in Awake(), like this:

protected override void Awake(){
	reference = CodeThatReturnsReference();

Calling base.Awake() after to ensure proper initialization.

But ultimately, the easiest way to create new option scripts is simply to copy existing option scripts with the functionality you want and just changing which values it modifies. All the basic option structures are present in the reference implementations included:

Basic DropdownOption.

DropdownOption where the option has a separate variable controlling ‘On’/‘Off’ state; index 0 acts as ‘Off’.

Basic SliderOption, with comments on how to override slider text formatting.

SliderOption where the option has a separate variable controlling ‘On’/‘Off’ state; 0 acts as ‘Off’.

Basic ToggleOption.


Copyright © 2020 Karl Ramstedt
SPDX-License-Identifier: GPL-3.0-or-later

Summary: You are free to copy, modify and distribute the code under the condition that modified versions and compiled software including the code are made publicly available under the same license. For details, read the included license file.

More info about the license can be found here:

If you wish to obtain a different license feel free to contact me at:

Show all projects by KarlRamstedt