Editing Map file
From Halopedia, the Halo wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 7: | Line 7: | ||
==Overview== | ==Overview== | ||
Within the Blam engine, [[tag]]s serve as individual containers storing data about a given subject. These include but are not limited to: models, textures, ai, vehicles, weapons, projectiles, scenery objects, and level data. Tags can be created and edited using the ''[[Halo Editing Kit]]'' components ''[[ | Within the Blam engine, [[tag]]s serve as individual containers storing data about a given subject. These include but are not limited to: models, textures, ai, vehicles, weapons, projectiles, scenery objects, and level data. Tags can be created and edited using the ''[[Halo Editing Kit]]'' components ''[[Guerilla]]'' or ''[[Foundation]]''. One tag type, know as a '''scenario''' tag, stores the necessary information required to compile an actual level, such as the map model (BSP), lighting, scripts, positions of player and enemy spawns, weapons and vehicles, objectives, and so forth. Scenario tags can be edited in the ''Halo Editing Kit'' component ''[[Sapien]]'' which gives a 3D view of the scenario. | ||
Scenarios can then be played in the ''Halo Editing Kit'' component ''[[Tag Test]]'' or compiled using the component ''[[Tool]]'' to create a map file. Compiled maps share their name with the scenario they were compiled from and contain all of the same info in a compressed format superficially similar to a .zip file or a .pak file. Map files are self contained and no longer reference any info from the ''Halo Editing Kit''. Because of this it is possible for two or more separate map files to contain different versions of the same tag or tags. This is what allows mod authors to upload new maps containing custom tags that do not overwrite any retail data. While maps do not share data directly with other maps of the same type (campaign, multiplayer, etc) they may inherit data from a shared map. Shared maps may be created for the purpose of optimizing frequently used tags such as multiplayer characters. | Scenarios can then be played in the ''Halo Editing Kit'' component ''[[Tag Test]]'' or compiled using the component ''[[Tool]]'' to create a map file. Compiled maps share their name with the scenario they were compiled from and contain all of the same info in a compressed format superficially similar to a .zip file or a .pak file. Map files are self contained and no longer reference any info from the ''Halo Editing Kit''. Because of this it is possible for two or more separate map files to contain different versions of the same tag or tags. This is what allows mod authors to upload new maps containing custom tags that do not overwrite any retail data. While maps do not share data directly with other maps of the same type (campaign, multiplayer, etc) they may inherit data from a shared map. Shared maps may be created for the purpose of optimizing frequently used tags such as multiplayer characters. |