Help Edit The Wiki! Click Here to Register Now!

From Fiesta Wiki

Jump to: navigation, search

View relevant sections for editing help specific to that section.



"What will wiki do to my code?"

The Wiki software does a pick-and-match-and-replace-with-some-intelligence on your input. What is replaced depends of course on what your input has!

Text formatting

Bold and italic

Bold text is created by quoting using three apostrophes.

'''Bold text'''

will look like Bold text. Of course, you may also use the HTML standard,


Italic text is created by quoting using two apostrophes.

''Italic text''

will look like Italic text. Of course, you may also use the HTML standard,


A combination of the two is possible:

'''''Bold and italic text'''''

looks like Bold and italic text.

HTML text decorations

Do not leave HTML tags unclosed!

Underline is achieved by




Color using #RRGGBB format

<font color="#99aacc">Color</font>

Size in pixels

<font size="14px">Size</font>

Several properties may be applied to the same tag at the same time: Big colored text

<font color="#99aacc" size="14px">Big colored text</font>

CSS text decorations

This is commonly used due to greater customisability. They all have the following property:

<TAG style=""></TAG>

Read about CSS at W3Schools.


Wiki special!




These are pages that are included using {{TEMPLATENAME}} and can take on a number of variables. Their standalone pages can be accessed at Template:TEMPLATENAME. Each template should have its help section on their standalone page.

Creation of template

Notes on usage

Formatting standard


Use the formatting below for tables. Cellpadding and background colours should be changed to suit the occasion.

{| border="1" cellpadding="5" style="font-size: 12px; border-collapse: collapse; border: #AAAAAA 2px solid;"
|- style="background:#cccccc"
| 1 || 2 || 3 || 4 || 5 || 6
| 7 || 8 || 9 || 10 || 11 || 12
1 2 3 4 5 6
7 8 9 10 11 12


Spacing is an important aspect of visual presentations. In order to make the Wiki a convenient source of information, it is crucial that its pages are presented in a concise and neat way. Clutters of information should be avoided, and a streamlined page layout should be the aim in mind.

Here are the tools that help create space:

The space

This is the basic space maker. Keep spacing regular!

  • Separate words with a single space
  • Follow every punctuation with a single space
  • A hyphen (-) should have two spaces, one on each side
  • Separate a word and the following group of words in parentheses (things in brackets like this chunk) with a space
  • If you left X number of spacing between two items A and B, and there comes later C and D, and E and F, in similar context, do leave X number of spacing between the latter two too!

The line break

This is another very useful tool which needs a little understanding

  • A single hard-return makes no difference in the processed page - it only aids in editing the code by separating chunks of stuff. Two consecutive hard-returns places text above and below them into two consecutive paragraphs (<p> </p>). Some hard-returns are used to aid editing, typically such that a list of items appear as a list (but only in the code view: example here) so while editing, do not double up the hard-returns if it has not been done for the rest of the page
  • If you desire a SINGLE hard-return in the processed page, the ONLY way to achieve that is by simply using a <br> in the coding!
  • Separation of headers and subheaders and subsubheaders...
    • Leave two empty lines before the headers that have a horizontal divider beneath them (that means, these two: =HEADER= and ==SUBHEADER==) This is so that the page appears to be in sections, as the default spacing is too narrow if an extra hard-return is not inplemented
    • Leave one or no empty lines at all for all the rest of them (that means, these: ===SUBSUBHEADER===, ====SUBSUBSUBHEADER==== etc.) This is simply because these headers are small, have no horizontal divider beneath them, and do not need the extra line-break to section them.

Conformity: Case studies

It is important that similar pages both look and function similarly in order to preserve the holistic nature of the Wiki as an encyclopaedic reference. These are some typical edit faults that show up every now and then.


A hard return is the character that is input when the Enter key is pressed. In the Wiki, one hard-return character amounts to nothing at all in the processed page; two hard-returns separate the two chunks of text above and below them by enclosing them in two paragraphs (<p> </p>). In effect, one hard-return merely helps with organising the code, while two of them make a difference in the appearance of the page.

Irregular spacing between items: This is an example of an extra hard-return inserted by an anonymous user between two Quest templates. The result is that there are gaps between certain entries, while the rest of them do not have any gap.

Page guidelines

This section deals with the style of editing in various pages. This is to ensure conformity amongst similar pages. You can read FiestaWiki:Templates about templates, which are very commonly used in these pages.

Monster Drops

Template:Drop has details on its usage.

Please read the following guidelines to ensure that edits from different contributors conform.


These cells should have values LQ, Norm, HQ, and/or HQ+. If more than one grade is dropped, use comma with a spacing (, ) to separate the two.

Quest Items

Use in-game spelling. Separate entries using the <br> tag. Do not hotlink item names.


Write the generic item name here. For example, any kind of Silver Ring should be entered as Silver Ring. For green weapons, shields, and armors, omit the prefix/suffix of the item name. It is clear that the equipment dropped will be green, so they are unnecessary.

In the list, arrange it so that the Return Scrolls come first, followed by any supplementary materials (eg. ores, gemstones, or jellies), then the metal lumps, and finally equipments.

Monster pages

Monster pages are articles whose titles are the names of monsters found in the game. All spelling strictly adhere to the in-game spelling, which can be found in the list at Monster Index. Please edit these pages following the guideline below. You can find the pages that need attention either by looking at, or by following the red links in Monster Index.


  • Stub: Use template {{Stub}} to tag a stub. This should be placed above everything else, on its own line. Pages that do not have a completed Stats section or a completed See also section should be tagged as a Stub.
  • No monster picture: Use template {{Needimg}} to tag these pages. This should be place above everything else like {{Stub}}. These two can be placed on the same line. Pages that do not have the representative pictures (see below) of the monsters should be tagged by this.

Page structure

View example
Each monster page should have the following, in the same order:

  • Monster picture - [[Img:Monster_Name.jpg|thumb|right|A Monster]]. Details below.
  • 'Stats' subsection - Use Template:Monstats in this section. View the template for details.
  • An 'Other' subsection - This can be omitted if there isn't any other useful information related to the monster.
  • 'See also' subsection - This is where templates for monster location, monster type, and monster grade are used.

Monster picture: This should be of a small size like the one in the example. It should also be against a dark background if possible. Please, name the file in a systematic way. It should bear the same name as the monster, plus an extension in lowercase.
Stats: This is simple enough. Level and HP can be found in Monster Index. The Grade, Type, and Location attributes can be found by viewing What links here in the toolbox to the left of the page. You should click on '500' in the choices for View. Inspect the list for 'Template: _____' entries, and you will have a clear idea of what type and grade the monster is of, and also all occurances of it location wise. This information will also be needed later for the 'See also' section.
Other: This is where other information on the monster goes. In the example page, this section contains Drop information.
See also: This section should have the link [[Monsters]], followed by the relevant templates. You should already know what these templates should be. Arrange them so that Location comes first, then Type, then Grade. There is no need to place a [[Category:Monsters]] tag here anymore - it is now embedded in Template:Monstats.

Sample layout

Use this to fill out new pages if you wish. The following code template is exhaustive, so remove any unused or irrelevant items.



==See also==

{{MAP1 Monsters}}
{{MAP2 Monsters}}
{{MAP3 Monsters}}
{{MAP4 Monsters}}
{{MAP5 Monsters}}
{{GRADE Monster}}
Personal tools

Top Searches:
level map


Recent Searches:
mushroom f
Citrie ice
avant garde
103 quest
75 mage set