Tasks - Box Engine
Developing the map engine
How do you find this atacking plan?
Any questions, comments, other ideas?
- complete implementation of the map
( map serialization, all types of voxels )
- testing the engine
( generate fractal maps, map editor )
during this step we will find the limitation of
the engine and how to overpass them;
decide if we continue with this engine or
we will think to another one
After step 2 is finished a part of the team will
start working on pathfinding the other will continue with
Here are more information about step 1.
I'm thinking that you should have an abstract
class Voxel, and derive the 4 kinds of boxes
( 1 complete box + 3 cutted boxes )
The cutted boxes are ( see picture )
- a box with a corner cutted
- the corner cutted from a box
- a box cutted in half by diagonally
The Voxel class should contain serialization methods,
position and size of the voxel and for cutted boxes info
about the cut
So serialization should be done like this
- complete box
x y z lenght width height
- box without a corner
x y z lenght width height cutted_corner_number
x y z lenght width height corner_number
- half box
x y z lenght width height cutted_edge
Map contains a list of voxels. Serialization will
read/write on the first line the number of voxels
and on each line a number which specify the kind of
voxel and then serialized voxel.
What do you think about this design? Good, bad? Improvments?