游戏中的地图（Maps in the game）.doc

游戏中的地图（Maps in the game） The map in the game 2009-03-03 21:59 on the map: Legend of Sword and Fairy map block (Tile) size is 32X16 (in pixels). The actual size of each block is 32x15 (in pixels), and stitching is just perfect. The map size is 128x128 (in block plots). The arrangement is as follows: 02468...... / / zeroth 13579...... 02468...... / / first 13579...... The advantage of this approach is that it is easy to determine where the blocks are visible within the screen and only visible portions are visible at a time. The map is divided into two layers, the bottom and the surface. Each block attribute occupies 4 bytes (2 bytes at the bottom and on the surface). So the size of the entire map is 128x128x4=64K bytes. Thats a coincidence, isnt it? DOS under memory, a paragraph is so big) The properties of each block are as follows: Typedef struct { Unsigned No:8; / / block number Unsigned Height:4; / / block height Unsigned Add:1; / / block number high Unsigned Block:1; / / obstacle marker (here can not go, such as the wall) Unsigned Actor:1; / / character mark (someone here NPC) Unsigned Switch:1; / / map switching sign (people come here to switch to another scene) } TCell; Notes： 1, GroundNo = 4, if GroundAdd = 1, then the actual GroundNo + = 256, GroundNo = 300. 2, each map up from 2 (8+1) 512 square blocks into different work. In actual applications, about 300 maps are used for each map. 3, the characters are about 3 blocks high, so the 4 bit Height is enough to deal with the occlusion effects of characters and scenes. About characters: Characters are located between the bottom and the surface. The height of the block is used to deal with the relationship between the characters and the scene. However, there are also relations between characters, how to deal with it? My method is to create a character list, using the painter algorithm. The relationship between characters is easy to calculate: first compare Y, and then compare X, small first painting. However, suc