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




The div style="clear:right;" is unnecessary I believe. If there are colisions with progression bar, we can plug it into progression. I don't see any other reason the clear:right is placed there. -PanSola 06:43, 4 May 2006 (CDT)

Blah, forgot the sectioning would be above the clear right if I put it inside progression template... -PanSola 06:47, 4 May 2006 (CDT)
Can you argue for the fake section please? Your reasons for it are entirely opaque to me. — Stabber  06:51, 4 May 2006 (CDT)
So ppl avoid hitting that edit link altogether. I'm constantly underestimating how many ppl don't read directions so... -PanSola 07:09, 4 May 2006 (CDT)
But that is a matter of policy and we have enough eyes watching over the recent changes list to catch that quickly. After all, if someone breaks the skill box template, it will be noticed in a matter of seconds. — Stabber  07:13, 4 May 2006 (CDT)
What is a matter of policy? I can't think of a reason WHY we would want that edit link there. o_O" -PanSola 07:14, 4 May 2006 (CDT)
That people shouldn't use the edit link there is a matter of policy. It is easily enforced, and your tinkertoy sections break the uniformity of the site. In particular, not all stylesheets follow a section heading with a horizontal rule. — Stabber  07:24, 4 May 2006 (CDT)
I don't see it as a policy thing, but rather as an intention thing. We don't intend an edit link to be there. People who see an edit link there and click on it intend to edit the article, not the template. Thus the edit link serves nobody. Though you have a very good point about the stylesheet. Is there any other way to create a pseudo section that would work? or anyway to only disable edit subsection of the included document but doesn't affect the including document? I'm still undecided which is the greater evil, but if there is a third way out I definitely welcome it. -PanSola 07:33, 4 May 2006 (CDT)
How about now? — Stabber  07:50, 4 May 2006 (CDT) Hmm... Didn't work

Should there be a colon after "campaign?" -- 20:39, 10 May 2006 (CDT)

Shouldn't there be a way to list that the skill is available in two compaigns? Such as "campaign: Nightfall, Eye of the North" -- Anon2 1:55, 25 Dec 2007

"Campaign" = the campaign this skill belongs to, and not the campaigns this skill is acquirable from (see skill sorting and the fact, that the skill will be disabled until you buy that campaign.) — Poki#3 My Talk Page :o, 14:02, 25 December 2007 (UTC)


Is this a mistake? Skuld Monk 07:04, 12 May 2006 (CDT)

It's not a mistake. -PanSola 07:14, 12 May 2006 (CDT)

Elite skill icon[]

Elite.png Thought we could use one for the new skill box. I'm sure this would fit nicely next to name or skill type. Chuiu Me Icon.png(T/C) 00:41, 24 May 2006 (CDT)

OMG I miss that icon from so long ago. I'd love to use it, but new players will not recognize it, so not sure if it is wise to introduce it... -User:PanSola (talk to the Follower of Lyssa.png) 01:03, 24 May 2006 (CDT)
Well it doesnt mean we have to take away from the wording or icon labling it as an elite skill. Chuiu Me Icon.png(T/C) 17:10, 24 May 2006 (CDT)
I'm in favor of it. It's pretty easy to see at a glance, unlike the yellow skill icon border. -- Gordon Ecker 04:29, 31 July 2006 (CDT)


Internet Explorer doesn't display empty cells properly. Specifically, it doesn't display the borders of empty cells. Could someone alter this template so that if stat1, stat2 or stat3 is blank then the collesponding cell has & nbsp; (without the space) in it instead of being empty? -- Gordon Ecker 18:51, 29 July 2006 (CDT)

I'm not entirely sure what you're asking since there are no/aren't supposed to be borders between the various stats. For example, the mockup in the section above looks the same in IE and Firefox (besides IE's broken PNG transparency). If I've misunderstood, could you name a skill which looks wrong in IE? -- 19:11, 29 July 2006 (CDT)
The skill box template has 2 forms, the box form produced by {{SKILLNAME}}, designed to be used in skill pages, which works fine, and the horizonal one called as {{SKILLNAME|row}}, designed to be used as part of a table in skill quick reference pages, which has the border error. You can see the border error on the Monk, Mesmer, Paragon and Dervish skill quick reference pages. -- Gordon Ecker 04:23, 31 July 2006 (CDT)
I guess the template usage is confusing, but you were asking about [Template:skill box row]. Pan fixed it. -- 06:04, 31 July 2006 (CDT)
Maybe I am, I'm not really familiar with all the intricacies of template usage. Regardless, the problem hasn't been fixed, {| {{STDT}} {{Resurrection Signet|row}} |} produces this:
Which looks fine in Firefox, but has huge gaps in the table borders in Internet Explorer. -- Gordon Ecker 08:45, 31 July 2006 (CDT)
Hmm, Pan put the spaces into skill box row, but the issue now is that some skills have an odd formatting in their templates. Look at the source of Template:Resurrection Signet as opposed to Template:Frenzy. The skill box row is only putting the nbsp in for undefined stat values, but telling the template "stat0 =" is actually defining it to nothing. This looks right:
Pan, is there a reason for the format used in the signet (and apparently a bunch of other skills? I'm not sure why they're like that. I'd guess it maybe looks like that so you can override things at various template levels, but it ends up only allowing overriding at the top level, I think. -- 09:13, 31 July 2006 (CDT)
Various fields were designed to be overridable at the template usage level (not sure if that's considered top or bottom), though individual stats were not supposed to be that way. Anyways that design has been scrapped a while ago. I would recommend taking them out individually if it bothers you. I'll fix Rez Signet right now. -User:PanSola (talk to the Follower of Lyssa.png) 12:42, 31 July 2006 (CDT)
I meant top as in whichever template the person writing code for an article uses and bottom as the last that gets included in the chain, but I guess it doesn't matter if it's scrapped. I use Firefox, so the problem doesn't bother me, heh. Someone made all the paragon skills look like that because of the use in (some of the?) mesmer skills (User talk:Matrix). I guess someone told him to look at the mesmer skill QR for guidance in making the paragon QR. -- 12:51, 31 July 2006 (CDT)
Now that I know exactly what the problem is, I've fixed the rest (at least the ones used on the skill quick reference pages). I can't believe Internet Explorer's had that well known table display bug for something like a decade without anyone fixing it. I only use IE for editing pages because that keeps each page I'm editing in a separate window, several unspecified browsers are better for pretty much everything else. -- Gordon Ecker 05:06, 1 August 2006 (CDT)
I found another problem, which appears to be in the skill box template itself.
Blackout.jpg Blackout Skill. For 2...5...6 seconds, all of touched target foe's skills are disabled, and all of your skills are disabled for 5 seconds.
    10 Energy.png 1 Activation.png 12 Recharge.png
Prophecies   Can be obtained through a quest
Drain Enchantment.jpg Drain Enchantment Spell. Remove an enchantment from target foe. If an enchantment is removed, you gain 8...15...17 Energy and 40...104...120 Health.
    5 Energy.png 2 Activation.png 20 Recharge.png
Core   Can be obtained through a quest
For non-questable skills, the questable cell should have & nspb; (without the space) like all the other empty cells produced by the template, but instead it's completely empty, messing with the borders in certain lower-end browsers. Unlike the previous problem, where it was actually being defined as blank in the individual skill templates, here it's undefined in the individual skill templates, so altering the default value of that cell to & nspb; (without the space) should only require editing the main skill box template. -- Gordon Ecker 20:42, 3 September 2006 (CDT)
Should be fixed now. (Also, like mentioned above, when something uses {{skill|foo}} it's actually using the template named "skill box foo." --Fyren 21:09, 3 September 2006 (CDT)

Dagger Skills stat0[]

We've had a lot of people mistakingly changing the stat0 parameter of dagger skills to the type of the attack instead of the prerequisite (twice on Twisting Fangs). I propose adding a comment to those templates to prevent further mistake. I had done so for Twisting Fangs but someone reverted it (no concrete reasons given). Not wanting to break 2RV, I'm asking here. --Theeth Assassin (talk) 17:18, 14 August 2006 (CDT)

It was my screw up. Put it back. -- 17:29, 14 August 2006 (CDT)
Alright. But still, that doesn't solve the problem that people wrongly believe that to be the actually attack icon and not the prerequisite. --Theeth Assassin (talk) 17:47, 14 August 2006 (CDT)

Category change[]

To get the template change to "take effect," we have to do a null edit on every article that needs changing. I guess I'll have my bot do it later. --Fyren 04:06, 21 September 2006 (CDT)

I will modify the edit a bit for now. For the final version we have to decide about the name of the category first. What is the offcial nomenclature in the "K" menu? "No attribute" or "Unlinked" or "General"? Could you look it up for me? I don't have access to the game right now. --Tetris L 04:11, 21 September 2006 (CDT)
"No Attribute," but I wouldn't really take it as binding. They don't say "Attrib: No Attribute" in the descriptions where other say "Attrib: Fire Magic." --Fyren 04:19, 21 September 2006 (CDT)
Null edit shouldn't be needed anymore since mediawiki 1.6 or something... The job queue thing will update it. -User:PanSola (talk to the Follower of Lyssa.png) 04:13, 21 September 2006 (CDT)
Gravewit's got it turned down (although I think off and running the shell script once every day or something would be better), so it might take a while. The change Tetris made the queue "length" about 3.6k (Special:Statistics), which has only gone down by a few in the time between my first comment and now. It does lower semi-randomly, so maybe it's just slower than average right now, though. --Fyren 04:19, 21 September 2006 (CDT)
Down to 1.6k! --Fyren 06:36, 21 September 2006 (CDT)

UGLY - stop the pain[]

Just looking at Well of Blood page and this template has destroyed our article pages, at first it was the useful but extremely misplaced "[edit skill details]" link, this should be positioned underneath the skill box. but the final straw is the progression table squashed into that type page. I call for a revert. On lower resolutions this must look even worse (1024x768 is bad enough). Stop this ruining of our pages NOW! --Jamie (Talk Page) 03:02, 20 October 2006 (CDT)

It looks bad on 1280*1024 as well... --Kitty1.jpg (Talk) (Cont) (Cool) Soft2.jpg 03:05, 20 October 2006 (CDT)
I usually run on 1680x1050, when on my laptop, but I can only imagine at that high resolution it would look any good. this change is a bad idea, move the progression tables back to bellow the skill box template, out of the template totally. Also look into moving the edit link (I tried myself yesterday, but I don't have access to the css file and style attribute sometimes noflicts with the css file css. --Jamie (Talk Page) 03:45, 20 October 2006 (CDT)
The edit link was moved because people were complaining no one could figure out how to edit the skill data. It used to be above the header's line, but a usability study on WP has shown that people who aren't regular contributors never use the section edit links. So I moved them down. And then showed people the new template. For weeks. And discussed it on the S&F
Anyway. In the meantime, you can change the CSS in your own copy of monobook.css or gamewikis.css in your userspace which will override the wiki-wide stuff. You can set the edit link to display:none and the table to clear:right if you want. I'll change it so you can fiddle with the CSS to float the link top or bottom later. --Fyren 04:47, 20 October 2006 (CDT)
I moved the TOC to above the progression and added a div to allow the edit link to be moved. For table.progression, add a clear:right. For div.editskill, add a position:absolute, bottom:0, right:0.1em or something like that. --Fyren 07:40, 22 October 2006 (CDT)

Skill codes?[]

What about implementing the skill codes from here?

Uhm, hello? Anyone here on this page?

Usage section[]

How about having a Usage section on the template noinclude that links to GuildWiki:Skill templates. This would definitely have saved me some time, as those GuildWiki: pages are never obvious to find. Biscuits (talk Biscuit.png contribs) 09:16, 9 December 2006 (CST)

It should have a usage section. But until it does, when in doubt, I always go to GW:S&F. From there, the guide for skills (GuildWiki:Style and formatting/Skills) has a link at the bottom to GuildWiki:Skill templates. --- Barek (talkcontribs) - 10:29, 9 December 2006 (CST)
And at the top. --Fyren 10:48, 9 December 2006 (CST)

Category Problem[]

We're running into a problem with the way this template categorizes monster skills now. Namely here: Category:Monster skills by attribute. I assume this is caused by the code in the template that says [[Category:{{{profession}}} skills by attribute]]}}. — Jyro X Darkgrin.jpg 17:11, 29 December 2006 (CST)

It's not a huge issue - but you're right, these should be getting tagged as part of Category:Monster skills by the template - I'm not good enough at the script myself to address this though. --- Barek (talkcontribs) - 17:17, 29 December 2006 (CST)
I could do it if it were written in Java or C++. =P — Jyro X Darkgrin.jpg 17:20, 29 December 2006 (CST)
It would be a simple check: if(profession!=Monster)[[Category:{{{profession}}} skills by attribute]] 17:23, 29 December 2006 (CST)
Add nocats = yes. --Fyren 18:43, 29 December 2006 (CST)

noprint edit link[]

Just something minor but the div containing the edit link should also have the noprint class so it won't show up in the printable version (if anyone actually does print these articles). -Smurf User Smurf.gif 21:33, 6 January 2007 (CST)

Adrenal skills category[]

In the skill box, I think it would be useful to modify the section that reads {{#if: {{{adrenaline|}}} | [[Image:Adrenaline.png|Adrenaline]] ... to also auto-use a category like Category:Adrenal skills. We could then link that category under "Related articles" within skills that give adrenaline boosts, such as Rage of the Ntouka. --- Barek (talkcontribs) - 10:41, 15 January 2007 (CST)

In general we seem to be making QR pages for skill lists. I don't like linking to categories in articles, especially when the contents will seldom change. --Fyren 17:47, 15 January 2007 (CST)

Allegiance and Sunspear skills[]

We'll need to adjust this template to account for the progression of Alleigance rank and Sunspear rank skills. I suspect that the green numbers for Sunspear skills represent either 0 and 10 or 1 and 10, and that the green numbers for Alleigance skills represent either 0 and 12 or 2 and 12, however it's also possible that they use the same 0...12 progression as other skills. -- Gordon Ecker 22:11, 15 June 2007 (CDT)

Sunspear skill progressions are possibly 0..8. My Elementalist is Castellan (rank 8) and has a 23% increase from Intensity, which is the maximum shown on the range. Either that, or the max on the range is a cap and skills no longer gain effectiveness past Sunspear Rank X... Oscidaes 22:16, 15 June 2007 (CDT)

Also on the subject, there's the issue of the Kurzick/Luxon skills having two icons... is it possible to make a second template just for those ten skills, with the ability to show both icons in the one box, instead of just one? Otherwise, we end up having to decide between which icon gets the coveted top spot. (more or less.) --GEO-logo.png Jioruji Derako.> 04:28, 18 June 2007 (CDT)

I have made a new template which will use both icons (and label which is which) for allegiance skills. The template is here User:JediRogue/Template:Test. And in the bottom of my testing area you can see the template is the same for normal skills and different for the allegiance skills User:JediRogue/Slide#Template_Demo_Zone I would like to change the existing template and then the template used in quick references. I think this is a good solution to the current Kurzick bias presented by the templates as they are now. —JediRogue 13:29, 19 June 2007 (CDT)

Maybe to pay back for the Kurzick bias we had, the Luxon icon should go first! :P --Gimmethegepgun 13:35, 19 June 2007 (CDT)
Yes, but that would imply that luxons are worthy of recognition lol. I'm certain this is trolling...Lord of all tyria 13:38, 19 June 2007 (CDT)
I thought about that. But everywhere its listed as Kurzick/Luxon and its alphabetical this way. It would be cool though it the order changed based on the position of the border though lol. That's way to complicated a template for me though. —JediRogue 13:39, 19 June 2007 (CDT)
Does the wiki software even allow that? Lord of all tyria 13:41, 19 June 2007 (CDT)
Can be done, not worth it though. Also please refer to Talk:Kurzick/Luxon_skills_quick_reference# and think of ways to solve these points before this is implemented, if it is. -- Xeon 13:54, 19 June 2007 (CDT)
I'm working on it now. Also working on making skill bars and mini skill bars have an option for which skill icon to display. atm, it displays Kurzick. If I wanted to show my skill bar, I definitely don't want that. So lookout for my cluttering of recent changes. —JediRogue 14:02, 19 June 2007 (CDT)

Here's what I was thinking for the QR template: User:JediRogue/Template:Test qr and again for a view of what it looks like User:JediRogue/Slide#Template_Demo_Zone. Other changes would probably need to change the css used in the qr. Not really sure what I want to do for the skill bars.—JediRogue 14:48, 19 June 2007 (CDT)

That second template (with the little subtitles under the icons) looks perfect; What you could do from there is simply make a new template for it, which we would only use for those ten skills (instead of the current skill box). Only thing we would need from there is to make sure all the category tags and whatnot still work. --GEO-logo.png Jioruji Derako.> 16:17, 19 June 2007 (CDT)

BUMP. Sexy admin review plz. —JediRogue 23:39, 19 June 2007 (CDT)


It might be a good idea to wikify the "PvE only" note on pve skills to point to PvE skills quick reference or somewhere relevant. --Roland icon.pngRoland of Gilead (talk) 04:59, 30 July 2007 (CDT)

I was thinking about that an hour ago too, :D The article needs to be created. PvE skill? -- Xeon 05:07, 30 July 2007 (CDT)
There's got to be a category already up... I saw a discussion on the subject back on the portal, check that... --GEO-logo.png Jioruji Derako.> 05:15, 30 July 2007 (CDT)
That would be Category:PvE skills, so should an article be listed (would we need it?) or should it be linked to the cat? -- Xeon 05:36, 30 July 2007 (CDT)
First off, you need to code the category tag as [[:Category:Blah]] (the ":" at the beginning is important), otherwise it just adds this page to the category.
But let's see now... the category itself's a little convoluted as it is, most of the PvE skills are all divided among sub-categories and whatnot when they should probably all be in the main category as well. For simplicity's sake, linking to the category seems the best option; I'm not sure how well an article would work on that anyway. Such an article would most likely be a quick explaination of what a PvE skill is, and a link to the category... either way, you're ending up in the category. --GEO-logo.png Jioruji Derako.> 05:55, 30 July 2007 (CDT)
Bah, i always forget the cat thing, ive done it so many times now that i forget to not to forget to not put it on. Alternatively you can link to the separate qr's at Category:Skill type quick references for each and a Mission skills quick reference can be created to accommodate for the lack of this one, which will then allow people to commentate on each list. -- Xeon 06:05, 30 July 2007 (CDT)

Update for GWEN?[]

| class="campaign" | [[Campaign]]: || class="campaigndata" | {{#switch: {{lc:{{{campaign}}}}}
| prophecies = [[Guild Wars Prophecies|Prophecies]] | factions = [[Guild Wars Factions|Factions]]
| nightfall = [[Guild Wars Nightfall|Nightfall]]
| eye of the north = [[Guild Wars Eye of the North|Eye of the North]]
|  [[{{{campaign}}}]]}}

Something like that.~ GoldDeanIcon.pngDean - 16:17, 8 August 2007 (CDT)

Good idea. Would be worth putting a shortcut in so people could type 'GWEN' instead of 'eye of the north'. Biscuits Biscuit.png 00:38, 9 August 2007 (CDT)

Unlinked skills[]

Is it possible to change categorization of the skills in a way that unlinked skills get their own subcategory like Category:Unlinked_skills_(Warrior) instead of all those skills being dropped as separate articles in the main category like Category:Warrior_skills_by_attribute? This could be done by combining the values of "profession" and "attribute". --- :Jill Bioskop X(T|C) 05:28, 12 August 2007 (CDT)

Category Bugs[]

There seems to be two problems with the auto-categories, one shouts which all starts "<name>", all get filed under the " category, the other enviromental 'skills' are listed, to quote from the cleanup tag that was placed on the category "Too much stuff that doesn't belong here, like environmental and title effects" --Nela 04:48, 9 September 2007 (CDT)


Could an Admin add a section to the template for Consise descriptions (if we plan on adding them)?Entrea SumataeEntrea Sumatae [Talk] 02:35, 16 March 2008 (UTC)

Unless there's a significant difference (eg an ambiguitiy present in one but not the other) I'd say why bother with the consise, says the same thing. --Shadowcrest 02:42, 16 March 2008 (UTC)
Thats what I think too, but Thoughtful wants to add them all. Letss put it to a vote! somewhere...Entrea SumataeEntrea Sumatae [Talk] 02:43, 16 March 2008 (UTC)

OK, vote time!

For Concise descriptions[]

  1. I think that's it's useful to have both skill descriptions. If no one else wants to find all the concise descriptions I'll gladly do it myself. Thoughtful Thoughtful Sig.png 02:48, 16 March 2008 (UTC)
  2. Conditional: I don't think the Concise are important enough for the actual skill description (redundant), but I do think they would be perfectly suited for the QR (such as this QR). They'll be documented just fine in that manner as well. --GEO-logo.png Jïörüjï Ðērākō.>.cнаt^ 23:23, 16 March 2008 (UTC)
  3. I support using the concise descriptions but ONLY on QRs. They are quick references and it makes sense to minimize them as much as possible. I know it is a lot of work, but if someone (Thoughtful) is willing then that's not an issue. Now, I am aware that some of the descriptions have errors in them, and some are hardly concise. But I'll give ANet the benefit of a doubt and let them work on that for awhile. Entropy Sig.jpg (T/C) 23:25, 16 March 2008 (UTC)
  4. It's in the game, so it should be documented somewhere. If any of them are inaccurate, a "GuildWiki note" or something can be added to it. Heck, we keep misspellings from the game already. -User:PanSola (talk to the Follower of Lyssa.png) 09:40, 17 March 2008 (UTC)

Against Concise descriptions[]

  1. They're just redundant and useless.Entrea SumataeEntrea Sumatae [Talk] 02:46, 16 March 2008 (UTC)
  2. Unless there's a significant difference, such as an ambiguity in one but not the other, don't bother with them. Why should we? It's just saying "Deals +10...26" damage twice.. I got it the first time. --Shadowcrest 02:47, 16 March 2008 (UTC)
  3. We don't need it. Unless the official wiki does it and has it looking really good, I can't even think of a way to make it not look silly on the pages. It might even be confusing because we'll be saying the same thing twice. On the other hand, if there is a notable difference between the concise and traditional, we should note it. —JediRogue 03:41, 16 March 2008 (UTC)
    We are implementing them at the moment (it's a big task as you can imagine), but still working out how it'll be formatted. The discussion is ongoing. -- Brains12 \ Talk 03:47, 16 March 2008 (UTC)
    It seems rediculous for most, especially blinding flash, which is actually LONGER than the traditional description.Entrea SumataeEntrea Sumatae [Talk] 20:11, 16 March 2008 (UTC)
  4. Redundant cluttering. As for the Showhide boxes: They span across the whole page, which imo looks a bit weird. Besides, as far as I know, they only auto-hide when there are 2 or more Showhide boxes on the page... --- VipermagiSig.JPG-- (s)talkpage 09:53, 16 March 2008 (UTC)
  5. Concise descriptions are pointless, and a lot of them inaccurate as well. We shouldn't add them to the wiki in any form, at least not until blatantly obvious errors like replacing "party members" with "allies" are fixed. Felix Omni Signature.png 22:41, 16 March 2008 (UTC)
  6. They still need a lot of work, and we should wait until they are completely fixed. Cress Arvein(Talk) 22:44, 16 March 2008 (UTC)

In between[]

  1. Well, as a matter of documentation I think it deserves it. However, I also think it would clutter stuff up too much. So, if we do add it, I think it should be in a show-hide box (default hide) --Gimmethegepgun 02:48, 16 March 2008 (UTC)
    Pan brought up a good point on the Game Updates page, concise is good for QR boxes.Entrea SumataeEntrea Sumatae [Talk] 02:50, 16 March 2008 (UTC)
    Yeah, but that would require easily the most massive overhaul of all :/ If we did that, we'd have to: add the concise to all the skills, modify the way QRs are referenced, AND change EVERY SINGLE QR REFERENCE on all of GuildWiki so that it does it that way instead --Gimmethegepgun 02:52, 16 March 2008 (UTC)
    OR change the QR templates to use the concise instead of normal descriptions. Not nearly so hard.Entrea SumataeEntrea Sumatae [Talk] 02:54, 16 March 2008 (UTC)
    Well, not so hard since Thoughtful's planning on doing all the work.Entrea SumataeEntrea Sumatae [Talk] 02:55, 16 March 2008 (UTC)
    I don't know how to make a show-hide box o.o Thoughtful Thoughtful Sig.png 02:59, 16 March 2008 (UTC)
    When you said QRs I figured you meant EVERY QR, as in condition causing, blocking, etc ones --Gimmethegepgun 03:00, 16 March 2008 (UTC)
    Maybe I just don't know how QR templates work... That would explain a lot!Entrea SumataeEntrea Sumatae [Talk] 03:02, 16 March 2008 (UTC)

This article has been protected from edits by everyone because of caching/performance issues. Please use the discussion page to propose changes or request unprotection.[]

It's protected for a reason. People with admin rights, if you are testing stuff, please make a clone of the template and do your tests on that. -User:PanSola (talk to the Follower of Lyssa.png) 05:31, 28 March 2008 (UTC)

The job queue length is 46,750. -User:PanSola (talk to the Follower of Lyssa.png) 05:32, 28 March 2008 (UTC)

Sorry Pan, we were on a roll and caught up in coding frenzy. It should be okay now though. Entropy Sig.jpg (T/C) 05:39, 28 March 2008 (UTC)

re concise[]

i would rather we added it to pages and then change the template to show the info so we don't have empty boxes around. we can add the boxes when we have more concise? also, i think that box is still quite obtrusive. takes up the same space as just writing out the consise on the page. can we put it at the bottom of the skillbox real small perhaps?—JediRogue 05:55, 28 March 2008 (UTC)

What empty boxes? It shouldn't show up unless someone adds a concise description to the skill's template. The box is rather large for such a small thing, I agree with that. Entropy Sig.jpg (T/C) 05:58, 28 March 2008 (UTC)
It shows up as a box with {{concise-description}} or something like that last I looked. Doesn't look good at all.—JediRogue 06:01, 28 March 2008 (UTC)
Could you point me to a specific occurance. I'm not seeing anything. Entropy Sig.jpg (T/C) 06:09, 28 March 2008 (UTC)
Yeah, there's an error in your template. If you arrive at the page via redirect: Mindbender.jpg for example, then you will the see the erroneous box. —JediRogue 06:17, 28 March 2008 (UTC)
I'm not seeing anything on my end. Could it be a browser error? --GEO-logo.png Jïörüjï Ðērākō.>.cнаt^ 06:23, 28 March 2008 (UTC)
It might be something that you corrected. Because I just looked at it again and didn't see it. When I looked before though there was a problem. I was probably looking at a cached page from earlier. In any case, I still think that the concise box needs some TLC cause its bulky as is. —JediRogue 06:41, 28 March 2008 (UTC)

What's the point of the hide box anyways? That thing is about as big as the concise description it is hiding o_O""" -User:PanSola (talk to the Follower of Lyssa.png) 08:01, 28 March 2008 (UTC)

Working on that now. I think it would be neat if users could set in their wiki prefernces if they want to show concise or not. That wouldn't be too hard to set up css for and a conditional in the template. Not sure how to hook to preferences tho. —JediRogue 08:11, 28 March 2008 (UTC)
My problem is the entire show/hide box takes up more space than the concise desc alone. Even if we figure out something to allow users get what they prefer, we still shouldn't have a box that takes up more space than what it is hiding. I would advocate a format that simply displays the concise description where the show/hide box header currently resides. We end up saving space.-User:PanSola (talk to the Follower of Lyssa.png) 08:15, 28 March 2008 (UTC)

March 2008 (UTC)

What I was going to work on was redesigning the navframe stuff so the show/hide box was smaller but then I thought... Okay, what about instead of a show hide for the concise descriptions, we add a small link that will toggle the descrption that appears on the page between concise and full. That way we only add a small link to the page. We can work up the switch into teh css of the template. I think this would be a tidy way to do it. —JediRogue 08:16, 28 March 2008 (UTC)
Sure, but in the mean time, I don't see any reason to keep the large show/hide nav frame box thingy in the skill box template. -User:PanSola (talk to the Follower of Lyssa.png) 08:19, 28 March 2008 (UTC)
I agree whole-heartedly. Also, Pan, you could probably do this quite quickly while I would spend hours on it. The first way to create such a toggle that comes to mind is to use a bit of javascript. I imagine that there is someway to do it with wikimarkup and css however. Would you care to offer some of your expertise? I'm working...User:JediRogue/Template:Test2 and the talk page has the sample of the template in use. —JediRogue 08:23, 28 March 2008 (UTC)
It will require Javascript, no way around it. I am of the personal opinion that on main skill articles we should list both, whereas for QRs we might consider doing the toggle, with concise as being the default. -User:PanSola (talk to the Follower of Lyssa.png) 08:37, 28 March 2008 (UTC)
My issues with it are twofold: 1. the consise descriptions don't convey any new information. We're repeating the information. The other issue is that its difficult to present the information. The show/hide boxes are too big and take up the same space as just having the information there. Having the two descriptions side by side looks silly (that's how they do it on GWW last I checked). My prefernce would have some toggle of showing one or the other because this way we aren't presenting the information twice on the page. But perhaps we can replace the show/hide navframes with a smaller more subtle navframe? Instead of that big bar we can have a small link that reveals the concise? As for the QR's I think taht having just the concise is perfect. The whole thing about a QR is expressing the information as concisely as possible so its a QUICK reference. No matter what we do, we should still include the concise description somewhere in the template. ATM its concise_description but for consistency it should have been concise-descrition I think. Anyway, we can still start adding that while we plan what to do with it. —JediRogue 08:52, 28 March 2008 (UTC)
It is only repeated information from the perspective of "what does this skill do?". It is not repeated information from the perspective of "what is the concise description of this skill?". -User:PanSola (talk to the Follower of Lyssa.png) 21:39, 28 March 2008 (UTC)
Obviously this is just my opinion, but at the moment the skill pages look... cluttered, with the addition of the concise description. In addition, smaller computer screens (like my laptop) arrange the page so that the concise box overlaps the template for the skills itself. I can take a screenshot if you would like. :| Maui sig.png 22:30, 28 March 2008 (UTC)

I think for the time being, we should just do the following (using color to highlight the area of my proposal, the color itself isn't part of the proposal):

Full: {{{description}}}

Concise: {{{concise_description}}}

Letting it show the {{{concise_description}}} which can cue people to help fill it in as well. No messy show hide boxes, and we'll discuss about the link to toggle it when the link is done. Comments? -User:PanSola (talk to the Follower of Lyssa.png) 22:42, 28 March 2008 (UTC)

I like that idea. It'll help keep the page more stream-lined, and easier to code, too. :] Maui sig.png 23:39, 28 March 2008 (UTC)
OK. Entropy Sig.jpg (T/C) 06:23, 29 March 2008 (UTC)

Unprotect please[]

Theres some coding for the Skill Box that I need to add to make the people adding concise description's jobs easier. —MaySig.pngWarw/Wick 11:12, 6 April 2008 (UTC)

...then post it here, or on your userspace so an Admin can add it? — Poki#3 My Talk Page :o, 11:33, 6 April 2008 (UTC)
May is sandboxing, and then we can all check it before it goes live RT | Talk 11:36, 6 April 2008 (UTC)

Put it on Template:Skill box draft. That way you can eaisly test how things look on each skill page by previewing "|draft". -User:PanSola (talk to the Follower of Lyssa.png) 12:56, 6 April 2008 (UTC)

Good plan Pan RT | Talk 12:56, 6 April 2008 (UTC)
Also, in the future, please don't change the protection level for the sole purpose of letting one individual who is not sysop change things. You should only change it if you believe for good reason that it should be unprotected for general editing. -User:PanSola (talk to the Follower of Lyssa.png) 13:01, 6 April 2008 (UTC)
Ok... Sorry (/bowhead) RT | Talk 13:03, 6 April 2008 (UTC)


Spam RT | Talk 13:22, 6 April 2008 (UTC)

noU. That reminds me, we need to check this over. —MaySig.pngWarw/Wick 13:28, 6 April 2008 (UTC)
Would somone unprotect this so the edits can be made accordingly? Brains managed to get it to work :). Or maybe my coding worked, and somthing weird happened.. —MaySig.pngWarw/Wick 17:54, 6 April 2008 (UTC)
'''Full''': {{{description}}} 

{{ #if: {{{concise_description|}}} | '''Concise''': {{{concise_description}}} | [[Category:Missing concise description]] }} 
-- Brains12 \ Talk 17:58, 6 April 2008 (UTC)
Or, to just put it simpler,

{{#ifeq:{{lc:{{{nocats}}}}}|yes||{{#ifeq: {{{name}}} | {{FULLPAGENAME}} | {{#ifeq: {{{elite}}} | yes | [[Category:Elite skills]]}}{{#if: {{{profession|}}} | [[Category:{{{profession}}} skills ({{{campaign}}})]] {{#if: {{{attribute|}}} | {{#ifeq: {{lc:{{{attribute}}}}} | no attribute | [[Category:{{{profession}}} skills by attribute]] | [[Category:{{{attribute}}} skills]]}} | [[Category:{{{profession}}} skills by attribute]]}} | [[Category:Common skills]]}}{{#ifeq: {{{type}}} | Skill | [[Category:Skills (skill type)]] | {{#ifeq: {{{type}}} | Echo | [[Category:Echoes]] | [[Category:{{{type}}}s]]}}}}{{#ifeq: {{NAMESPACE}} | Template | [[Category:Skill templates|{{PAGENAME}}]] |}}}}}} <div class="fakeh2"><div class="editsection plainlinks" style="font-size:60%" >[[{{fullurle:Template:{{{name}}}|action=edit}} edit skill details]]</div> Skill details </div> {| class="skillbox" ! class="name" | [[{{{name}}}]] |- ! class="icon" | {{#ifeq:{{lc:{{{attribute}}}}}|allegiance title|<div style="float: left; margin-left: 20px; background: #FFFFFF;">[[Image:{{{name}}} (Kurzick).jpg{{pipe}}Kurzick]]<br>Kurzick</div><div style="float: right; margin-right: 20px; background: #FFFFFF;">[[Image:{{{name}}} (Luxon).jpg{{pipe}}Luxon]]<br>Luxon</div>|[[Image:{{{icon|{{{name}}}}}}.jpg]]}} |- | class="properties" | {| class="skillproperties" | class="campaign" | [[Campaign]]: || class="campaigndata" | {{#switch: {{lc:{{{campaign}}}}} | prophecies = [[Guild Wars Prophecies|Prophecies]] | factions = [[Guild Wars Factions|Factions]] | nightfall = [[Guild Wars Nightfall|Nightfall]] | [[{{{campaign}}}]]}} | rowspan=2 class="professionicon" | {{#if: {{{profession|}}} | [[Image:{{{profession}}}-icon.png|{{{profession}}}]]}} |- | class="profession" | [[Profession]]: | class="professiondata" | {{#if:{{{profession|}}}|[[{{{profession}}}]]|None}} |- | class="attribute" | [[Attribute]]: || colspan=2 class="attributedata" | {{#if:{{{attribute|}}}|{{#ifeq:{{lc:{{{attribute}}}}}|no attribute|Unlinked|[[{{{attribute}}}]]}}|Unlinked}} |- | class="type" | [[Skill type|Type]]: || colspan=2 class="typedata" | {{#ifeq: {{{elite}}} | yes | [[Elite]]}} {{#ifeq: {{{type}}} | Echo | [[Echo (skill type)|Echo]] | {{#ifeq: {{{type}}} | Skill | [[Skill (skill type)|Skill]] | [[{{{type}}}]]}}}} |} |- | class="stats" | {| class="skillstats" | class="stat" | {{#ifeq:{{lc:{{{exhaustion}}}}}|yes|[[Image:Exhaustion.png]]|{{#if: {{{req|}}} | {{#switch:{{lc:{{{req}}}}}|lead=[[Image:LeadAttack required.png]]|offhand=[[Image:OffHand required.png]]|dual=[[Image:DualAttack required.png]]|hex=[[Image:Hex.png]]|enchantment=[[Image:Enchantment.png]]}}|{{{upkeep|{{{sacrifice| }}}}}}}}}} | class="statdata" | {{#if: {{{upkeep|}}} | [[Image:Upkeep.png|Upkeep]] | {{#if: {{{sacrifice|}}} | [[Image:Sacrifice.png|Sacrifice]] |  }}}} | class="stat" | {{{adrenaline|{{{energy| }}}}}} | class="statdata" | {{#if: {{{adrenaline|}}} | [[Image:Adrenaline.png|Adrenaline]] | {{#if: {{{energy|}}} | [[Image:Energy.png|Energy]] |  }}}} | class="stat" | {{{activation| }}} | class="statdata" | {{#if: {{{activation|}}} | [[Image:Activation.png|Activation]] |  }} | class="stat" | {{{recharge| }}} | class="statdata" | {{#if: {{{recharge|}}} | [[Image:Recharge.png|Recharge]] |  }} |} |} '''Full''': {{{description}}} {{ #if: {{{concise_description|}}} | '''Concise''': {{{concise_description}}} | [[Category:Missing concise description]] }} __TOC__{{#if:{{{progression_0_effect|}}}|{{Progression|{{{attribute}}}|{{{progression_0_effect}}}|{{{progression_0_0}}}|{{{progression_0_15}}}|{{{progression_1_effect|}}}|{{{progression_1_0|}}}|{{{progression_1_15|}}}|{{{progression_2_effect|}}}|{{{progression_2_0|}}}|{{{progression_2_15|}}}|{{{progression_3_effect|}}}|{{{progression_3_0|}}}|{{{progression_3_15|}}}}}}} <noinclude> Return to [[{{PAGENAME}}]] </noinclude> —MaySig.pngWarw/Wick 18:01, 6 April 2008 (UTC)

Would somone add said above coding? —MaySig.pngWarw/Wick 21:12, 6 April 2008 (UTC)