[QUOTE=FriendlyFire1;451759]
A word to the “Add or modify extra settings”-node:
I think this node is meant to take the input at “settings array” and add the settings of the input array “New or changed settings”. But if there is a setting with the same name but different value in these arrays, It´s just logical to take the value of the “New or changed settings”-array, isn´t it? Because at the moment, it quite seems to me, that there is the one of the “settings array” taken in this case 
Ofc i may be wrong with it, but taking a look at that is worth it anyway.
And sry for bad english ^^
It takes an input array and compares it to an output array that already exists, if the key is already in it, it overwrites the value, if it is not then it adds the key/value.
It is to be used when the new/add array might not have all of the keys in it, it was made pretty much to be a faster way to add values to the settings array when changing options as you don’t have use a blueprint array loop or anything, you just throw the new key at the function and array and let it handle overwriting or adding the value depending on if it already exists or not.
For example of you have a drop down filter for searching for servers and change it from one value to another you can throw the new value with the key name into that node and let it handle changing the correct index.
It might not be useful for everyone, but it doesn’t have to be used.