The YamlConfiguration class is NOT thread safe.
This means it is not safe for me to edit the config while saving it on another thread, meaning I have to run all of my configuration operations on one thread, usually the main thread. I/O should not be ran on the main thread, but at this point it is really the only option (unless I dramatically change how I use the configs, but not everyone is aware of how to do that or how it works, and even then, it will only work for saving configs, not for reloading them).

Fixes:

• Allow the internal 'map' field to be reassigned, and change the modifier to protected volatile (you'll see why)
• Change the internal 'map' field to 'ConcurrentLinkedHashMap', or at least allow a constructor to set the field to whatever it wants to
• When 'load(File)' is invoked, simply load the new contents into a new ConcurrentLinkedHashMap and replace the old map field (this prevents any Threads from walking in when a reload is not finished yet, without using a synchronized block!! :O)