API Changes

[TokisanGames]

This discussion can house threads on changes to the API, especially renaming things.

[TokisanGames]

Materials

• TerrainLayerMaterial aren't layers really. That name is confusing. They are just materials. How to differentiate it from the single master terrain material? I would rename the master to that or global. People won't be interfacing with the master. They will be interfacing with the layers, so it should be clearer. TerrainMaterial -> TerrainMasterMaterial or TerrainGlobalMaterial, TerrainLayerMaterial -> TerrainMaterial.

• set_material(0, mat), get_material(0), get_materials, get_material_count all make more sense to me than layers.

• void set_layer(const Ref<TerrainLayerMaterial3D> &p_material, int p_index); I think the index should come first, as is done in set_surface_material(0, mat) and elsewhere.

• Master set_material -> set_master_material or set_global_material or set_terrain_material

• material var changes to match above

• TerrainLayerMaterial::albedo and set_albdeo. Maybe these are better named albedo_tint. Also do we need this? IMO, we should drop this and include a color map so the user can paint various colors. We don't need a per texture color tint. If they want that, they should change the texture in photoshop.

[TokisanGames]

TerrainStorage funcs & vars

• _update_arrays() - will probably go away as UVs can be paintable and colors turn into a global map

• _update_textures() better named _update_terrain_textures() or _update_terrain_texture_arrays().

• _update_layers() -> _update_materials()

• _update_material() better as _update_maps() or _update_terrain_maps()

• albedo_textures -> albedo_texture_array, and normal

• In _update_textures, swap albedo_textures and albedo_texture_array. Each is more accurate of a name for the opposite.

• _convert_array() -> _create_texture_array