So, im currently writing a little program, with the aim to modify the path map (wpm file) in a way that makes places with certain textures (as written in the w3e file) unwalkable. However, i'm getting confused about the map sizes.
In the environment file (w3e), i get (mapwidth+1)*(mapheight+1) sets of data, so a 64x64 map would have dimensions of 65x65.
In the path map, however, i have a size of (mapwidth*4)*(mapheight*4), or for the 64x64 map, 256x256, respectively.
Now, seeing mapwidth*4, it seems like every texturable spot would be seperated into 4 parts, each of which can have its own pathing information. However, the w3e file uses dimensions+1 while the mmp doesn't, which would mean that there is not enough pathing data for the whole map, or more texture data than actual ground. Both seems unreasonable. Someone mind elaborating on this?
In the environment file (w3e), i get (mapwidth+1)*(mapheight+1) sets of data, so a 64x64 map would have dimensions of 65x65.
In the path map, however, i have a size of (mapwidth*4)*(mapheight*4), or for the 64x64 map, 256x256, respectively.
Now, seeing mapwidth*4, it seems like every texturable spot would be seperated into 4 parts, each of which can have its own pathing information. However, the w3e file uses dimensions+1 while the mmp doesn't, which would mean that there is not enough pathing data for the whole map, or more texture data than actual ground. Both seems unreasonable. Someone mind elaborating on this?