Mission Wiki Editing Guide

From TMTM Wiki
Jump to navigation Jump to search

This is a general guide for creating a wiki page for a TMTM mission. Please ensure that you're following the guide below to ensure that mission pages follow a consistent standard.

NOTE: Please ensure that all wiki pages have correct spelling and grammar. It's *insert current year*, spell-check is a thing.

Creating a page for a mission will require the following sections.

Mission Page Template

The mission page template can be included using the following code on the page. See below for an explanation of each variable.

| name =
| image =
| author =
| map =
| gamemode =
| type =
| playercount =
| version =
| repository =


This should be set to the name of the mission. It can optionally be deleted, at which point the page name will be used instead.


The loading screen image for the mission should be uploaded to the wiki, and the file name should be written here. Please upload the image in .png format, named in the following format:



This should contain the author(s) that created the mission.


This should be set to the map that the mission is played on. Templates have been created for each of the maps that we use. Please use those templates, as they automatically include the mission in the appropriate categories. The list of map templates is below:



Similar to the map, templates have been created. Please use one of the below for the gamemode that matches the mission.



Similar to the map, templates have been created. Please use one of the below for the type of op.


A Main Op would be a full length op played either on a Thursday or Saturday.
A Side Op would be an op such as Paintball or Nyx Race.
And a Sunday Op is fairly self explanatory, and supports lower player counts and Advanced Medical.


This should be set to the number of players that the mission supports. Zeus slots should be indicated using a "+" sign. Ex: 52+1 for 52 player slots, and 1 Zeus slot.


This should be set to the latest playable version of the mission. This should match how the mission version numbers are written in the mission name.


This should link to the repository of the mission (if available). An example of how to configure the link is below. Use a single space to separate the url, and the text. Set the text to the name of the website that the URL is hosted on.

[*url_goes_here* *DisplayText_goes_here*]
[https://github.com Github]


This should follow immediately after the mission template. Use the quote template to create a quote from the mission. This could be something from the briefing, something that the mission maker said, or something present within the mission.

{{Quote|*Quote text goes here*|*Quote location goes here (ex. Mission Briefing)*}}


This should include a description of the mission in question. Pretty straight-forward.


This should include a list of friendly assets present in the mission. Use a list for this.


This should include a changelog of the various mission versions. Use third-level headings for this (three "=" signs). Generally the first version will be listed like so:

===Version 1.0===
Initial Release