here.
''Italic Text''Will show up as Italic Text.
'''Bold Text'''Will show up as Bold Text.
'''''Bold & Italic'''''Becomes Bold & Italic.
<span style="color: purple;">Change text colors</span>Can be used to Change text colors. This should be used VERY sparingly as it may not look good on all skins in our wiki and violates the hard work of our skin designer.
<u>Underline</u>Will Underline things.
<s>Strikeout</s>Will
<big>Big</big>Makes things Big
<small>Small</small>Will make things Small.
<center>Center</center>Will center justify text,
[[Guidelines]]Gives you a link to the Guidelines page.
[[Guidelines|Clarifications]]Gives you a link to the Guidelines page, but displays as Clarifications
[[Category:Lore]]Adds the current page to Category:Lore. This is a "Compiler Directive" and does not display anything.
[[:Category:Lore]]Gives you a link to Category:Lore without adding the current page to that category.
[[:Category:Lore|Lore]]Gives you a link to Category:Lore but displays as Lore
Please Note For common terms, a link needs to follow this syntax [[Hume (FFXI)]] or [[Hume (FFXI)|Humans]]. The former will display as Hume and the latter will display as Humans but they both lead to the same page. More info can be found on the guidelines page, under Common Terms.
Also Note Linking part of a word such as [[Windurst]]ian will create a link to Windurst but will display as Windurstian.
[[Yagudo#The Yagudo Theomilitary|The Yagudo Theomilitary]]Will take you to a specific heading on the Yagudo article, and will display as The Yagudo Theomilitary
[http://www.google.com Google Homepage]Will display as Google Homepage and is preferred for making external links.
[http://www.answers.com/reference&r=67]Will display an inline reference [1] For citing external links. They do not generate footnotes [2].
<ref>This is a footnote</ref>These tags will create a footnote. Click the footnote link to jump there, then click the ^ to return here.[1] This does not auto generate a note's list. To make the text within the tags appear on the page you need to add a few bits of code at the end of your article.
==Notes==
<references />This will add a section header for Notes, and will parse everything inside a pair of ref tags into a numbered list wherever you place the references tag.[2] Please, for style and organizational purposes, keep the notes section at the bottom of your article.
==Header 1== ===Header 2=== ====Header 3==== =====Header 4=====Are the four varying degrees of headers. The questions in this FAQ are Header 1, while the subsection headers like "Basic Text Formats" are Header 2.
Note: if you use 3 or more Header 1, in combination with any other headers, a table of contents will be generated using the text encased in the header tags, like the table of contents at the top of this page.
Note: If you use a link to a DB namespace, such as EQ2_Zone:, in a header the Table of Contents will show the namespace unless you include alternate text for the link, such as [[EQ2 Zone:Antonica|Antonica]].
By default, the Table of Contents will appear just before the first Header 1. You can force it to appear elsewhere with __TOC__ or prevent it from appearing at all with __NOTOC__ (placed anywhere in the article). These are called "Compiler Directives".
* Asterisks and ** Double Asterisksshow up as
# Hash Marks and ## Double Hash Marksbecome
# Hash Marks and #* Hash Mark-Asterisksbecome
* Asterisks and *# Asterisk-Hash Marksbecome
These can be mixed and matched!
#Do this step first
#Secondly, do the following in any order
#*a task
#*another task with 3 steps that must be done in order
#*#Step 1
#*#Step 2
#*#Step 3
#Final task
becomes
Tables can be very daunting and complicated, but they can be very useful for organizing lists of information in articles. There are numerous bits of code that you need to be aware of when putting together a table.
{| and |}Begin and end a table. Tables can be nested within tables, but doing so can make what is already complicated, even more complicated.
|- and |Will respectively add a new row and a new cell. Note that these tags to not need to be closed if you start each | on a different line. Beginning a new row or cell will close the previous one, and the final closing table tag will close the final row or column tag.
!Is a special header version of the cell tag, using this tag will bold the text following it, and center it within the cell.
|+Is a caption tag, any text that is placed after it will be centered above the table, as a sort of title.
{| border=1 |+ This is an example table. |- ! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |}
header 1 | header 2 | header 3 |
---|---|---|
row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |
row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |
||In some cases, a double pipe tag can be used instead of placing each cell tag on a new line.
style="background:black; color:purple"Adding this after a row or cell tag will change the background and text colors. This example, placed after a row tag will make every cell within that row have a black background and purple text.
border=1By default, tables do not have a drawn border around them. Adding this tag can help organize information. The numerical value in quotes is a pixel width for the border.
width=100%This tag, placed after an opening table tag, will determine the overall width of your table. The example shown, will force the table to stretch all the way across the wiki article. If the reader resizes their browser, the table will expand and contract to reflect this. You may also specify pixel widths.
{| border=1 width=100% |+ This is an example of an advanced table that is 100% the width of the wiki article. |- style="background:yellow; color:grey" ! header 1 this row is grey text on yellow ! header 2 ! header 3 |- | width=50% | row 1, cell 1. This column will always... | width=150 | row 1, cell 2. this column will always... | row 1, cell 3 |- | style="background:white; color:black" | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |}
header 1 this row is grey text on yellow | header 2 | header 3 |
---|---|---|
row 1, cell 1. This column will always be 50% of the overall table width, and the text will auto wrap to fit within it. | row 1, cell 2. this column will always be 150 pixels wide, no matter how large or small the overall table is. | row 1, cell 3 |
row 2, cell 1 has a white background and black text. | row 2, cell 2 | row 2, cell 3 |
Bludwyng has made a set of game tags that can be used on any page to display a little graphic and automatically link that page to the game's category so the search engine will see it. See the complete list on the Global Template Users Guide.
First, please pick a name that makes sense! Use the Search box to see if the name already exists. If it does and is in use by another game, disambiguation will be necessary. To disambiguate, add " (EQ2)" after the name. Also, the other game page will need to be moved to a name that is similarly disambiguated, and a disambiguation page should be created at the original name. The disambiguation page should have links to both pages, and should end with {{disambig}}. More explicit information about disambiguation is available, below, under Q: What do I do if two in-game things have the same name?
Other than that, just be sure to place the {{eq2}} tag on the bottom of your article so that the page is placed in the EverQuest II category. This is absolutely required or the Everything Search will not see the page!
Examples:
The link format is the same as for FFXI (described above).
The link format is the same as for FFXI (described above).
There are 2 ways, external and internal.
For an externally-hosted image:
For an internally-hosted image:
You must use disambiguation to separate them. How this is done depends on what the thing is. The following examples are for EQ2, but the principle is the same for all games.
For a Quest:
For an Item:
For a Mob:
Currently, using the Move function does NOT do something that most other wiki's do:
Here is the recommended procedure:
The two different colors represent links to pages that do exist, versus those that do not yet. In a standard Wiki color scheme existing links would be blue and missing links would be red. This is why missing links on a wiki are universally referred to as "redlinks".
The actual colors depend on the color scheme of the game base you are looking at. For instance, on the EverQuest II Wikibase, existing links are yellow and "redlinks" are orange.
Allakhazam's Wikibase is NOT Wikipedia. We do not expect dry, emotionless, researched and peer-reviewed work here. We are gamers, all of us, and we use language differently from college professors. However, the wiki is NOT The Asylum, and things that are permitted there will not be allowed here. Any edits containing rude or vulgar comments, hate speech, racist or sexist remarks, or profanity will not be tolerated and could result in your access to this system being revoked. We cannot block users from the wiki separately, so the only tool we have is the ZAM Mute or Ban, and we will use them on repeat offenders. You will be warned first, to give you an opportunity to behave, but no second warning will be given.
Basically, restrict yourself to language that would not embarrass the average person should their mother happen to read it over their shoulder.
This rule extends to all parts that touch on the Wikibase, including but not limited to: Wiki text, database page comments, edit summary lines, and the Wikibase Forum.
There is no practical limit to the size of a wiki page. However, if it gets THAT big it probably needs to be split into multiple smaller pages that cover specific parts of the original.
Additionally, there is a limit to the total number of templates that may be called on a given page during the compile process. This means all the templates on the page, and all the templates they call as sub-templates, and all the templates those sub-templates call, etc. This can add up very fast. The worst place this is seen is on some very large Quest Series pages. When this happens the best thing to do is to split the Quest Series page into 2 or more sub-pages and point to each of them from the original page name.
A good example of this can be seen in the Runes of Magic wiki, on the Sascilia Steppes Quest Series page. This one zone covers quests from level 1 through 20 and it is the single largest overland zone in the game. It is, quite truly, huge by RoM's standards. I reached a point where the only choice was to split it into North (1-11) and South (14-20) sub-pages.