Difference between revisions of "PSU Cyril Wiki:Weapon template"

Revision as of 20:42, 7 May 2008

Below is the code used to generate the page Deva-zashi. It is given here as example of the code needed to generate a complete weapon page. See below for comments.

Code

[[Image:Deva-zashi.jpg|thumb|right|A male CAST wielding a Deva-zashi.]]
''A super high-end dagger used by high-ranking COG officials. The elegant, wing-like form belies its destructive power.''<br>
{{10 stars}}
==Item details==
* Has white feathery effects with attacks.
* May inflict [[Status Effect|silence]] with attacks.
<br>
==Stats, synthesis, etc.==
{| border="0" width="100%"
{| border="0" align="center"
|- valign="top"
|
{{Striking weapon stats
| type = Dagger
| rarity = 10
| pp = 332
| attack = 421
| ata = 361
| version = PSU
| req = 345
| maker = Y}}
||
{{Board stats 10 star striking
| name = Deva-zashi
| photons = ???-photon
| metal = Cladorian
| wood = Neu Walna
}}
||
{{Pricing info
| buy = N/A
| sell = 40500
| shop = N/A
| bbuy = N/A
| bsell = Unknown
| bshop = N/A
}}
|}
|}
{| border="0" width="100%"
{| border="0" align="center"
|- valign="top"
|
{{Grinding info
| attack = ATP
| a0 = 421
| a1 = 427
| a2 = 432
| a3 = 437
| a4 = 441
| a5 = 445
| a6 = 450
| a7 = 456
| a8 = 462
| a9 = ???
| a10 = 479
| pp0 = 332
| pp1 = 342
| pp2 = 351
| pp3 = 359
| pp4 = 366
| pp5 = 373
| pp6 = 381
| pp7 = 391
| pp8 = 402
| pp9 = ???
| pp10 = 432
}}
||
{| class="wikitable" style="text-align:center"
|-style="background:#e8e8e8"
| colspan="4" | '''Drop information'''
|-style="background:#f2f2f2"
| '''Enemy/Mission''' || '''Level''' || '''Type''' 
|-style="background:#f9f9f9"
| [[Goshin]] || 100+ || Board
|-style="background:#f9f9f9"
| [[Zamvapas]] || 100+ || Board 
|-style="background:#f9f9f9"
| [[Sakura Blast]] || S || Board 
|-style="background:#f9f9f9"
| [[Sakura Blast]] || S || Weapon
|}
|}
|}

==Image gallery==
<gallery>
Image:Deva-zashi2.jpg|Feather effects when swinging the Deva-zashi.
</gallery>
[[Category:Daggers]]

Comments

• As should be obvious, each weapon has its own individual statistics, synthesis information, drops, etc. For most weapons, simply changing the fields (ATP, rarity, manufacturer, synth ingredients, drops, etc.) is very simple to do.
• Different types of weapons will require a slightly different set-up for the statistics table. Most notably, TECHNIC-casting weapons do not have ATA values, therefore the TP cell will take up two rows (cf. Uransara).
• If a picture is available for the weapon in question, fill in the first line (and remove the HTML comment-code) to add the picture. If additional images exist, do the same to final lines of code (also removing the text concerning image uploading).
• The second line of code should include the exact description of the weapon as it appears in the game.
• If the first image uploaded is vertically large, additional line breaks may need to be added before the "Stats, synthesis, etc." subtitle, lest the underlying tables be displaced by the right-aligned image.
• The "Item details" subsection should include objective information concerning the weapon, such as unique graphical or audio effects, and status conditions associated with the weapon, if any. If no interesting features exist, note that in this section.
• Image captions should be objective descriptions of exactly what is shown. In most cases, this will be "A male human wielding a Deva-zashi" or something of that nature. Do not use the caption field to give credit to the uploader/originator of the image. This is better done on the page for the image itself.
• For the "Synth rate" field in the synthesis table, give the absolute range of synth rates for the weapon in question. For striking weapons, use elemental statistics, not non-elemental. For Deva-zashi, give the rate on a 0 striking PM, followed by the rate on a 100 striking PM. Likewise, 0 TECH to 100 TECH for casting weapons, and 0 range to 100 range for ranged weapons.
• When in doubt as to how to address a certain issue, check other similar pages to see what has been done, and try to work from there. If there are still questions about this style, leave them on this article's talk page.