Note:The advancedsettings.xml file does not exist by default. You have to create it first!

The advancedsettings.xml file, which does not exist by default, can be created by a user in their userdata folder.

This file is used for advanced settings and options that do not have GUI controls inside of Kodi. Some settings are experimental or very rarely set, so they can only be used via the advancedsettings.xml file. The file is simply a plain text file and can be edited by various text editors, so long as the name is "advancedsettings.xml". These advanced settings can be used to tweak various things such as episode naming patterns, special network ports, special behaviors, and more.

The following page will describe the structure of the advancedsettings.xml file and the various individual settings.

Note:

All XML tags must be lowercase. The start and end of the advancedsettings.xml file must have the <advancedsettings> and </advancedsettings> tags.

Kodi will only read the advancedsettings.xml file when it starts up. If you make changes while it is running then you must restart Kodi.

For some Windows versions, Kodi has two \userdata\ folders. The correct one to put the advancedsettings.xml file in is not the one in Program Files, but in %appdata%\Kodi\userdata\.

2 List of available settings

2.1 Troubleshooting settings

2.1.1 loglevel

The logging level that Kodi will use to log errors and information. The "hide" attribute is optional.

Attribute options:

true

Hides "enable debugging" guisetting.

false

"enable debugging" guisetting will switch between min(loglevel, 0) and max(loglevel, 2) for off and on respectively. (Default)

Main options:

-1

No logging, suppresses all log output

0

Normal logging, only logging errors (Default)

1

Debug logging (without showing text on screen)

2

Debug logging with freemem, fps and cpu usage shown on screen

3

Debug logging with freemem, fps and cpu usage and full smb logging

Example:

<loglevelhide="false">1</loglevel>

Note: If debugging is switched on in the GUI, loglevel will be set to 2 (log to both file and on-screen information); this will over-ride any advancedsettings.xml setting.

Note: If debugging is switched on in the GUI when Kodi is shut down, then it will be automatically be re-enabled at level 2 when it is re-started. This is true even if 'hide' is subsequently set to 'true' - in other words, if you enable it in the GUI and then hide the GUI toggle, it will stay on level 2 irrespective of what you subsequently set in advancedsettings.xml.

2.1.2 jsonrpc

To make it easier for developers using the JSON RPC API in their (third party) applications to debug during development the json output of Kodi can be prettified by setting compactoutput to false. Default json output mode is a compact print which does not contain any unnecessary whitespaces and therefore is difficult to read for humans.
Furthermore using the tcpport setting it is possible to change the default TCP port used by Kodi for JSON RPC (which is 9090) to any other valid port.

Percentage of video to ignore at the end. If you stop watching the video here no resume point is created. Set to 101 to never save a resume point. The video is already marked as watched at 90%, see above. See also: HOW-TO:Modify automatic watch and resume points

<vdpauscaling>true</vdpauscaling>

Scales with vdpau instead of opengl and turns on its HQ scaler when available, enabling this might slow down rendering and cause framedrops especially on ION systems, this setting requires a vdpau feature set C GPU.

<enablehighqualityhwscalers>true</enablehighqualityhwscalers>

Allow turning on the spline36 and lanczos3 shader (for GL builds).

<dxvaallowhqscaling>false</dxvaallowhqscaling>

Enables high quality video upscaling for Windows.

<ppffmpegdeinterlacing>linblenddeint</ppffmpegdeinterlacing>

Override the deinterlacing options passed to libpostproc.

<ppffmpegpostprocessing>ha:128:7,va,dr</ppffmpegpostprocessing>

Override the post processing options passed to libpostproc when 'Video post-processing' is activated in GUI Videos-Settings-Playback.

<autoscalemaxfps>30</autoscalemaxfps>

When scaling method is set to auto, bilinear is chosen when the fps is higher than this limit, the default is 30.

<adjustrefreshrate>

Settings for when "Adjust refreshrate to match video fps" is enabled in the video playback GUI settings.

<override><fps>23.976</fps><refresh>60.0</refresh></override>

Example - "Adjust refreshrate to match video fps" will try to select the best refreshrate for the video fps but it doesn't always get it right, for example it might switch to an unsupported refreshrate. You can add overrides here to switch to a certain refreshrate based on video fps. It's possible to add as many overrides as you need. Overrides are processed in order, if the first one doesn't match the fps or no refreshrates match that override, it will try the next one until no overrides are left.

fps - if the fps is between 23.966 and 23.986

refresh - switch to the first found refreshrate that is between 59.99 and 60.01

Example - If none of the overrides match, or none of the refreshrates match any of the fps matching overrides, it will choose a fallback refreshrate. Fallbacks are process in order, if the first fallback doesn't match any refreshrate, it will try the next one until no fallbacks are left.

refresh - Switch to the first found refreshrate that is between 49.99 and 50.01.

If none of the overrides match the video fps, or no refreshrates match any of the fps matching overrides, and no fallbacks are specified or no refreshrates match any fallbacks, it will automatically choose the best refreshrate (same as having no overrides and fallbacks).

</adjustrefreshrate>

<checkdxvacompatibility>value</checkdxvacompatibility>

Advanced setting not present: let Kodi autodetect cards that support H.264 profile > L4.1. Set value to false to enable DXVA no matter what. Set value to true if Kodi doesn't autodetect that the graphics card doesn't support > L4.1.

Position behavior of ass subtitiles when setting "subtitle position on screen" set to "fixed". True to show at the fixed position set in video calibration. False to show at the bottom of video (default).

</video>

2.2.3 audio

<audio><!-- Amount of headroom Kodi should use above the maximum volume level, in decibels. Defaults to 0, valid values 0, 6, 12. --><headroom>0</headroom><!-- Default audio player: paplayer or dvdplayer --><defaultplayer>paplayer</defaultplayer><!-- Regular expressions that if evaluated to true won't be added to library. --><excludefromscan><regexp>[-\._ ](podcast)[-\._ ]</regexp></excludefromscan><!-- Regular expressions that if evaluated to true won't be displayed in Files View --><excludefromlisting><regexp>[-\._ ](podcast)[-\._ ]</regexp></excludefromlisting><!-- Amount of gain (dB) to be applied to AC3 streams that have been mixed-down to 2 channels. Default is 12.0. Valid values are: -96.0 to 96.0. --><ac3downmixgain>12.0</ac3downmixgain><!-- Minimum percentage that has to be played before it is considered for incrementing in the Top 100 database view, or for last.fm submittal --><playcountminimumpercent>99</playcountminimumpercent><!-- Whether to use Dynamic Range Compression (DRC) on AC3 streams. 1.0 is "full" compression, as defined by the audio track's metadata, which is recommended for "basic" sound systems such as the internal speakers on a TV. 0.0 is no compression at all, which is recommended for people with nice multi-speaker sound systems. -1.0 (default) defaults to whatever ffmpeg uses, which is currently the same as 1.0. This has no effect if passthrough is enabled for AC3. --><applydrc>-1.0</applydrc><!-- default values for limiter/compressor --><limiterhold>0.025</limiterhold><!-- default values for limiter/compressor --><limiterrelease>0.1</limiterrelease></audio>

2.2.4 edl

Commercial break detection not as good you think it could be? Are some commercial breaks in a series of adverts not being skipped? Are some parts being skipped that are clearly not commercials? Does the end of the previous recording still show? The following advanced settings can be used to better identify full commercial break sequences, remove incorrectly flagged commercial breaks, and have playback start at the actual beginning of the recording.

<edl><!-- if true, commercial breaks will be merged according to the remaining options. --><mergeshortcommbreaks>false</mergeshortcommbreaks><!-- Commercial breaks won't be merged if the total length of the commercial break would be greater than this (seconds) --><maxcommbreaklength>250</maxcommbreaklength><!-- After merging, commercial breaks shorter than this will be removed (seconds) --><mincommbreaklength>90</mincommbreaklength><!-- Commercial breaks that are further apart than this won't be merged (seconds) --><maxcommbreakgap>120</maxcommbreakgap><!-- How long to wait before automatically skipping when the start of a commercial break reached (seconds) --><commbreakautowait>0</commbreakautowait><!-- How long to rewind after automatically skipping to the end of the commercial break (seconds) --><commbreakautowind>0</commbreakautowind></edl>

2.2.5 pvr

<pvr><timecorrection>0</timecorrection><!-- Correct all times (epg tags, timer tags, recording tags) by this amount of minutes. --><infotoggleinterval>3000</infotoggleinterval><!-- If there is more than one pvr gui info item available (e.g. multiple recordings active at the same time), use this toggle delay in milliseconds. --><channeliconsautoscan>true</channeliconsautoscan><!-- Automatically scan user defined folder for channel icons when loading internal channel groups. --><autoscaniconsuserset>false</autoscaniconsuserset><!-- Mark channel icons populated by auto scan as "user set". --><numericchannelswitchtimeout>1000</numericchannelswitchtimeout><!-- Time in ms before the numeric dialog auto closes when confirmchannelswitch is disabled. --></pvr>

If the argument action="append" or append="yes" is supplied, the default moviestacking regular expressions will remain intact and the user specified ones will be added to the end.

Example:

<moviestackingaction="append"><!-- This expression will match movename1-xvid.avi, moviename2-xvid.avi. Be warned that it will likely stack sequels in a flat directory layout, so it is only recommend in a dir-per-video layout. --><regexp>(.*?)([ ._-]*[0-9])(.*?)(\.[^.]+)$</regexp></moviestacking>

If the argument action="prepend" is supplied, the default moviestacking regular expressions will remain intact and the user specified ones will be added to the beginning.

The string found before will be used as basis string getting cleaned by the cleanstrings expressions.

By default date formats like MM:YY are ignored.

2.3.8 cleanstrings

Clean unwanted characters from filenames or folders by using a list of Regular Expressions. Please note that everything right of the match (at the end of the file name) is removed, so if you would have a file named Super movie.mp4 and would add <regexp> </regexp> (only a space), the only thing that would be left is Super, which is probably not what you want.

Examples of matching regexps for certain filenames can be found on the TV shows page.

For multi-episode matching to work, there needs to be a third set of parentheses '()' at the end, this part is fed back into the regexp engine.

A forum thread has a discussion of pre-made regex lists to match common names. These might improve Kodi's ability to match TV show names in some situations, at the risk of additional false positives.

2.3.9.1 Filenames without Season

There are two methods to add episodes without a season in their file path. Both ways will force the season to '1' by default, so that you can use
the 'Use Absolute Ordering (Single Season)' setting from the TheTvDb.com scraper.

Simple Method (XBMC v9.11 onwards and Kodi)

Use only one pair of parentheses

<regexp>[/\._ \-]([0-9]+)</regexp>

Advanced Method (XBMC v10.05 onwards and Kodi)

Supports multi-episode files without season

Use an empty pair of parentheses for the season

<regexp>[/\._ \-]()([0-9]+)(-[0-9]+)?</regexp>

Specifying Default Season (XBMC v12.0 onwards and Kodi)

It is possible to set the default season for specific regular expressions by setting the 'defaultseason' attribute.

2.3.15 videolibrary

Options specific to the Video Library

<videolibrary><allitemsonbottom>false</allitemsonbottom><!-- sorts the "*All" items at the bottom of the list when in Ascending order --><cleanonupdate>false</cleanonupdate><!-- default set to false to prevent Kodi from removing items from the database while updating. --><usefasthash>true</usefasthash><!-- defaults to true. Set to false in order to skip hashing based on the folders modification time. --><recentlyaddeditems>35</recentlyaddeditems><!-- number of recently added items. Defaults to 25 --><itemseparator> / </itemseparator><!-- separator used for multiple artists/genres in tags. Note, this is *space* *slash* *space* --><exportautothumbs>false</exportautothumbs><!-- export auto-generated thumbs. Defaults to false --><importwatchedstate>false</importwatchedstate><!-- import previously exported playdate and playcount from .nfo files. Defaults to false --><importresumepoint>false</importresumepoint><!-- import previously exported resume point from .nfo files. Defaults to false --><dateadded>1</dateadded><!-- 0 results in using the current datetime when adding a video; 1 (default) results in prefering to use the files mtime (if it's valid) and only using the file's ctime if the mtime isn't valid; 2 results in using the newer datetime of the file's mtime and ctime --></videolibrary>

2.3.16 videoscanner

Options specific to the Video scanner

<videoscanner><ignoreerrors>true</ignoreerrors><!-- Set to true to silently ignore errors while scanning videos. This prevents the error dialogue box, so you don't have to keep hitting "yes" to keep scanning.--></videoscanner>

2.4 Library artwork

2.4.1 imageres

This tag is new for v12 (Frodo), replacing <thumbsize>.

Specify the maximal resolution that art should be resized to in pixels. The width is automatically calculated as being 16/9*height. The image will be resized to fit within this size. e.g. an image that is 2000x500 will be cached at size 1280x320. An image that is 500x800 will be cached at size 450x720 using the default value of 720.

<imageres>720</imageres>

2.4.2 fanartres

This tag is new for v12 (Frodo), replacing <fanartheight>.

Specify the resolution that cached fanart should be resized to in pixels. The width is automatically calculated as being 16/9*height. Only images that are exactly 16x9 and equal to or greater than this resolution will be cached at this size - all other images will be cached using <imageres>. The default value is 1080.

<fanartres>1080</fanartres>

2.4.3 fanart

As of v12 (Frodo), this tag is only used for music and not video.

A list of additional files to try when searching for fanart images. (The defaults are fanart.jpg and fanart.png which can be removed.)

Example:

<fanart><remove>fanart.jpg</remove><add>backdrop.jpg</add></fanart>

2.4.4 musicthumbs

A list of additional files to try when searching for music thumbnail images. (The default is folder.jpg which can be removed.)

2.5.4 musicdatabase/videodatabase

Note:It is HIGHLY recommended that you not attempt to place an sqlite3 database outside of kodi's path. sqlite3 contains no filesystem abstraction, so this will plain break on any non-local (as far as Kodi is concerned) paths. Use this for mysql only.

Parent tags:

<videodatabase>

<musicdatabase>

<tvdatabase> - Highly experimental/unstable and no practical benefit for most users. Avoid using.

<epgdatabase> - Highly experimental/unstable and no practical benefit for most users. Avoid using.

<adspdatabase> - Highly experimental/unstable and no practical benefit for most users. Avoid using.

Kodi also supports using MySQL for PVR (tvdatabase and epgdatabase) as well as the ADSP database. However, there is little to no practical benefit to using MySQL for those databases, and there has been very little testing with them (expect bugs!). Unless you simply want to experiment, or have a very specific need, you should avoid using MySQL for PVR and ADSP.

sqlite3: defines the name of the database file to read from, excluding the ".db" extension.

mysql: defines the name of the database to use

<user>

Required for MySQL -

sqlite3: silently ignored

mysql: defines the user with privileged access to the database

<pass>

Required for MySQL -

sqlite3: silently ignored

mysql: defines the password for the user with privileged access to the database

<compression>

Optional - Defaults to false. Set to "true" to enable MySQL compression protocol. Performance benefit is going to be largely dependent on the network bandwidth, latency between database and clients and on the size of the result sets. [1]

Note: Slower clients (such as the RPi and others) won't benefit from it as the zlib de-compression overhead is higher than the actual compression savings

It is possible to add or remove extensions for Music, using the following XML tags. Useful if you keep, say, FLAC and mp3 versions of music in the same folder. The <remove> tag can be used to remove mp3 from being listed in the library, leaving only the higher quality FLAC being displayed.

2.6.2 cddbaddress

The address of the online CDDb database. You may set this to another freedb mirror if there is a more suitable one.

Default:

<cddbaddress>freedb.freedb.org</cddbaddress>

2.6.3 songinfoduration

This controls how long the song information will remain onscreen when the song changes during visualisations. The valid range is "1" to "Indefinite (0)", in seconds. This does not include the duration of any transition effects.

Default:

<songinfoduration>10</songinfoduration>

2.6.4 musicfilenamefilters

Contains filters to match music information (artist, title etc.) from a tag-less music filename. The first <filter> to match completely is used. Matched items include:

2.6.5 musiclibrary

Options specific to the Music Library

<musiclibrary><hideallitems>true</hideallitems><!-- removes the "*All" items from the music library --><!-- This will be replaced in v15 with a GUI option. --><allitemsonbottom>true</allitemsonbottom><!-- sorts the "*All" items at the bottom of the list when in Ascending order --><promptfulltagscan>false</promptfulltagscan><!-- prompt for full tag rescan, regardless of files being unchanged, every time scanning is initiated --><recentlyaddeditems>35</recentlyaddeditems><!-- number of recently added items. Defaults to 25 --><albumformat>%B - %Y</albumformat><!-- album label template, default is "%B" --><prioritiseapetags>true</prioritiseapetags><!-- prioritise APEv2 tags over ID3v1/2 tags, default is false. --><itemseparator> / </itemseparator><!-- separator used for multiple artists/genres in tags. Note, this is *space* *slash* *space* --><artistseparators><!-- separator used for multiple artists. Note that spaces are used for some separators.--><separator>;</separator><separator>:</separator><separator>|</separator><separator> feat. </separator><separator> ft. </separator></artistseparators><dateadded>1</dateadded><!-- 0 results in using the current datetime when adding a song; 1 (default) results in prefering to use the files mtime (if it's valid) and only using the file's ctime if the mtime isn't valid; 2 results in using the newer datetime of the file's mtime and ctime --></musiclibrary>

Note: Changing the <itemseparator> or <artistseparators> will only affect newly added items. Even a rescan won't change the added ones, you have to remove the music source(s) and add them again, or delete the music database to achieve this. This process should be made easier in v18 using <promptfulltagscan> (that is not available in v17)

2.7 Photos settings

2.7.1 pictureextensions

A list of additional file-extensions to allow (add) or exclude (remove) in the My Pictures window.

2.7.3 slideshow

<slideshow><!-- Amount to pan images as a percentage of the screen --><panamount>2.5</panamount><!-- Amount to zoom images as a percentage of the screen --><zoomamount>5.0</zoomamount><!-- Amount to compensate (zoom) images to attempt to reduce black bars. --><!-- Results in cropping of the longer length of the image in order to reduce the black bars on the shorter length of the image. --><!-- Defaults to 20. --><blackbarcompensation>20</blackbarcompensation></slideshow>

2.8 Network settings

2.8.1 samba

<samba><doscodepage></doscodepage><!-- code page to use for filenames --><clienttimeout>10</clienttimeout><!-- timeout (in seconds) --><statfiles>true</statfiles><!-- Set to false to disable smb stat() on files to speed up listings of large directories (over slow links) --></samba>

2.8.4 cache

<cache><memorysize>0</memorysize><!-- number of bytes used for buffering streams in memory When set to 0 the cache will be written to disk instead of RAM --><buffermode>0</buffermode><!-- Choose what to buffer: 0) Buffer all internet filesystems (like "2" but additionally also ftp, webdav, etc.) (default) 1) Buffer all filesystems (including local) 2) Only buffer true internet filesystems (streams) (http, etc.) 3) No buffer --><readfactor>4.0</readfactor><!-- this factor determines the max readrate in terms of readfactor * avg bitrate of a video file. This can help on bad connections to keep the cache filled. It will also greatly speed up buffering. Default value 4.0. --></cache>

2.8.5 airtunesport

This overwrites the defalt listening port of the AirTunes server (announced via zeroconf).

2.8.6 airplayport

This overwrites the default listening port of the AirPlay server (announced via zeroconf).

2.9 File system settings

2.9.1 packagefoldersize

<packagefoldersize>options</packagefoldersize>

The amount (in megabytes) of add-on zip packages saved from previous add-on installs. These packages are mainly used for the add-on rollback feature. Increasing the size should increase the amount of past versions saved. Defaults to 200 MB.

Example:

<packagefoldersize>200</packagefoldersize><!-- this example would keep up to 200MB of add-on packages. -->

2.10.2 controllerdeadzone

2.10.3 enablemultimediakeys

This setting only has any effect on Windows versions of Kodi, and only applies to builds from 28th May 2011 onwards.
In Windows the multimedia keys generate a WM_APPCOMMAND message in addition the keypress. Kodi processes both keypresses and the WM_APPCOMMAND messages, and the end result would be that the command is executed twice. To avoid this, by default multimedia keypresses are disabled. Although it should rarely be necessary, the enablemultimediakeys setting allows you to enable the multimedia keys.

2.10.5 touchscreen

This setting allows you to move/align the origin of the touch screen with the origin of the display used. If touch input does not result in a correct movement of the mouse pointer, the behaviour can be corrected with an offset and a stretch/compress factor.

Example:

<touchscreen><x_offset>0</x_offset><!-- set pixel x offset to align it to the used display--><y_offset>0</y_offset><!-- set pixel y offset to align it to the used display--><x_stretch_factor>1.0</x_stretch_factor><!-- stretch/compress the touch x axis--><y_stretch_factor>1.0</y_stretch_factor><!-- stretch/compress the touch y axis--></touchscreen>

2.11 Other interface settings

2.11.1 window

Note: This is a "hidden" guisettings.xml setting (defined by the mouse moving the window size), but it is mentioned here because it is a particularly useful override when used in advancedsettings.xml
This allows you to manually set the default size of Kodi's windowed mode. If you resize the window, it will return to the set size when restarting.

WIDTH and HEIGHT are the values for each dimension, in pixels.

<window><width>WIDTH</width><height>HEIGHT</height></window>

2.11.2 restrictcapsmask

Windows only. A bitmask to prevent Kodi from using detected texture capabilities of the GPU. This helps work around buggy hardware/drivers.

1: prevent the use of compressed textures (DXT1, DXT3, DXT5)
2: prevent the use of non-power-of-two dimensions for textures
4: prevent the use of compressed textures with non-power-of-two dimensions.

<restrictcapsmask>0</restrictcapsmask>

2.11.3 algorithmdirtyregions

Note: Some GPU/hardware configurations will have some minor issues (such as a visual "flicker"). For those situations try mode 2 or use the default (mode 3, which requires no advancedsetting). Almost all ARM-based devices (such as Android) willl likely have flickering issues.

Enable dirty-region processing. Dirty regions are any parts of the screen that have changed since the last frame. By not re-rendering what hasn't changed the GUI can be sped up. Because all GPUs work differently, only Mode 3, combined with nofliptimeout=0, is guaranteed to work for everyone without flickering issues. This mode will reduce CPU/GPU usage, but will not increase GUI speed.

value

result

description

0

Off

The entire viewport is always rendered.

1

Union

All dirty regions are grouped into the smallest possible rectangle. This is typically the fastest mode for slower GPUs due to only making one pass.

2

Cost reduction

Each dirty region is presented separately, in as many passes as there are regions.

3

Whole Screen

The entire screen is rendered if there are any dirty regions. This, combined with nofliptimeout is a safe default for drivers that clear buffer contents (manifests as blinking or vibrating images). Default

2.11.4 visualizedirtyregions

Note: This is only a development mode and isn't of use to normal users.

Example:

<gui><visualizedirtyregions>true</visualizedirtyregions></gui>

2.11.5 showexitbutton

Setting to hide the exit button, useful for people running appliance based setups where exit would only confuse/complicate the user. Modifiable via the advancedsettings.xml by setting showexitbutton to false, default is true (show)

Example:

<showexitbutton>true</showexitbutton>

2.11.6 fullscreen

Starts Kodi in full screen (check resolutions!).

<fullscreen>false</fullscreen>

2.11.7 splash

Set to false if you wish to disable the startup splash image. Defaults to true.

<splash>true</splash>

2.11.8 cputempcommand

Provide a shell command Kodi will use to get CPU temperature. It should print out only "[temp as integer] [scale as one of "CcFf"]".

<resample>, <forceDirectSound>, <audiophile>, <audiosinkbufferdurationmsec>, <allowtranscode44100>, and <streamsilence> - These were various sub-tags for <audio> that were removed in v13 Gotham and either replaced by GUI settings or were no longer needed.

<hideallitems> - For both the <videolibrary> and <musiclibrary> sections, this is replaced by a GUI option in v15 Isengard

<SmallStepBackSeconds> - In v15 the SmallStepBackaction ID has been replaced by seek(-7) in default keymaps. See skip steps for details. When the original SmallStepBack action ID is used it defaults to the first backwards additive seeking value.

<timeseekforward>/<timeseekbackward> - In v15 these tags are replaced by GUI options via additive seeking, which is configured in the GUI. See skip steps for details.

<karaoke> - In v16 all of the karaoke features in Kodi were removed.

<useddsfanart> - removed in v17 Krypton.

<cachemembuffersize> and <readbufferfactor> - In v17 <cachemembuffersize> is renamed to <memorysize> and <readbufferfactor> is renamed to <readfactor>. In addition, all three buffer related settings in <network> are moved out of <network> and into a new <cache> parent tag.

<minvideocachelevel>, <minaudiocachelevel>, and <cacheindvdplayer> have been removed in v17.

<useffmpegvda> - Tag was only used for development testing. Removed in v17.

<nofliptimeout> - Removed in v17

<blackbarcolour> - Removed in v17 (maybe?)

<disableswmultithreading> - Removed in v17 (maybe?)

<measurerefreshrate> - Removed in v17 or v18?

<myth> - Removed sometime between v16 to v18

<tuxbox> - Removed

<backgroundupdate> - Removed

<hideemptyseries> - Replaced by a GUI option.

<mymovies> and child tag <categoriestogenres> - Removed

<albumssortbyartistthenyear> - Removed

<albumformatright> - Removed

<remoterepeat> - Removed

<allowd3d9ex> and <forced3d9ex> - Removed sometime between v16 to v18

<lingertime> - Replaced by a GUI setting in v18

<forcevaapienabled> - Removed in v18

2.13 guisettings.xml settings

You can also define the settings normally defined in the GUI (and stored in guisettings.xml) in advancedsettings.xml. Most guisettings.xml settings defined in advancedsettings.xml will override the guisettings.xml values, and the settings will be removed completely from the interface.

The easiest way to include a guisettings.xml setting is to first change the setting in the interface to the value that you want, and then open the userdata/guisettings.xml file and find the XML entry that corresponds to that setting.

Then just add that entry to the advancedsettings.xml file.

For instance, to set the Font Character Set (found in the appearance setting, in the Look and Feel section), you'd open up guisettings.xml and find:

<lookandfeel><charset>Hebrew (Windows)</charset></lookandfeel>

Simply take that entry and place it in advancedsettings.xml. The option in Kodi's interface for the character set will then no longer be visible, and Kodi will always use the Hebrew (Windows) character set.