godot_voxel VS voxelgame

Don't do this, CSG is unoptimized. Use this.

Take a look at https://github.com/Zylann/godot_voxel, which would be a great starting point that you could build game mechanics on top of.

https://github.com/Zylann/godot_voxel https://voxel-tools.readthedocs.io/en/latest/

Currently all our major C++ based number crunching is in the GDAL. We haven't had to make in-house GDExtensions or Modules, yet. But we do also use Godot Voxel. Both are good examples of where you'd want more native speed.

I originally ported Qodot to an engine module that required people to compile their own engine (like godot-voxel) but users were turned away at this first roadblock.

I really wanted to use it but sadly it might be hard to export projects done with it cuz it's not a gdextension yet https://github.com/Zylann/godot_voxel/issues/333 still possible but i think you gotta compile something.

If you aren't adverse to doing a custom editor build you could add https://github.com/Zylann/godot_voxel

To give some practical examples. At my day job we use GDAL (a C++ geospatial data processing library) and Zylann's Godot Voxel (a C++ engine Module) https://github.com/Zylann/godot_voxel

The master branch of this one will also build as a GDExtension for Windows. This one is successfully building regularly, but structured different than the rest of the GDExtensions I've seen. I haven't played with this project too much yet, but it's an insanely powerful module/extension: https://github.com/Zylann/godot_voxel

To be honest though, Zy's module is going to be rough for you if you are averse to written documentation + code samples + experimentation, since that's kind of the best option for learning it at the moment. For an integrated character controller, dig into the blocky game example here. Specifically this script.

I'm messing around with these .obj files: https://github.com/Zylann/voxelgame/tree/master/project/blocky_game/blocks/log