Redirects are keywords which change the flow to another page. This may be done for searching pages for content which does not have a page, has been moved/renamed, or has been merged to another page.
Redirects can be created by typing #REDIRECT [[<destination link>]] as the first line of the page. The word redirect is case-insensitive. The page can have content after the redirect, but it is usually avoided. The destination link can also be a specific section on another page. Neither the redirect nor the destination link need to belong to the main namespace.
Redirect pages do not have a comment section. When the redirect is removed, the comment section reappears with the previous comments (if any) if the page is a main namespace page.
[]
When content is meant to be searched, it is allowed to create redirects. This includes the following cases:
- The characters used in the name are non-standard characters - A redirect (with the same disambiguation) is created by replacing the non-standard character with a standard character. Example: Arbaletrier redirects to Arbalétrier.
- An important term does not have a page - A redirect is created to the non-main namespace page it most closely resembles. Example: Patch redirects to Template:Patch Nav, and Game mode redirects to Category:Game modes.
Moving pages[]
Main namespace[]
When a content gets renamed, the article must be moved to its new name and a redirect must be created from its older name to its newer name. After the page has been moved, disambiguation with the previous name gets negated.
For example, after having moved Faith (Age of Empires IV) to Proselytization, we create a redirect from the former to the latter, and rename Faith (Age of Empires II) to simply Faith. The disambiguation would still exist if there were a third page named Faith, say Faith (Age of Mythology).
After the rename, the links must be updated to reflect the new name and link.
Other namespaces[]
Redirects in other namespaces is usually useless, since most of them are not meant to be searched. Except when formally allowed, it is not allowed to create redirects. The responsibility of resolving redirects lies upon the user moving the content or the owner of the page (like user blogs).
When a user changes their handle, fandom bots automatically move the user and user talk pages with a redirect, which must be deleted unless they have atleast one link pointing to them.
Merging pages[]
Pages are merged when the article about the contents is identical (except cosmetically). For example, two units having the exact same statistics but different name and/or icon. Some minor ability differences may be ignored. In Age of Empires IV, the units Knight and Lancer are statistically identical, where the former is available to European/Christian civilizations, the latter is available to Asian/non-Christian civilizations.
When merging pages, the older name still exists - just the content of the article is moved to another page. As such, all disambiguations remain as they were. Links may or may not be changed.
If a non-unique content is merged with another non-unique content, the display title and name in the infobox must be updated accordingly. The different name must also be mentioned, along with the civilizations for which it is different, in the introduction (before the first heading) of the article. For example, after merging Knight (Age of Empires IV) to Lancer (Age of Empires IV), the display title has to be changed to Lancer/Knight (Age of Empires IV) or Knight/Lancer (Age of Empires IV). This can be done with {{DISPLAYTITLE:<new title>}}, which has to be placed at the bottom of the page.
If a unique content is merged with a non-unique content, like Oda Tactics with Elite Army Tactics, this change can be mentioned in civilization bonuses. If it has a different icon, it is shown with the name of the civilization.
Other merging cases[]
Pages for animals, trees, maps, and hero units are always merged (and the latter is separate from their campaign page if it exists). In these cases, redirects are not needed.
| Policies and guidelines | ||
|---|---|---|
| Content | Interaction | User rights |
|
||
| Simplified ruleset | ||