Results 436 comments of froggie

Note: see #1016 and #53. I'm leaving this as low priority because I'm not sure how to go about this, and it would require a rewrite of some modules. Also...

Maybe this should be optional if users expect that behavior

It happens to some users. Probably mac thing again

Oh okay lol. It doesn't happen on Linux for me

Here (https://github.com/kami-blue/client/blob/1dd4db30f390d3d8b0d2359878e6d7597167ba94/src/main/kotlin/org/kamiblue/client/setting/settings/MutableSetting.kt#L36) is the gremlin responsible. It assumes you're always setting the value by doing `setting.value = something`, which clearly isn't the case for a Collection

Theoretically the valueListeners should also work for this as well, when this is fixed

A temporary workaround has been added to CollectionSetting by #2186, I don't know of a better way of doing it

Lol I have no idea how this happens

This has been possible for ages.