GuildWiki has been locked down: anonymous editing and account creation are disabled. Current registered users are unaffected. Leave any comments on the Community Portal.

Template talk:WeaponInfo

From GuildWiki
Jump to: navigation, search

damage range[edit source]

Why doesn't this template include the damage range? There's a fair number of weapons including the Tyrian version of the sickle and rusty axe which have not been observed with the normal maximum damage for their weapon class. -- Gordon Ecker 01:04, 30 July 2006 (CDT)

The old item_begin template (and company) had fields for ranges, but no one was really filling in the minimums for anything and a lot were even missing the maximums. Newer templates just dropped the fields. It's not really that sickles have a lower maximum range because of their skin/name, it's just that the stuff dropping them is yields low level loot. Trying to place maximum observed ranges back into templates for things like sickle would be a pain since it'd have to differentiate the sickle types from within the template. Just note it in the article text. --68.142.14.19 01:40, 30 July 2006 (CDT)
I tried arguing to add it back in; but there weren't many in the community involved, so I figured most didn't care and just dropped the issue. --- Barek (talkcontribs) - 09:36, 10 August 2006 (CDT)

Bows[edit source]

This template now has bow capabilities. Example: If you add the attribute:

shortbow = yes

the shortbow's stats will appear. The other bow you can define are: shortbow, recurve, hornbow, flatbow, longbow

A full example is:

{{WeaponInfo

| image = someimage.jpg

| attributes = [[Marksmanship]]

| type = [[Piercing damage]]

| recurve = yes

| commonsalvage = [[Wood]]

| raresalvage = [[Steel]]

}}

--Xasxas256 01:11, 15 August 2006 (CDT)

It could be cajoled into taking bowtype = short, long, etc. instead. Also, there's Template:BowInfo that's used on a few bows. --68.142.14.42 01:29, 15 August 2006 (CDT)
I must admit my solution seems a bit kludgy, I was in a hurry, I pressed "save page" then grabbed my bag and left work. [Template:BowInfo]] looks ok but I like the old system of having the bows stats right there. --Xasxas256 00:15, 16 August 2006 (CDT)
I would prefer : {{If-Then|if={{{bowclass}}}|then=|- valign=top | ||'''[[Bow#Bow Classes|Bow Class]]:'''||{{{bowclass}}}}}—├ Aratak 12:26, 17 August 2006 (CDT)
I myself like seeing the stats there but also what to compare it to. Is it possible to have the stat numbers displayed and the 'type' of bow displayed as well? Example outcome:
  • Bramble Shortbow
  • picture goes here
  • Weapon Details
  • Linked Attribute(s): Marksmanship
  • Damage Type: Piercing
  • Bow Class: Shortbow
  • Class Refire Rate: 2.0 seconds
  • Class Flight Time: .59 seconds
  • Class Arrow Range: 1.0 times aggro bubble
  • Class Bow Arc: Normal
  • Class Inherent Properties: None
  • Salvage
  • Common: Plant Fibers
  • Rare: unknown

Of course this could make the page a bit fatter and unweildy but I find skiping between pages slows me down quite a bit as the wiki pages take forever to load sometimes and this may help lessen the page changing if all the info is there. Of course I have no idea how to link the stats other than posting the stats on every bow but it seems you two may have some means to accomplish this.--Vallen Frostweaver 11:06, 22 August 2006 (CDT)

If we choose to show all the stat, Xaxas256 version will do the job.—├ Aratak 11:12, 22 August 2006 (CDT)
the problem with a optional data on this box is that it cannot be included by If-then, the table formating pipes are confused with template argument seperating pipes. --Honorable Sarah Honorable Icon.gif 11:18, 22 August 2006 (CDT)
We could simplify it then to drop the bow 'class' stats to keep it clean looking then. Upon looking at other ages (swords, wands, etc.) they don't list the detail info and only have a link to the damage type, etc. So the questions then are:
  1. Do we go detailed stats with problems in the creation of a template.
  2. Or, detail stats without a template (entered in individually).
  3. Or, go with a smaller display of a reference to the 'type' or 'class' of bow it is and skip the stats as they are listed on the Bow page that they are all linked to.
What's you're preferences? I can accomplish 2 or 3 if you like but I can't do 1 without someone else building the template (and making sure it doesn't mess up the image links).--Vallen Frostweaver 11:29, 22 August 2006 (CDT)
The image is not a problem, it is really easy to add to the template. And I aggre that the pipe screw it up, I try to make in in a subtemplate but then the bow class showed up on all the page. Im at work and my diner break is finish so I shoudnt even read this ;) —├ Aratak 11:40, 22 August 2006 (CDT)
idealy we'd want to duplicate the functionality of Template:BowInfo and Template:WeaponInfo in one template, but i don't think that's possible, given the template+tables pipes problem. the only option would be to include a subtemplate, which is no cleaner then the current implementation. --Honorable Sarah Honorable Icon.gif 11:43, 22 August 2006 (CDT)
I see no reason to not have WeaponInfo include another template. If Aratak's only problem is auto-categorization of a second template, put the category tag outside of that template and in an "if" inside WeaponInfo or inside of includeonly tags in the second template. --68.142.14.35 20:23, 22 August 2006 (CDT)
Well i still beleive we should have them in seperate infobox, would be a lot less trouble and would be a lot cleaner to change afterward. I also think that it should only have the bow class not all the info.—├ Aratak 11:54, 22 August 2006 (CDT)
So then you would prefer it to look like it does now for the Celestial Longbow?--Vallen Frostweaver 12:05, 22 August 2006 (CDT)
We could use this I think I got it to work now but its still messy:
{| style="margin:0 auto; text-align:left; background:none;" cellpadding="2"
|- valign=top
| ||'''[[Weapon#Linked_Attribute|Linked Attribute(s)]]:'''||{{{attributes}}}
|- valign=top
| ||'''[[Weapon#Damage_Types|Damage Type(s)]]:'''||{{{type}}}
{{If-Then|if={{{bowclass|}}}|then={{WeaponInfoBow}}|}}
|}

├ Aratak 14:15, 22 August 2006 (CDT)

Sounds good but I'm not that handy with understanding this code yet. You tell me if it'll work, get one up and running using it, and I can take over from there if you want someone to do the footwork. Sorry I can't be more help on this but I'm just not that learned on wiki yet.--Vallen Frostweaver 14:44, 22 August 2006 (CDT)
unfortunatily that leaves us with three templats, instead of the two we have. the idea is to get to one. --Honorable Sarah Honorable Icon.gif 20:24, 22 August 2006 (CDT)
I think Aratak is trying to replace the two we have with just the one made above.--Vallen Frostweaver 06:57, 23 August 2006 (CDT)
Well it does use another template, a small one to bypass the pipe probleme. I did that while I was working but I know I have seen a way to make a pipe not acte has a pipe for the template, need to search mediawiki. Pansola have something too, I think is {{pipe}}. So yes it would be 2 template but most user will never saw it. So its simpler for them because to them they always use WeaponInfo they dont see the other one.—├ Aratak 07:31, 23 August 2006 (CDT)
As I commented above, there's no reason to not use another template. As Aratak says, the users will never see anything but WeaponInfo. --68.142.14.35 07:36, 23 August 2006 (CDT)
[Bad news]. It's easy to switch to html code for that part but it will look weird with all the template in wiki-pipe and not that part. So I think that the easiest way is to hide it in a new template and that what I have done with WeaponInfoBow. I have try to use the code for the pipe, | so it doesn't acte has a pipe in the template at all, so it doenst stop then= but it doesnt work for the table either. I dont understand the &nbsp way. Unless someone come up with something better I think that we are stuck with to seperate template or one that inclued another one.—├ Aratak 08:49, 23 August 2006 (CDT)

Overriding width[edit source]

Is there any way to override the 160 pixel width? It's causing problems on the Soulbreaker page. -- Gordon Ecker 19:31, 15 September 2006 (CDT)

I guess I could change it so you can specify a width for each image. Is there a reason there are subtables used instead of just rows in one table? --Fyren 19:45, 15 September 2006 (CDT)
We can get an in-game image in a week, at which point the image will be horizontal instead of vertical - that will solve the problem. I don't think the template needs to be updated for an issue that won't exist in a week. --- Barek (talkcontribs) - 20:08, 15 September 2006 (CDT)
Someone can flip the existing image if they care. --Fyren 20:18, 15 September 2006 (CDT)
I went ahead and rotated the image 90degrees. Needed to clear cache, but solves the display issue. --- Barek (talkcontribs) - 20:32, 15 September 2006 (CDT)

Image parameters[edit source]

If you give this a parameter named image, it doesn't append .jpg to it. I have no idea if this is the intended behavior, since if you give it image1, image2, image3, or image4, they all get .jpg appended. I switched it from If-Then-Else to PF but left it working exactly as it did just in case it's used somewhere that expects it to work in that way. --Fyren 10:34, 25 October 2006 (CDT)

Because image is not a parameter, when I made the template I put parameter image1 for concistencies with the rest (image2, image3 and so on). So it was just a choice when I made it. I know some one told me he would change it so it can use other extension, like .JPG but dont know if he done it. If we change that, we would have manualy input .jpg at the end of each name on every page that use this.—├ Aratak 10:57, 25 October 2006 (CDT)

PvP reward categorization[edit source]

I can't get this to work. I think I might not be using #if correctly, although it's also possible that the cache may not be updating. -- Gordon Ecker 21:02, 26 May 2007 (CDT)

I managed to get it working on the other wiki, but I'm still not sure what I'm doing wrong here. -- Gordon Ecker 21:12, 26 May 2007 (CDT)
I finally managed to get it working here. -- Gordon Ecker 21:24, 26 May 2007 (CDT)
What you had before was basically "|- | blah blah." You can't start a new row and supply cell contents on the same line. Also, why are there empty cells in the table? --Fyren 21:26, 26 May 2007 (CDT)
I don't know why the first column is full of empty cells, but they were there when I started working on it, so I added one for th PvP reward row to match the formatting of the previous columns. I can't figure out how to get the pvprewardnote parameter to work properly, it completely breaks the table. -- Gordon Ecker 21:37, 26 May 2007 (CDT)
Removed the empties, then. If they ended up being there for spacing, then padding should be set instead. How/where do you want the note to be displayed? --Fyren 21:40, 26 May 2007 (CDT)
To the right of the PvP reward class, something like this.
pvpreward = basic
pvprewardnote = (Canthan skin)
Weapon details
Linked attribute(s): <attribute>
Damage type(s): <damage type>
PvP reward class: Basic (Canthan skin)
Salvage
-- Gordon Ecker 21:45, 26 May 2007 (CDT)
So, like it is now? You don't need to use PF unless you want to automatically put in the parentheses. I also changed "class" to "type" in my previous edit just since the other things in that part of the table were types, heh. --Fyren 21:57, 26 May 2007 (CDT)
It's good, thanks. I've copied it into template:BowInfo, template:OffhandInfo and template:ShieldInfo. -- Gordon Ecker 00:22, 27 May 2007 (CDT)