There were problems when creating forests by adding an array of Forests which had properties configured on those forests. (If you don't care about setting forest properties, you can just set the forests on the server as a list of strings and they'll get the default configuration). You can pass an array of Forest objects to set_forests on database. In that case, what should happen, is that forests are created with the properties on the forest object. Some, like availability, are changeable. Others, like the large data dictionary, cannot be changed after the forest is created.
There were problems when creating forests by adding an array of Forests which had properties configured on those forests. (If you don't care about setting forest properties, you can just set the forests on the server as a list of strings and they'll get the default configuration). You can pass an array of Forest objects to set_forests on database. In that case, what should happen, is that forests are created with the properties on the forest object. Some, like availability, are changeable. Others, like the large data dictionary, cannot be changed after the forest is created.