GuildWiki talk:Style and formatting/Builds

Older Stuff

 * /archive 1
 * /archive 2

A new Builds article
Since I have been unhappy with the inconsistent and complicated way we are currently displaying build articles for a while, I decided to come up with a suggestion (User:Bishop/Builds) of what I think the main Builds article should look like. The obvious assumptions are that the current article is moved to Builds (Definitions) and that that article is expanded to include further information on how we vet and sort builds; information that is currently only available on talk pages in various places. The astute reader will also observe that I have included my suggestion for a new group of deprecated and/or weak builds, the Category:Unfavored builds, which I believe is a far better solution than to throw away builds that people have put time and effort into. --Bishop (rap|con) 11:33, 12 May 2006 (CDT) Oh, as an aside, we really need to decide if we want the categories to use capitalized Builds or not, as the current state is horribly inconsistent. --Bishop (rap|con) 11:37, 12 May 2006 (CDT)

optional

 * i want it to scream "LOOK AT ME!!!". in fact, i want it to screem "LOOK AT ME!!! I'M WRONG! PUT A SKILL HERE! THE HOLLOW IS PAIN!" maybe if we put an eyejaring florescent icon the center of the white it would get people to stop using it. --Honorable Sarah [[image:Honorable_Icon.gif]] 16:43, 31 July 2006 (CDT)
 * I was so moved by this plea that I came up with this as a possible alternative.
 * [[image:optional-1.jpg]]
 * "Optional" Makes CoP-Baby Cry. --Black Ark 18:40, 31 July 2006 (CDT)
 * i was hoping for something like this
 * [[image:new-optional.gif]]
 * --Honorable Sarah [[image:Honorable_Icon.gif]] 11:58, 1 August 2006 (CDT)
 * 2 words: Ohh my... That's simply horrible! I'm all for transparency, except that jpegs doesn't support transparency, and if we switch file type on optional, it's just too much work to go through everything and edit.


 * And if I saw the CoP-baby in a skillbar, I'd assume that CoP was optional. o.o So.. What's wrong with blank? :p &mdash; Galil  12:15, 1 August 2006 (CDT)
 * optional is the guildwiki equivilent of "I don't care". it would be much better if every build had a full bar, then said "Replace X with Y if you need YAdvantages." is that really hard? i'd really vote to break optional in every skill bar if i could. or at least move it to "Blank" to signify that no skill should go there, or the author doesn't know what to put. we could upload a "skill-bar grey" icon to match an empty slot on the ingame skill bar. --Honorable Sarah [[image:Honorable_Icon.gif]] 12:52, 1 August 2006 (CDT)
 * Well, I did make it whitish so as to divorce it from CoP in that respect. And also because that icon just freaks me out, looking all blue like that. Compare [[image:optional-1.jpg]] and [[image:Contemplation_of_Purity.jpg]]. Frankly, I think my version is not only distinctly different, it's the most beautiful thing I've ever seen. And not to rag on Sarah's design, but that would sooner drive me insane than urge me to add a skill or two. Would it be an option to just abolish "optional" altogether in the skillbar, and prompt the user to actually add in skills if and when they submit their build, on pain of not being able to submit at all? I don't know my wiki that well, so you tell me. And for what it's worth, I agree that a build should use at least seven slots, with a res-signet as the "filler". God, just add a res-signet to your build, it'll make everyone happy. --Black Ark 17:19, 1 August 2006 (CDT)


 * As .jpg does not support transparent background, and .png doesn't scale appropriately in the wiki, how about just modifying the current image to use an off-white color? A very pale yellow, brown, blue, or gray?  Might take the edge off, while still allowing it to clearly show that there's an open skill slot. --- Barek (talk • contribs) - 12:46, 1 August 2006 (CDT)
 * A little bit off topic; if Gravewit approves to my changes, soon enough the wiki will resize png images decently. :) &mdash; Galil  13:13, 1 August 2006 (CDT)
 * I can see an advantage in using resizable .png icons. I just hope users don't start uploading large .png images once they can re-size cleanly into thumbs on the articles.  My understanding is that part of the recent purge of old images was to free up disk space.  For larger images where image quality can stand compression and still be usable, I feel we should still enforce the .jpg preference from GW:IMAGE (note: I suppose we should move any discussion on this, if needed, to that policy's talk page if/when the changes go into effect). --- Barek (talk • contribs) - 17:52, 1 August 2006 (CDT)


 * a sample skillbar

how many people would let that sit? someone would change it. that's the point, convince people that "optional" is to be avoided as much as possible. --Honorable Sarah 17:30, 1 August 2006 (CDT)
 * If you're trying to have a discussion about build style and formatting, move it to a better place. --68.142.14.106 17:47, 1 August 2006 (CDT)


 * Difference of opinion on basic assumptions. I do not believe that "optional" should be avoided.  If a particular skill trully is optional, then let it show that fact - not try to insert an arbitrary skill that may work well with the build but isn't required for the core design purpose.  But as 68.142 mentions, this should probably be discussed in the style & formatting page for builds or skills.  --- Barek (talk • contribs) - 17:52, 1 August 2006 (CDT)

I'm serious, this works. You wouldn't leave this as is. No person is that heartless. Best of all, this solution won't make the build-article look like "My First GeoCities". --Black Ark 19:51, 1 August 2006 (CDT)


 * Why not something like this?
 * {| style="border:0; text-align: center; border-collapse:collapse;"

Illusionary Weaponry Flurry Shield Bash Optional Optional Optional Optional Resurrection Signet
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * style=" vertical-align:top; width:68px; border:1px dotted #444;"|
 * }
 * &mdash; Galil  20:02, 1 August 2006 (CDT)


 * For one thing, it doesn't change the current solution - don't get me wrong, it looks good and sensible, but it won't prompt people to actually finish their build, nor will it urge other people to add skills in lieu of the original poster. Emotional blackmail is the key. --Black Ark 20:04, 1 August 2006 (CDT)


 * Who says builds with optional slots are unfinished? I agree with Barek here, what if a skill slot truly is optional, as in any skill will work? I've had builds where I've had absolutely no skill to fill up my bar with so I have actually played with half a skill bar (today at the latest). So why shouldn't I be able to create an article reflecting that? &mdash; Galil  20:08, 1 August 2006 (CDT)


 * Just to add, I'd rather have B&W SoC-icons, but I am too lazy to edit it. :p &mdash; Galil  20:09, 1 August 2006 (CDT)


 * Many builds need to be variable depending on where you use them. Now it surely is a matter of taste whether you'd rather add multiple complete skill bars to the build article, to reflect all possible mutations, or one skill bar with one or more "optional" slots. I would go with the optional slots. :) --84-175 (talk) 20:16, 1 August 2006 (CDT)


 * I'm with Barek (and two edit conflicts later, also Galil and 84-175), optional is fine. Take this example, if you have some interrupting Ranger build which works in a variety of situations. In PvE your optional skill might normally be Favorable Winds to add damage, in RAs because Touch Rangers are so prevelent your optional skill might be Throw Dirt, in HA you might normally swap in Frozen Soil to combat IWAY and in ABs, because you often need to quickly travel from point to point, you then choose Storm Chaser. Same build, does the same interrupting role in each, but is tailored to the situation. Don't confuse having some flexibility in a build with an unfinished build. --Xasxas256 20:24, 1 August 2006 (CDT)



Variations

 * Favorable Winds is preferred for PvE, but less useful in PvP. make the following subsitutions:
 * for Heroes Ascent, use Frozen Soil to prevent resurection.
 * for Alliance battles, use Storm Chaser for extra speed and energy.
 * for Random Arenas, use Throw Dirt to combat rangers and warriors.
 * }
 * easy, plus the first timer doesn't look at that bar and wonder what is supposed to go there. don't confuse indifference for flexability. ;) --Honorable Sarah [[image:Honorable_Icon.gif]] 20:45, 1 August 2006 (CDT)


 * So how about this one then. I was gonna bomb some Charr today and found the build on a user-page. The user-page suggested a R/A with Dash and Death's Charge, but I couldn't be bothered getting them for my ranger and changing secondary just to bomb some Charr (needed Fur Squares). So, I modified it slightly and the skills I took were:
 * No 7th and 8th skills needed as I wouldn't have used either even if I did take them. What should I put there? Just some random skills to "fill up" the skill bar? Since no more skills are needed, and it wouldn't change anything if I did take any. &mdash; Galil  21:11, 1 August 2006 (CDT)
 * No 7th and 8th skills needed as I wouldn't have used either even if I did take them. What should I put there? Just some random skills to "fill up" the skill bar? Since no more skills are needed, and it wouldn't change anything if I did take any. &mdash; Galil  21:11, 1 August 2006 (CDT)


 * I don't think we're seeing eye to eye here. Gali is arguing for optional because sometimes you need less than 8 skills. Sarah is arguing against optional because you should just put the most common skill and list variations below. Black Ark (edit: and Sarah, apologies) is arguing against optional because it encourages people to submit unfinished builds. Barek, 84-175 and myself are arguing for optional because sometimes you'll have a skill that changes due to circumstanes. I don't think I forgotten anybody or put words in someones mouth (although I know I've simplified the arguemts)? But the variations/unfull skill bars is a seperate argument and usage for this skill bar, as is the unfinished builds/list variations arguments.
 * ...So I guess it might be better to rename this, optional sounds like Gali's purpose, it's used when you don't have a full skillbar. However this is normally used for variations, perhaps variable would be a better name? We very very rarely have builds without full skill bars, so I'd suggest renaming it to variable and keep the current white picture. What you guys think? I'll get ready to cast Mantra of Flame!! --Xasxas256 00:33, 2 August 2006 (CDT)
 * i also think it encourages people to submit half done builds.
 * the argument that putting a blank spot there instead of a skill with variations is founded on the premise that the blank spot improves the ability to vary a bar, which it doesn't since you have to write a variants section anyways.
 * char bombing is a corner case build, since it's a level 20 ranger with access to elites going against level 7 or 8 AI foes with maybe two skills, neither of them elite. however, for the bar above, not being an expert on charr bombing, i'd say troll and antidote signet.
 * i still think we should break it and have a red link. no one would leave a outpost with a blank spot if they have skills to fill it, why would anyone leave a blank on a bar on a build page? --Honorable Sarah [[image:Honorable_Icon.gif]] 00:56, 2 August 2006 (CDT)