You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When trying to read or write block data to a world, the developer must take several more steps than are necessary to do so. The developer must create a VoxelQuery parameter, calculate the chunk coordinate from the block coordinates, get the chunk, then finally read the block data value from that chunk. This entire process is a bit more verbose than is needed.
Describe the solution you'd like
I propose adding a second system parameter companion to voxel query (which should probably be renamed to ChunkQuery) that would abstract away chunks and allow for reading and writing block data directly to a world.
Describe alternatives you've considered
Adding more verbose code or simply writing a macro for reading and writing block data also works, but it is less flexible and requires more work. This is something that should be quick and simple.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Another approach to this proposal might be to further extend VoxelQuery into subcommand executors, similar to how Bevy Commands can call .entity(_) to receive a mutable EntityCommands object.
Is your feature request related to a problem? Please describe.
When trying to read or write block data to a world, the developer must take several more steps than are necessary to do so. The developer must create a VoxelQuery parameter, calculate the chunk coordinate from the block coordinates, get the chunk, then finally read the block data value from that chunk. This entire process is a bit more verbose than is needed.
Describe the solution you'd like
I propose adding a second system parameter companion to voxel query (which should probably be renamed to ChunkQuery) that would abstract away chunks and allow for reading and writing block data directly to a world.
Describe alternatives you've considered
Adding more verbose code or simply writing a macro for reading and writing block data also works, but it is less flexible and requires more work. This is something that should be quick and simple.
Additional context
N/A
The text was updated successfully, but these errors were encountered: