-
Notifications
You must be signed in to change notification settings - Fork 32
Auxiliary Components
The two main phases: generation and runtime are supported by the two main components: the map builder and the path finder, respectively. namigator additionally relies on three other separate components.
namigator reads game data from the MPQ data files using the stormlib library. The development of namigator has led to several contributions to this excellent toolkit.
The utility component provides generic capabilities relevant to namigator's goals. Examples are linear algebra and trigonometry calculations, computational geometry operations like ray tracing, file I/O, compression and decompression, and hashing. The utility component depends on no other components.
The parser component depends on stormlib and the utility component, and will extract all necessary information from the data files of the game. Examples of this are terrain data, object positions, model shapes and sizes, and more. The map builder component relies on the parser, but the path finding component does not.
The map viewer component is not required for any aspect of using namigator, but is included as a hopefully useful tool. The purpose of the map viewer was to render data produced by namigator for debugging purposes.