Template:Scenario

From Traxus

Instructions

Every usage of this template should include, at a minimum, the url. If left blank, the name will default to the title of the page. This field allows the "official name" and "common name" (or whatever) to both be displayed on the page. Any field other than these will display blank if left blank. For logo, just supply the name of the file without the "Image:" namespace; it is automatically resized. I think tagline is pretty obvious.

For engine, put what version of the game is used to play the scenario. It may be the original Marathon 1, Marathon 2, Marathon Infinity, or Aleph One. Number of levels is obvious; if you want to differentiate solo game levels vs netplay levels, that's fine. The a1compat field notes whether the scenario is playable with the A1 engine. Some older scenarios work fine as-is, some need to be ported and haven't been. Developer is the name of the person or team that made it. Linking to the proper article or URL would be great.

Initial and latest are dates of release, version refers to the number of the most recent official release. Status should simply be complete, beta, incomplete, or unreleased: we don't want to get into the morass of determining which development efforts are permanently dead and which aren't.

The next group of parameters are simply flags. Set them to yes if the scenario contains new monsters, music, whatever. This will give a quick idea of how different the scenario is from the standard Bungie Trilogy. The newuniverse one might be confusing; it indicates a non-Bungie setting, so what the player might have learned regarding UESG, etc, doesn't carry over here. Two others are not obvious either: newcoopdesign denotes that the scenario has levels or features designed specifically for players playing in cooperative mode, and new3d denotes that the scenario uses the "true 3D" capabilities of the Aleph One engine.

Note that while the values in the fields are freeform, they are used for categorization in some cases so it is important to be consistent!

Example

You can copy and paste the following blank to get started.

{{scenario
|url=
|name=
|logo=
|tagline=
|engine=
|levels=
|a1compat=
|developer=
|initial=
|latest=
|version=
|status=
|newcoopdesign=
|newmonsters=
|newmusic=
|newobjects=
|newphysics=
|newsounds=
|newtextures=
|newuniverse=
|newweapons=
|new3d=
}}