{"id":605,"date":"2010-07-25T18:45:37","date_gmt":"2010-07-26T02:45:37","guid":{"rendered":"http:\/\/technofovea.com\/blog\/?p=605"},"modified":"2010-07-25T18:48:09","modified_gmt":"2010-07-26T02:48:09","slug":"map-includes-for-various-mods","status":"publish","type":"post","link":"http:\/\/technofovea.com\/blog\/archives\/605","title":{"rendered":"“Map includes” for various mods"},"content":{"rendered":"

For PackBsp 2.0.2, I’m working on a configuration system for various “map includes”, or things which various mods need which are directly affected by the name of the map. For example, consider internationalized map descriptions. As a general rule, they follow the form of\u00c2\u00a0maps\/%m_%l.txt<\/code>, where %m <\/code>is the map’s name without the trailing .bsp<\/code> extension, and %l<\/code> is one of many different language codes.<\/p>\n

I need help to make sure that this system has good default values that will work for most people. The plan is that it will first look at the name of the game (ex. Team Fortress 2<\/code>) and also at the engine code (ex. orangebox<\/code>). Using those it will find the different include patterns that are necessary for that particular game.<\/p>\n

<\/p>\n

The problem is that without having mapped for each game, I don’t really know what each one needs in terms of these includes. Here’s what I have so far, in the user-editable configuration file:<\/p>\n

\r\n<?xml version="1.0" encoding="UTF-8" standalone="yes"?>\r\n<mapIncludes>\r\n    <include id="soundscape"\r\n             path="scripts\/soundscapes_%m.txt" type="soundscape"\/>\r\n    <include id="particlemanifest"\r\n             path="maps\/%m_particles.txt" type="particles"\/>\r\n    <include id="ain"\r\n             path="maps\/graphs\/%m.ain" type="plain"\/>\r\n    <include id="nav"\r\n             path="maps\/%m.nav" type="plain"\/>\r\n    <include id="description"\r\n             path="maps\/%m.txt" type="plain"\/>\r\n    <include id="international_description"\r\n             path="maps\/%m_%l.txt" type="plain"\/>\r\n    <include id="photos"\r\n             path="materials\/vgui\/maps\/menu_photos_%m.vmt" type="material"\/>\r\n    <include id="overview"\r\n             path="materials\/overviews\/%m.vmt" type="material"\/>\r\n    <include id="overview_text"\r\n             path="resource\/overviews\/%m.txt" type="plain"\/>\r\n    <include id="radar"\r\n             path="materials\/overviews\/%m_radar.vmt" type="material"\/>\r\n\r\n\r\n    <game name=":base">\r\n        <includeIds>description international_description<\/includeIds>\r\n    <\/game>\r\n\r\n    <game name="engine:ep1" parent=":base">\r\n        <includeIds><\/includeIds>\r\n    <\/game>\r\n\r\n    <game name="engine:source2007" parent="engine:ep1">\r\n        <includeIds>soundscape<\/includeIds>\r\n    <\/game>\r\n\r\n    <game name="engine:orangebox" parent="engine:source2007">\r\n        <includeIds>soundscape particlemanifest <\/includeIds>\r\n    <\/game>\r\n\r\n    <game name="game:Team Fortress 2" parent="engine:orangebox">\r\n        <includeIds>nav photos<\/includeIds>\r\n    <\/game>\r\n    \r\n    <game name="game:Counter-Strike: Source" parent="engine:orangebox">\r\n        <includeIds>nav ain overview overview_text radar<\/includeIds>\r\n    <\/game>\r\n\r\n    <game name="game:Day of Defeat: Source" parent="engine:orangebox">\r\n        <includeIds>nav ain overview overview_text<\/includeIds>\r\n    <\/game>\r\n<\/mapIncludes>\r\n<\/pre>\n
Actually getting the content<\/b> of this right is the main thing holding back 2.0.2 right now. What do I put for HL2, HL2:Ep1, HL2:Ep2, etc? Which things are specific to games, versus generally applied to all games on the same engine?<\/p>\n","protected":false},"excerpt":{"rendered":"
For PackBsp 2.0.2, I’m working on a configuration system for various “map includes”, or things which various mods need which are directly affected by the name of the map. For example, consider internationalized map descriptions. As a general rule, they follow the form of\u00c2\u00a0maps\/%m_%l.txt, where %m is the map’s name without the trailing .bsp extension, […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[8],"_links":{"self":[{"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/posts\/605"}],"collection":[{"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/comments?post=605"}],"version-history":[{"count":8,"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/posts\/605\/revisions"}],"predecessor-version":[{"id":614,"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/posts\/605\/revisions\/614"}],"wp:attachment":[{"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/media?parent=605"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/categories?post=605"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/technofovea.com\/blog\/wp-json\/wp\/v2\/tags?post=605"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}