This plugin makes it easy to generate and modify voxel terrains in Bevy. bevy_voxel_world handles multithreaded meshing, chunk spawning/despawning, texture mapping and provides an easy to use API that can be accessed from any system.
$ cargo run -r --example noise_terrainThe voxel terrain can be controlled in two main ways: through a terrain lookup function, and directly by set_voxel and get_voxel functions. The world has two "layers" of voxel information, one that is purely procedural and determined by a terrain lookup function, and one that is memory based and controlled by set_voxel. The data layer always overrides the procedural layer. This way, the world can be infinitely large, but we only need to store information about voxels that are deliberately changed.
The set_voxel and get_voxel access functions are easily reached from any normal Bevy system:
fn my_system(mut voxel_world: VoxelWorld) {
voxel_world.set_voxel(IVec3 { ... }, WorldVoxel::Ground(0));
}This will update the voxel value at the given location, and cause bevy_voxel_world to queue the affected chunk for re-meshing.
Voxels are keyed by their XYZ coordinate in the world, specified by an IVec3. The type of voxel is specified by the WorldVoxel type. A voxel can be Unset, Air or Ground. Ground voxels also holds a mterial type value of type u8, meaning that a maximum of 256 material types are supported. Material types can easily be mapped to indexes in a 2d texture array though a mapping callback. Each material can map to three indexes; top, sides and bottom (examples coming soon.)
For an example on how to use a terrain lookup function, see this example.
bevy_voxel_world began as an internal part of a game that I'm working on, but I figured that it could be useful as a standalone plugin, for myself and perhaps for others, so I decided to break it out and make it public as a crate.
In its current state (as of 0.1.0), there are still various hard-coded assumptions that works well enough for my usecase, but may not suit everyone. Over time, I aim to generalize and make bevy_voxel_world more configurable. There are also many potential performance optimizations that I have not prioritized yet at this point.
Currently only "blocky", Minecraft-like, voxels are supported, and there is no support for "half-slabs".
Feedback, issues and pull requests are welcomed!
| bevy | bevy_voxel_world |
|---|---|
| 0.11 | ^0.1 |