Add-on settings conversion

From Official Kodi Wiki
Jump to navigation Jump to search
Home icon grey.png   ▶ Development ▶ Add-on development ▶ Add-on settings conversion

Converting addon settings


As of Kodi 18 Leia it is possible to write your addon settings in the same setting format as Kodi uses. Due to many initial issues, it is not recommended to convert your settings if your addon is in the Leia addon repo.

In Kodi 19 Matrix, those bugs have been fixed, so we recommend to convert your addon settings if you plan to submit your addon to the Matrix addon repo (or higher).


The structure of your settings.xml file should look like this

<?xml version="1.0" ?>
<settings version="1">
	<section id="">
		<category id="general" label="" help="">
			<group id="1" label="">
				<setting id="" type="" label="" help="">
					<control type="" format=""/>
  • The <settings> tag must have a version="1" attribute, or the <section> tag will not be supported.
  • Your addon settings file can only have one <section> tag.
    The id should be the id of your addon. The use of multiple sections is reserved for Kodi's main settings.xml file.
  • You can use multiple <category> tags, just like in the old addon settings format.
    The id of a category needs to be a string.
  • The <group> tag is a replacement for the old sep and lsep types.
    You can define multiple groups in order to group a number of settings.


Similar to Kodi settings, addons can now define a setting level for every setting.
This will show or hide certain settings based on the settings level the user has selected (Basic, Standard, Advanced, Expert).

<setting id="" type="" label="" help="">

The various levels are defined as such:

  • 0 - Basic
  • 1 - Standard
  • 2 - Advanced
  • 3 - Expert
  • 4 - Internal (will never be shown in the GUI)

Setting types


<setting type="text" id="test01" label="32001" default=""/>

<setting type="text" id="test02" label="32002" default="" option="hidden"/>

<setting type="text" id="test03" label="32003" default="" option="urlencoded"/>


<setting type="ipaddress" id="test04" label="32004"/>


<setting type="number" id="test05" label="32005"/>


<setting type="date" id="test06" label="32006" default="2015-03-12"/>


<setting type="time" id="test07" label="32007" default="13:13"/>


<setting type="bool" id="test08" label="32008" default="false"/>


<setting type="select" id="test09" label="32009" lvalues="11|12|13|14"/>

<setting type="select" id="test10" label="32010" values="aa|bb|cc|dd"/>


<setting type="addon" id="test11" label="32011" default="" addontype="xbmc.metadata.scraper.movies"/>

<setting type="addon" id="test12" label="32012" default="" addontype="xbmc.metadata.scraper.movies" multiselect="true"/>


<setting type="enum" id="test13" label="32013" lvalues="11|12|13|14"/>

<setting type="enum" id="test14" label="32014" values="aa|bb|cc|dd"/>


in case you use lvalues in a labelenum control, the saved value will now be the string id, instead of the localized string. please adapt your python code for this.

<setting type="labelenum" id="test15" label="32015" lvalues="11|12|13|14"/>

<setting type="labelenum" id="test16" label="32016" values="bb|aa|dd|cc" sort="yes"/>

note: for labelenum settings, the label attribute for the options is optional. if you use it, it can either be a hardcoded string (label="foobar") or a localized id (label="32085").


<setting type="slider" id="test17" label="32017" default="20" range="5,5,100" option="int"/>

<setting type="slider" id="test18" label="32018" default="0.5" range="0.0,0.1,1.0" option="float"/>

<setting type="slider" id="test19" label="32019" default="20" range="0,1,100" option="percent"/>


<setting type="file" id="test20" label="32020" default=""/>


<setting type="audio" id="test21" label="32021" default=""/>


<setting type="video" id="test22" label="32022" default=""/>


<setting type="image" id="test23" label="32023" default=""/>


<setting type="executable" id="test24" label="32024" default=""/>


<setting type="folder" id="test25" label="32025" default=""/>

<setting type="folder" id="test26" label="32026" default="" option="writeable"/>

<setting type="folder" id="test27" label="32027" default="" source="videos"/>

<setting type="folder" id="test28" label="32028" default="" source="music"/>

<setting type="folder" id="test29" label="32029" default="" source="pictures"/>

<setting type="folder" id="test30" label="32030" default="" source="programs"/>

<setting type="folder" id="test31" label="32031" default="" source="files"/>

<setting type="folder" id="test32" label="32032" default="" source="local"/>


<setting type="action" id="test33" label="32033" action="RunScript(script.globalsearch)" option="close"/>

<setting type="action" id="test34" label="32034" action="RunScript(,Location1)" default=""/>

You can use the variables $ID and $CWD in your actions. $ID will be replaced by your add-on ID and $CWD with your add-on path:


fileenum type settings (which was basically a spincontrol listing all items) are no longer supported. these settings can be converted into a file or folder browser.

<setting type="fileenum" id="test35" label="32035" values="resources"/>

<setting type="fileenum" id="test36" label="32036" values="resources" mask="/"/>

<setting type="fileenum" id="test37" label="32037" values="resources" mask="*.txt"/>


colorbutton type settings allow a user to open a color picker dialog to select a color from Kodi's default color list. When the color has been selected, you can preview the colour and the hex code.

Note: Available from Kodi v20

<setting id="test36.color" type="string" label="32035" help="">
	<default>FF000000</default> <!-- Black -->
	<control type="colorbutton" />


if you wish to define a subsetting, you can use the parent attribute with the id of the parent setting as the value.

<setting id="test37" type="path" label="32037" help="" parent="test36">



if a setting should always be hidden, you can add this to the setting


if a settings should be conditionallly visible, add a dependencies section to your setting

	<dependency type="visible" setting=""></dependency>


if a setting should always be disabled, you can add this to the setting


if a settings should be conditionally enabled, add a dependencies section to your setting

	<dependency type="enable" setting=""></dependency>


enabling based on a boolean condition

	<dependency type="enable" on="property" name="infobool"></dependency>

eq / lt / gt


compare to a bool value of another setting

	<dependency type="enable" setting="test01">true</dependency>

compare to a int value of another setting

	<dependency type="enable" setting="test01">5</dependency>

compare to a string value of another setting

	<dependency type="enable" setting="test01">something</dependency>


	<dependency type="enable" operator="!is" setting="test01">true</dependency>
	<dependency type="enable" operator="!is" setting="test01">0</dependency>
	<dependency type="enable" operator="!is" setting="test01"></dependency>


	<dependency type="enable" operator="lt" setting="test01">5</dependency>


	<dependency type="enable" operator="gt" setting="test01">0</dependency>

and / or

multiple dependencies can be defined as such

	<dependency type="enable">
			<condition setting=""></condition>
			<condition setting=""></condition>
	<dependency type="enable">
			<condition setting=""></condition>
			<condition setting=""></condition>