Template - Mods - XCOM:EU 2012

From Nexus Mods Wiki
Revision as of 15:27, 30 April 2013 by Amineri (talk | contribs) (Added Compatibility subsection and Known Issues section)
Jump to: navigation, search

[This is a template. Please do not make any changes to this page. Instead, copy the contents below to a new page, and replace anything within {curly braces} with your own appropriate material.]


Overview

{ A very general synopsis description of the Mod. }

Game Version Compatibility

{ This subsection should give the game version (e.g. Patch 4 ( Changelist: 356266 ) ) that the mod is compatible with. }

Known Issues

{ This section should document any side effects or glitches known to be caused by the mod. This can include bugs that have yet to be fixed, as well as unavoidable side effects or UI issues that the player may experience. }

Programs and Tools

{ This section should list and if possible provide links to any program and/or tools needed to replicate your exploration of this subject or installation of the Mod. The section should not be omitted. Note that 'none are required' in that case. }

Details

{ Create an many subsections here as are useful to organize and describe what the Mod does in detail. Remember that you can upload and link to screenshot files to illustrate where ever needed. See this page for help on including files in your article. }

File Changes

{ This should be a general description of all files affected by the Mod, and if it is significant, they should be listed in the required installation sequence. If the install sequence is not significant, it is helpful to note that. When multiple files are involved, they should be linked immediately after the description of what they change, and also linked in the 'References' section in the same order.

{ 'Code Breakdown' is where the hex code is explained by added comments. It is placed within a block pair of 'nowiki' and '/nowiki' (within <angle brackets>) HTML 'markup tags' to preserve the formatting. (Note it is REQUIRED to put a leading space before the 'nowiki' markup tag. The closing tag can be on the last line or after it, and does not require a leading space.)

For example:

original hex: (virtual size 0x552)
header:
DB 7C 00 00 50 55 00 00 00 00 00 00 C0 7C 00 00 00 00 00 00 00 00 00 00 C6 7C 00 00 00 00 00 00 A9 02 00 00 2C 5C 00 00 52 05 00 00 B6 03 00 00 

body:
if(!DoesDamage())
07 19 00 81 1B 9B 1A 00 00 00 00 00 00 16 16 

return iHitChance;
04 00 C6 7C 00 00 

This preserves the authors necessary non-HTML format.

A Code Breakdown that at least identifies the significant bytes a player may wish to adjust to their own purposes should be the minimum provided. If the installer the mod was designed to work with does not support embedded comments or descriptions, then separate Code Breakdown and Mod Install files should be provided.

Install files should provide the following either internally of the file or externally at the point the file is described, in any suitable order: }

MOD NAME:

MOD FILE NAME: { Include " 'number' of 'total number' " if appropriate. }

AUTHOR:

FILE REVISION NUMBER:

COMPATIBILITY: { This should indicate game revisions/patches known to be compatible with this version of the mod, and compatible installers.  A mod user should not be expected to alter anything more than the minimum of desired settings and values.  If they will be required to perform more complicated adjustments, the expected level of proficiency should be explained. }

DESCRIPTION: { A summary of the file's purpose within the overall Mod. }

ADDITIONAL INFORMATION:  {
* Tables or lists with the values to be used to effect the desired results within the mod should be provided where available, or links to that information.
* Affected files and whether or not backups of those files are necessary or handled by the installer automatically.
* How to revert the mod, or links to the relevant information (i.e. [http://wiki.tesnexus.com/index.php/Steam_and_mods Steam_and_mods on the Nexus XCOM Wiki].)
}

{ The files needed to implement the mod should be placed on their own pages and linked from the appropriate points in the article. It is desirable to group them in one place, but use whatever works best to convey the information. All referenced links should also be include in the 'References' section below, as that is where people will look when they only want those links. }

Localization Changes

{ Detail any language localization changes that are required. This section should not be omitted. Simply note that 'none are required'. }

References

Guidelines_for_new_posts_-_XCOM:EU_2012
How_to_post_a_new_wiki_page

{ Specific page links go here, even if already referenced in the main body of the text. Put the HTML tag 'br' (inside <angle brackets>) after each line so they will display on their own separate lines. Use the entries above, the first of which links to the parent subject of which this is a child link, as an example. }

{ Below the specific page links will be the 'Category' links. The category names be placed within double [square brackets]. Multiple categories are not unusual, but must each be placed on their own line. The Category:XCOM is standard and also serves as an example. These category links will appear when you click on the 'Show preview' button, but in the Category frame below the edit window action buttons. IF a category page does not yet exist, it will appear in RED. You can click on the red entry and commence the process of creating the category page even before saving the one you are currently editing. }