Expose set_pixel and variants

[CsloudX]

Description

I want modify terrain when game runtime. but there was no a function for get the Image's pixel position with global_position.
Now I'm solved this problem by look at the Terrain3DEditor C++ code, but I wish can has api for GDScript.

Are you willing to help create this feature?

No

[TokisanGames]

There is an API. All of the get pixel variants take a global position. Why can't you use this?

Terrain3D/src/terrain_3d_storage.cpp

Lines 1091 to 1095 in c5a72b0

	ClassDB::bind_method(D_METHOD("get_pixel", "map_type", "global_position"), &Terrain3DStorage::get_pixel);
	ClassDB::bind_method(D_METHOD("get_height", "global_position"), &Terrain3DStorage::get_height);
	ClassDB::bind_method(D_METHOD("get_color", "global_position"), &Terrain3DStorage::get_color);
	ClassDB::bind_method(D_METHOD("get_control", "global_position"), &Terrain3DStorage::get_control);
	ClassDB::bind_method(D_METHOD("get_roughness", "global_position"), &Terrain3DStorage::get_roughness);

You just want a function that does the math of get_pixel without returning the pixel? But you can already write your own function for that as you have. Vec3 to vec2 image position is not useful without the region Id as well. Most people should use get_pixel. The reason you'd use the maps directly is if you want to use image.blit or fill. And in those cases you aren't recalculating the image position every pixel.

Now I'm solved this problem by look at the Terrain3DEditor C++ code

That's great, and exactly what you should be doing in both Terrain3D and Godot source when doing advanced gamedev projects.

[CsloudX]

There is an API. All of the get pixel variants take a global position. Why can't you use this?

I'm not only want get_pixel, but also want set_pixel, so I need the true pixel of image.
OR, there was get_height(global_position), can implement set_height(global_position, height)?

[TokisanGames]

I can add set_pixel easily and see it as useful.

[TokisanGames]

Per pixel setters have been added in 6ec4f7b.

After writing to the maps, you'll need to use force_update_maps to see changes. That won't update collision. You can disable and reenable collision, but that is slow. Dynamic collision is being worked on in #161.