godot-voxel-tools
godot-voxel-tools
When to use this skill
Use for Zylann/godot_voxel specifically, including its VoxelTerrain, VoxelLodTerrain and VoxelViewer workflows. Choose one independent mode: edition-fit, module-build-export, extension-build-export, terrain-setup, streaming-diagnosis, or CSharp-integration. Route generic engine selection or unrelated voxel ray tracers elsewhere.
Instructions
1. Freeze edition, revision and target
Read upstream evidence. Record Godot exact version/commit, Voxel Tools revision, module or GDExtension, renderer, architecture, export target and language. Preserve the existing project version. Research master is 1.7.1-dev, while latest observed module release is v1.7; their commits were not equated. Godot 3 support is on an unmaintained branch. End with a version/edition/export matrix and unresolved compatibility items.
Module means a custom Godot editor plus custom export templates. GDExtension means addon libraries and regular Godot templates, but the pinned development docs warn about crashes and production readiness. Never enable both: registered classes conflict. Manifest minimum 4.4.1 and SConstruct GodotCpp API 4.5 are distinct evidence, not universal compatibility guarantees.
2. Run the installed offline helper only within its scope
Helper host prerequisite: Before running the helper, use a POSIX Python environment with os.O_NOFOLLOW and os.open support for dir_fd. Native Windows may fail closed with secure_posix_traversal_unavailable; preserve these safety guards. Windows users can retry in a WSL environment that supports these features or manually compare the original manifest-listed source files against the pinned evidence. Neither this guidance nor a manual comparison verifies helper execution or runtime behavior; report those as unverified.
From this installed skill directory: