We're having OceanBroadcastManager.Save wrap
updateConfigWithTransaction, which achieves several things.
Firstly, if everything uses OceanBroadcastManager.Save for updating broadcast config fields, then we'll have everything inherently synchronised propertly.
Secondly, this should greatly reduce boilerplate associated with using updateConfigWithTransaction for every modifification of the broadcast config.
closes #177
We're having OceanBroadcastManager.Save wrap updateConfigWithTransaction, which achieves several things.
Firstly, if everything uses OceanBroadcastManager.Save for updating broadcast config fields, then we'll have everything inherently synchronised propertly.
Secondly, this should greatly reduce boilerplate associated with using updateConfigWithTransaction for every modifification of the broadcast config.