FANDOM


Examples

Maple Harp

Maple harp
(String Instr.) All Races
Lv. 1 BRD

Happy Egg

Happy eggRareExclusive
All Races
HP +1% VIT +1
Lv. 1 All Jobs

Wooden-Katana

Wooden katanaRareExclusive
(Great Katana) All Races
DMG: 1 Delay: 450
Lv. 1 All Jobs
Damage Per Second: 0.13
TP Per Hit: 115

Melt Dagger

Statistics

Nadrs-candid
Melt dagger
(Dagger) All Races
Lv. 23 WAR / BLM / RDM / THF / PLD / DRK /
BST / BRD / RNG / SAM / NIN / DRG / SMN
Damage Per Second: 3.28
TP Per Hit: 50

Other Uses

Resale Price: Cannot be sold to NPCs.


Nadrs

Statistics

Nadrs-candid
NadrsRareExclusive
(Sword) All Races
DMG: 18 Delay: 236 Trans Water +3
Additional effect: Poison
Lv. 24 WAR / THF / DRK / SAM / BLU
Damage Per Second: 4.58
TP Per Hit: 63


Additional effect: Poison

  • The additional effect triggers more often than most additional effects on weapons.

Other Uses

Resale Price: Cannot be sold to NPCs.

Comments and suggestions

Images

Perhaps, like furnishings, we should allow for screenshot images as well. There are a number of weapons already that have images (e.g. Nadrs), and I think the code we used in furnishing is unobtrusive enough. The only question is will it fit? The item descriptions for weapons and armor might take up too much space... something to think about. --Chrisjander t/ c 14:46, 11 August 2007 (CDT)

Sounds like a good idea to me; Better to have it managed by a template than leave it up to individual editors. I'll add the code and see how it looks. The only problem I see, aside from the space issue, is that people may try to add images for each individual weapon. We'll have to make it clear that it's only to be used on unique-looking weapons. ~ Karuberu 18:43, 11 August 2007 (CDT)

I concur. Unless the weapon has a unique look (isn't just a plain ordinary weapon of its type), then an image would be appropriate. --Chrisjander t/ c 22:31, 11 August 2007 (CDT)

Action shots such as the change recently made to Nadrs breaks the convention of having it appear exactly as it does in the image description, this needs changed. --User:Charitwo/Sig 12:42, 31 October 2007 (UTC)

Seems lower resolutions make the image crowd the text, so we'll have to think of a different placement. --Chrisjander t/ c 12:47, 31 October 2007 (UTC)

It looked fine before we switched to Wikia and got that annoying tower-ad on the right side... oh well. I suppose we could make the thumb smaller, but that wouldn't look too great with landscape images. Perhaps an optional variable for resizing the image? ~ Karuberu 12:59, 31 October 2007 (UTC)

Not sure it will help (tower ad and all), but you can try and and we'll see how it looks on the lower res. --Chrisjander t/ c 13:01, 31 October 2007 (UTC)

Yeah, I'm at work and display properties are blocked, but regardless need to accomodate for viewers of different resolutions. As for the white space, there is a CSS/JS trick that gets rid of it, but I'm still figuring it out. --User:Charitwo/Sig 13:03, 31 October 2007 (UTC)

I'm not concerned so much with ultra low resolutions, those people see everything different anyway because they can't set their screens higher. 1024, on the other hand, is very common and used to be the default for most people. It was the default resolution we were working with when we first designed the item template et al, so the basic function should work in that resolution. --Chrisjander t/ c 13:06, 31 October 2007 (UTC)

File:Nadrs-1024-768.png Yes, currently displaying on 1024 x 768 --User:Charitwo/Sig 13:15, 31 October 2007 (UTC)

The image size variable worked pretty well for Nadrs (I set it at 80px, which looks good at both resolutions), but I have a feeling this issue may come up again if/when the template becomes more widespread. I'll try to think of some other options. ~ Karuberu 13:17, 31 October 2007 (UTC)

Still doesn't look right to me, I am opposed to making this live until it's fixed. --User:Charitwo/Sig 13:18, 31 October 2007 (UTC)

Well, the images are only used for unique-looking weapons, so it's really a very small problem. Try some other sizes and see how it looks; I can't see what you're seeing, so you'll have to be the one to fix it. ~ Karuberu 13:22, 31 October 2007 (UTC)

Are you blind? I just posted a screenshot. --User:Charitwo/Sig 13:24, 31 October 2007 (UTC)
The image doesn't show up (blank on page; 404 on "higher resolution"), but that's beside the point. I changed my resolution to 1024 x 768 and 80px looks right for me; obviously, there's some sort of a difference somewhere. ~ Karuberu 13:34, 31 October 2007 (UTC)
How conveinent... perhaps you have a widescreen monitor? Either way, it's not going to matter, it's just a coincidence that this item in question only has 5 jobs, others have a lot more. Nadrs --User:Charitwo/Sig 13:45, 31 October 2007 (UTC)
It's those lock icons that are causing the problem for you. I don't know what they're from (some security setting?), but without them the page looks fine (on both IE and Firefox). Oh, and I have a standard monitor. ~ Karuberu 14:08, 31 October 2007 (UTC)
I see you missed my point and went straight to the image. --User:Charitwo/Sig 14:12, 31 October 2007 (UTC)
I already addressed that. Items with special images are few and far between, so we can just deal with them on a case-to-case basis for now. If we decide to add images for all weapons one day, then we'll definately need to find a better way, but this will work for now. ~ Karuberu 14:31, 31 October 2007 (UTC)
Ahem. Civility. Now then - I am a bit skeptical about the positioning, but I'd suggest applying the template to the most complex item out there and let's see how it looks. --GAHOO t/ c 14:18, 31 October 2007 (UTC)

The Melt Dagger example looks fine at 1280 x 1024, but at 1024 x 768 it has some serious crowding issues. The image would have to be reduced to around 35px to fit without messing up the jobs, which, needless to say, is far too small, especially when you view it at 1280 x 1024. However, most items with unique models are only used on a few jobs, so I don't think this issue will come up. ~ Karuberu 14:44, 31 October 2007 (UTC)

Paragraph Problem

There's a problem with entering info for stats on multiple lines, presumably caused by paragraph breaks. I tried to remedy the problem by forcing it to be one paragraph with no margins, but it didn't work as planned (it worked for up to two lines, but actually worsened the problem with more than two lines). Here's an example the problem:

Ponderous Lance
(Polearm) All Races
DMG: 92 Delay: 492 Accuracy +2

Ranged Accuracy +2

Enchantment: Stone
Lv. 75 DRG
Damage Per Second: 11.22
TP Per Hit: 133

I have no idea why this is happening. Not only should the <br>s prevent the MediaWiki paragraph breaks, but a single line break shouldn't trigger a new paragraph anyways. I made sure not to have any line breaks in the template's code, so it should still take two line breaks to trigger a new paragraph. I've found no solution to the problem, save entering all the info on one line and avoiding the problem altogether. ~ Karuberu 00:56, 12 August 2007 (CDT)

I've always had that sort of problem in templates (not just this one), so the "enter it as one line" is a solution, and a good one. Fixes it 100% for me. --Chrisjander t/ c 11:11, 12 August 2007 (CDT)

iLevel Rendering

All tries failed in a proper render of the iLevel attribute. Currently its too far away from the description body itself and not right aligned. This is ugly especially with DPS rendered:

Magic Wand
(Wand) All Races
DMG: 92 Delay: 492 Accuracy +2
Lv. 75 DRG
<Item Level: 119>
Damage Per Second: 11.22
TP Per Hit: 133

--Thexder 18. July 2014

Community content is available under CC-BY-SA unless otherwise noted.