Deadline Mission File: Difference between revisions
Jump to navigation
Jump to search
(Deadline example mission file) |
m (links, source) |
||
Line 1: | Line 1: | ||
This is the mission metadata file included with the sample Deadline campaign. | This is the mission metadata file included with the sample Deadline campaign. Feel free to use this as a template for the metadata while for your own [[Add-on|custom campaign addons]]. | ||
Remember the URL in the Website key should point to the home website to your mission and have a download option there! Players who don't have your mission will be directed to this website to get it. | Remember the URL in the Website key should point to the home website to your mission and have a download option there! Players who don't have your mission will be directed to this website to get it. | ||
<source lang=ini> | |||
// Mission files describe the metadata needed by campaign-specific add-ons so they can be | |||
// integrated into Left4Dead. The data in this file is used by the game UI, matchmaking and server. | // integrated into Left4Dead. The data in this file is used by the game UI, matchmaking and server. | ||
// Although you may provide multiple Campaigns in one add-on by putting more than one .TXT file | // Although you may provide multiple Campaigns in one add-on by putting more than one .TXT file | ||
Line 135: | Line 136: | ||
} | } | ||
</source> | |||
== See also == | |||
* [[L4D_Campaign_Add-on_Tutorial]] | |||
[[Category:Left 4 Dead]] |
Revision as of 15:39, 25 June 2009
This is the mission metadata file included with the sample Deadline campaign. Feel free to use this as a template for the metadata while for your own custom campaign addons.
Remember the URL in the Website key should point to the home website to your mission and have a download option there! Players who don't have your mission will be directed to this website to get it.
// Mission files describe the metadata needed by campaign-specific add-ons so they can be
// integrated into Left4Dead. The data in this file is used by the game UI, matchmaking and server.
// Although you may provide multiple Campaigns in one add-on by putting more than one .TXT file
// in the missions folder, it's generally a good idea to stick to one per add-on.
//
// HOW TO DEBUG MISSION FILES:
// In the console set "developer 2"
// Then type "mission_reload"
// This will make the game reload all the mission files and print out every chapter for every mode it
// finds. It's very useful to ensure that your mission file is being correctly read.
"mission"
{
// Use a short name, since it is used as a tag on the servers for matching
// your campaign when looking for a dedicated server. Generally it should
// be something unique. One suggestion to is use your initials and a short
// abbreviated name for your campaign.
"Name" "Dead Line"
// The version number is used when finding campaigns on dedicated servers
// and in matchmaking. If you try to connect to someone in matchmaking
// who has a newer version, you will be directed to download the new
// version. You must increment this to the next integer (whole numbers)every
// time you release an update.
"Version" "3"
// Author is displayed in the UI when people see others playing your
// campaign.
"Author" "Valve"
// Website is extremely important as people will automatically be sent
// to this URL if they try to join a friend running your campaign. This
// should be the home page for your campaign and it should provide a
// description, a link to download it, and installation instructions.
"Website" "http://media.steampowered.com/apps/513/deadline.html"
// This name is used when refering to the campaign in the UI.
"DisplayTitle" "Dead Line"
"Description" "Catch the last subway... out of hell."
// Vmt shown behind the end credits when your campaign completes.
// Note: This item needs to have "vgui\" at the front. It is assumed
// for the poster and the map thumbnails.
"OuttroImage" "vgui\OutroTitle_Deadline"
// Loading poster data
//
// Note that "posterTitle" and "posterTagline" are often blank as
// the poster usually includes these in the poster image itself.
// If you do not provide a poster, a generic default will be used.
"poster"
{
"posterImage" "LoadingScreen_DeadLine"
"posterTitle" ""
"posterTitle_y" "360"
"posterTagline" ""
"posterTagline_y" "372"
// Adjust these to align the survivor names on your poster.
// 0,0 is center of the poster.
"bill_player_name_x" "118"
"bill_player_name_y" "-195"
"louis_player_name_x" "-53"
"louis_player_name_y" "-205"
"zoey_player_name_x" "-124"
"zoey_player_name_y" "-210"
"francis_player_name_x" "31"
"francis_player_name_y" "-200"
}
// The modes section lists each of your campaign maps and each mode
// they support. Depending on how you set up your campaign maps,
// you can reuse the same bsp for different modes as is the case with
// coop and versus in this example. This requires setting up entities
// that show up or operate differently for different modes.
//
// The following modes are supported: "coop", "versus", "survival"
//
// Number each map section starting with "1"
//
// "Map" is the name of the bsp of the starting map. (do not include
// an extension)
// "DisplayName" is the name to use for the chapter of the map.
// "Image" is the image used for the chapter in the lobby and
// settings.
"modes"
{
"coop"
{
"1"
{
"Map" "l4d_deadline01"
"DisplayName" "Deadline 1"
"Image" "maps/l4d_deadline"
}
"2"
{
"Map" "l4d_deadline02"
"DisplayName" "Deadline 2"
"Image" "maps/l4d_deadline"
}
}
"versus"
{
"1"
{
"Map" "l4d_deadline02_vs"
"DisplayName" "Deadline Versus"
"Image" "maps/l4d_deadline"
}
}
"survival"
{
"1"
{
"Map" "l4d_deadline02"
"DisplayName" "Dead Line Survival"
"Image" "maps/l4d_deadline"
}
}
}
}