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)


 * I guess that makes me no one, as I have left with blank slots, especially when going out to farm. Never saw the point in cluttering things up with skills that just take up space and would never be used.
 * As for looks; I view the flashing monstrosity as such a severe eye sore, I would view replacing the white box with it as borderline vandalism. Forcing an obnoxious block into the wiki is not a good design solution.  Develop/enforce policy rather than crippling the templates.
 * If a build is unfinished, it will remain in test status and eventually get deleted if no work is done on it. We already have a process for that, and last I looked, it seemed to be working.  If another level of tags is needed, then maybe adding 'build-wip' for a build that's a work in progress and not ready for testing yet.  Those can then be reviewed periodically, and any with a month or more of no development can be purged. --- Barek (talk • contribs) - 08:32, 2 August 2006 (CDT)
 * With no points in Wilderness Survival I can't see how Troll Unguent would help, seeing as you don't have any time to cast it, and when you do, you're spamming Barrage instead since they die faster than it would normally take to use Troll Unguent. Antidote signet would be even more of a waste seeing as they don't give you any conditions. Charr bombing might be a "corner base build", but it's still a build.


 * As Barek stated though, I too have left outposts more than once without a full bar, simply cause if I put something there, I wouldn't use it anyway. So why try to figure out a skill to put there, that you're not going to use anyway? I'm all for the Variants-box though, since it is indeed a good idea to place it where it would make sense, but I am against removal of Optional simply cause sometimes you don't need a full bar and it wouldn't help if you did fill it. &mdash; Galil  10:19, 2 August 2006 (CDT)

I don't think "optional" slots should be eliminated or even discouraged. My argument is about the same as Barek's. Look at Me/E Migraine Mesmer and Me/N Migraine Mesmer. Neither consume corpse nor windborne is a part of the build's primary purpose. In HA, people stuff CC or windborne there because they help they can help the team a lot but the core build doesn't improve much with any other particular choice. This should definitely be Me/any Migraine Mesmer with an optional slot. The same could be said for a lot of mesmer builds, where gale, windborne, draw conditions, a repeatable resurrect (for GvG), CC (for HA), or something else is often a viable choice all in the same build. The actual choice comes down to the team build and not just the mesmer. Look at W/E_Shock_Axe. It's tagged as RA/TA/HA/GvG. You'll often see healing signet in GvG (and I presume the same in RA). You won't often see it in HA (and I presume the same in TA). I'd swap healing signet out for optional (or split it into two articles, I guess). I'd swap out bull's for optional even though I'd personally take it most of the time. Healing signet isn't part of the "warrior with shock" build, it's part of the "warriors in GvG need self-healing to aid the ability to overextend or split without a monk" metagame (or the "RA is random and the other team will all attack you for no reason sometimes" metagame). Bull's strike is a good skill, but I wouldn't say it's clearly superior to the other choices. --68.142.14.106 11:27, 2 August 2006 (CDT)
 * obviously the flashing monstrosity was half joking (ok, maybe less then half, but not less then 25% joking). as i said, char bombing is a corner case. i think i left a town once without a full set of skills, but that town was presearing ascalon. i still think we should change it to "Blank" and the text to "no skill". unrelated note: i'm merging the migraine twins now. --Honorable Sarah [[image:Honorable_Icon.gif]] 10:27, 3 August 2006 (CDT)
 * I'm going to have to agree with (damn, I'll just call you "the need to make an account person") here. Optional slots are slots that are completely situational, but are still required as they serve a purpose, such as skills that are of equal value to the main build. For example, one would argue that a good Energy-Recovery skill would be Drain Enchantment, while another would argue for Inspired Hex. The fact is, both are situational, and each have their place in specific areas, one being suitable in Enchantment-Heavy areas, one being suitable in Hex-heavy areas. Optionals (like mentioned above), are also useful in builds where skills are not completely necessary, and can do without. But a support skill can be used, not needing to specify which one as it is not completely necessary, being what the main build skillset suggests. &mdash; Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 18:53, 9 August 2006 (CDT)
 * I know this can be solved by selecting one and putting the other as a variant, but Optional skills are used in cases where there are multiple skills that are of equal value. Since we want to have a NPOV here, sometimes it is better to have an Optional Slot to avoid bias. I'd suggest, of course, that optionals are reviewed, and that they are only in builds where they are necessary. However, I completely disagree with your statement about "Optional skills = I don't care". &mdash; Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 18:56, 9 August 2006 (CDT)

My opinnion: I want to see quickly what the point of a build is. I just need to know the core, the changeable skills can be read from below if I get interested. Therefor the optional slot serves a purpose. -- (talk) 14:50, 23 August 2006 (CDT)

category:PvP builds and category:PvP team builds
since the PvP cats have superior orginization, these two categories are only used to collect other categories. we should stop recomending people put new builds in them. --Honorable Sarah 15:01, 9 August 2006 (CDT)
 * For months it's said to pick the narrowest categories that apply. --68.142.14.65 15:21, 9 August 2006 (CDT)
 * Fixed the Category list, as well as updating the Syntax. &mdash; Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 18:47, 9 August 2006 (CDT)
 * Sorry, you broke what was originally there. Read 68.142's comment closely again. 70.20.114.124 19:20, 9 August 2006 (CDT)
 * My mistake. It seemed contrary to the use of . &mdash;  Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 19:57, 9 August 2006 (CDT)

Unfavored-build template
this strikes me as wholly unnessisary. we remove unfavored builds from every category except unfavored, so anyone looking at an unfavored build will be looking through unfavored builds. why would anyone need this warning? --Honorable Sarah 10:23, 10 August 2006 (CDT)
 * Perhaps if following a link from another article. I certainly don't look at the category-list every time I follow a link just to see what categories the article is in. &mdash; Galil  10:25, 10 August 2006 (CDT)
 * I think it makes sense. If someone were to link directly to this article from another website, for example, it might not be clear that we think this build is pants :)  &lt;LordBiro&gt;/&lt;Talk&gt; 11:29, 10 August 2006 (CDT)
 * ok, point. could we include some useful information in the template then?

this build is unfavored. this build was voted unfavored for the following reasons: * *
 * etc? --Honorable Sarah [[image:Honorable_Icon.gif]] 11:32, 10 August 2006 (CDT)
 * Feel free to update the template. I just created it since it was referred to at Style and formatting/Builds, but didn't exist. Didn't give too much consideration into how it should look. Figured someone else more engaged in the build pages would edit it as they see fit. &mdash; Galil  11:40, 10 August 2006 (CDT)
 * i suppose i have to learn template syntax eventually. ok, looking into it. --Honorable Sarah [[image:Honorable_Icon.gif]] 11:42, 10 August 2006 (CDT)
 * http://meta.wikimedia.org/wiki/Help:Template is a good start. :) Wish interwiki-links would be enabled... &mdash; Galil  11:48, 10 August 2006 (CDT)


 * Just to state my position on this issue, in no way do I think we need an Unfavored template, like Sarah said, all of the categories are removed, and the Unfavored builds category is added. There's really no need for explanation when a build goes unfavored; we don't like it, it's not effective, and we still don't like it. Besides, why would you go through garbage, anyways? :P &mdash; Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 12:01, 10 August 2006 (CDT)
 * I halfly agree, though we should still let people know that we think the build in question is junk. As I've already said, not all visitors reach pages from within the categories, or even from the wiki. These users shouldn't have to scroll all the way to the bottom just to check if a build is unfavored or not. If you've ever studied media communications (not sure of the name in english), the first thing you learn is to put the information where users expect to find it. Most visitors read from top left, to bottom right. As such, they won't start looking for unfavored builds at the bottom of the page. Also, not all visitors have visited the wiki before. These most likely don't know we tag favored builds if they visit an unfavored build directly. &mdash; Galil  12:11, 10 August 2006 (CDT)
 * Interwiki links do work, I just think Gravewit didn't throw the default interwiki data into the database. They're nearly all just for the different language Wikimedia projects.  --68.142.14.65 15:36, 10 August 2006 (CDT)
 * template optionally accepts unfavor reasons. people who look at the page might not be able to see why it went unfavored. if a build went unfavored because "not a good PvP build" i might be able to make a good PvE build out of it, but if it went unfavored because "core of build based around flawed usage of "Move Zig!". it doesn't work this way" i know to go look somewhere else for inspiration. i've had to ask why myself sometimes. --Honorable Sarah [[image:Honorable_Icon.gif]] 12:18, 10 August 2006 (CDT)


 * I think this template should only be used for those builds that have a fundamental flaw or would be useless in any circumstance. I don't think this should be used for builds if they've been posted as PvE builds and failed but are still useful in PvP.  &lt;LordBiro&gt;/&lt;Talk&gt; 13:27, 10 August 2006 (CDT)
 * Yes, with the manual "Category:Unfavored builds" box at the bottom. Besides, the only way most people reach the Unfavored builds section, is through the Builds portal. Therefore, they already know they're in the Unfavored section when they see those builds. &mdash; Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 13:31, 11 August 2006 (CDT)
 * hopefully the voting process would catch any that were just miscategorized, but there are several builds submitted as pure PvP builds that might be useful in PvE with a little work. obviously if a build is submitted as both PvE and PvP, and it's worthless in a PvP situation but works fine in PvE, it should be removed the from PvP cats and tested as any other PvE build. --Honorable Sarah [[image:Honorable_Icon.gif]] 13:46, 10 August 2006 (CDT)
 * well i'm appling it to everything unfavored. consistency is a yellow bannana shoe... i think my brain just stopped. --Honorable Sarah [[image:Honorable_Icon.gif]] 13:36, 11 August 2006 (CDT)


 * Oh dear, not again... don't worry, I'll fetch the vinegar!  &lt;LordBiro&gt;/&lt;Talk&gt; 15:15, 11 August 2006 (CDT)

theoretical builds
Whats the deal with "candidate for deletion" on Nightfall based builds. Theres no warranting a delete, once the game comes out those builds simply need to be updated with the current content. This would be a totally backwards way to approach thinking ahead of the curve. I'd rather see build ideas that were explored already during the FPE event listed, and then simple updated, rather then deleting all the research the community already put into the product. --Amokk 15:44, 22 August 2006 (CDT)
 * as i explained on Talk:D/N Dwayna's Curse, these builds will be useful for four days over four months, and will undoubtedly require updates at every juction. they should not have been created, but i ignored it. when skuld started placing tags on them i realized that they should have had tags on day one, durring the weekend. --Honorable Sarah [[image:Honorable_Icon.gif]] 15:50, 22 August 2006 (CDT)
 * I think your missing something in your reasoning. Techniqually you should go and delete every Nightfall skill from guild wiki from my understanding of your statement.  If Guild Wiki is ever to properly become oriented with the community, much less the PvP community, it has to keep up with what is happening in said community and the builds that community is designing.  If anything Nightfall based builds should be labeled a "Work In Progress" and allowed to stand until final release of the game unless completely vetted out by the community veterans as rubbish before hand.--Amokk 16:09, 22 August 2006 (CDT)
 * i didn't say anything was rubbish, just that it was not useful. those builds might be the best in the universe, but they cannot be used, tested, or improved until release. as you point out, the skills are certainly going to change, and while skill pages can be updated by simply coping the text out of the game, builds have subtle interactions that will, most likely, need extensive evaluation in the very likely event that the skills are changed. evaluation that could be better used on existing untested builds. "the community" has no way of testing these builds either, unless you are refering to anet's beta community, who assuredly has offical information that is far superior to ours. --Honorable Sarah [[image:Honorable_Icon.gif]] 16:20, 22 August 2006 (CDT)
 * Yes! THANK YOU, Sarah! I've been meaning to throw the delete tag on those ages ago, for the exact same reasons. The point is, those builds are not able to be tested, and cannot stay in the category they are in now. Perhaps they could be moved to Category:Archived builds? &mdash; Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 23:32, 22 August 2006 (CDT)
 * Maybe we should have a different category? Something like "Preview event builds" or "Unreleased expansion builds"?  (I don't really like either name that much, but you get the idea.)  I agree that having them clutter up the other Untested and PvE, HA, AB, RA, etc. builds is undesirable. --Spot 16:30, 22 August 2006 (CDT)
 * you mean something Akin to the unfavored category, where the builds exist only in that category and not in any functional or skill categories? --Honorable Sarah [[image:Honorable_Icon.gif]] 16:33, 22 August 2006 (CDT)
 * Pretty much, yes. But not Unfavored though, preferrably a separate category. --Spot 16:48, 22 August 2006 (CDT)
 * i'm not totally opposed to that. i still think the solution is to simply remove the pages and create new builds when nightfall is released, but at least they would be out of the main builds areas. --Honorable Sarah [[image:Honorable_Icon.gif]] 16:50, 22 August 2006 (CDT)
 * Something along these lines is exceptable. Out of the way, but still excessable to those working on them or willing to give input...Sounds like a good deal.--Amokk 16:54, 22 August 2006 (CDT)
 * I find it silly that people are posting Nightfall builds now, but for different reasons. Any posted outside the weekend are guaranteed to be untested. I like to create builds and create pages for them only after I've ran considerable testing of my own to deem it viable as a build. I wouldn't mind a separate categorty, but it still doesn't touch the issue that builds posted now are untested, untestable, and very likely to use skills that change upon release. --Thervold 19:11, 22 August 2006 (CDT)
 * True, but it doesn't hurt to leave ideas on the table. A great idea thats posted is availible to test and wok with. If its deleted though that leaves room for completely forgetting the concept that made it work in the first place. The wiki buildspace is a place to post builds for the community. I feel that having valad idea for the community to work with is just as viable. Hell, i Will PERSONALLY test every Dervish build when Nightfall is released to test for inneffectiveness due to changes. (because i unlocked all the availible dervish skills during the event) that way we could keep the concepts and remove them when they are no longer valad at all. Isnt teh unfavored section there for exactly the same reason? To allow room for inspiration? --Midnight08 19:34, 22 August 2006 (CDT)


 * GuildWiki shouldn't be a dumping ground for untested theoretical builds, many of which will be forgotten by the time Nightfall is actually released, and will never be updated. If you have theoretical builds that you want to try out once you can try them, track the build in your user space for now.  I see no justification to as actual build articles at this stage. --- Barek (talk • contribs) - 19:49, 22 August 2006 (CDT)
 * Some of these were tested pretty extensively, and until we see changes come through the builds are still valad. No reason to nuke em until we see changes that make them no longer valad builds. Just create a place for them, even if its an archive of sorts. When Nightfall comes i want a few established build ideas to look at. And so far its only the good ol boys who have any problem with this. --Midnight08 23:14, 22 August 2006 (CDT)
 * barek put it as concisely as it can be put. these will surely be forgotten when nightfall comes around. category:untested builds shouldn't be a dump space. --Honorable Sarah [[image:Honorable_Icon.gif]] 00:09, 23 August 2006 (CDT)


 * I am in favor of keeping them (in a separate category without being linked). They might be good builds, so why waste them by deleting. However, once Nightfall arrives, we should be quick to delete them, unless they are proven to still work (preferably by the original submitter). --Xeeron 00:18, 23 August 2006 (CDT)


 * So have the authors keep them in their user space for now. Gets them out of the main article space.  If after factions is released they prove to still be viable, then build articles can be built for them. --- Barek (talk • contribs) - 00:38, 23 August 2006 (CDT)


 * I disagree with keeping them in userspace. The reason i want them there is soo that i can see them and use them as an inspiration for ideas. If they were in userspace then i wouldnt be able to find them and neither would the rest of the community. Just give them their own area, its that really so difficult? (Remember we'll be having this debate every 6 months, might as well make a long term solution. If you choose the userspace route now in 6 monhs when a group of new people come through and C4 is released they'll have no clue that the builds will be rejected by the old school leaders here... The'll make a build to help the community and then they'll have to deal with possible deletion of their work. If you create an area for Theoretical or Pre Release builds and open the link to the area when the 1st preview events are announced, and then close the link and wipe the area a month after the games release (make it a tag and it the authors responsibility to re link it to the testing forums). this would stop this issue from ever coming up again and would be a simpler process than arguing over it. Deletion of a persons efforts for really no reason is a fast way to alienate the newcomers... If you want the contributors to keep coming you guys need ta learn that new ideas arent really a bad thing. --Midnight08 06:35, 23 August 2006 (CDT)
 * /2nd; seriously --Amokk 08:41, 23 August 2006 (CDT)


 * Forgive me if I'm wrong, but I think there was some talk about deleting untested builds that have become abandoned unfinished by thier authors. If that's so, why not just apply the same to this? If 1 or 2 months after Nightfall is released no changes or comments have been added on those page, they would be deleted. For now, a note about it being a theoretical build might be enough, though I suppose it would waste space a bit. I'm with the delete-one-month-after-nightfall idea though. Silk Weaker 06:24, 23 August 2006 (CDT)


 * While personally I dont care whether the articles are in Userspace or not, putting the builds in Category:Nightfall preview builds would keep them linked, even if in userspace. --Xeeron 06:43, 23 August 2006 (CDT)
 * Now that idea i like... so could we set some sort of a deadline then and then if a build is not transferred by that deadline I will add it to my userspace for testing on release. i will also keep them all linked through the category above. (wouldnt mind a link to the category listing on the builds page) --Midnight08 08:31, 23 August 2006 (CDT)

In Response to Barek and his whole "these are all speculation builds" Text that he removed:
 * note: I had removed this less that 5 minutes after posting as I wanted to wait until I had more time to think on it - but as it was replied to, here is the removed post --- Barek (talk • contribs) - 09:20, 23 August 2006 (CDT)
 * We regularly delete anything that is mere gossip/speculation and not provable as part of the game - untestable builds should fall under that same umbrella. Some of these were developped and tested during the preview event, while others have merely been thought of afterwards as "I wonder how this mix would do" type things.
 * The argument asking if we really want to go through the deletions every six months is irrellevant. We already go through a similar process in the Nightfall campaign article where we delete anything that is unproven speculation - only factual content is kept - a process repeated every six months, it's not a hassle.
 * New ideas are not bad things. Unprovable speculation and theory in the main namespace of a site that prides itself on supplying only factual provable content is the problem. Once nightfall is released, new builds will be getting added very quickly. If these builds had been appropriately tagged for deletion sooner, we wouldn't even be having this debate, the only reason it occurred is because of the volume of build dumping by the time someone noticed. Stand alone databases exist for tracking personal/concept builds - GuildWiki's main space should not be used for that purpose. --- Barek (talk • contribs) - 09:03, 23 August 2006 (CDT)


 * Most of these build WERE tested during the event. I'm sure they will be retested during the next event. They arent speculation. they worked. I will be testing EACH dervish build here during the events... Where is the speculation. The only Speculation here is the assumption that the skills will be changed. Yes, i realize its likely that some will, but they might not be and the last official notice we recieved was the currently used skills which were tested for the builds. --Midnight08 09:11, 23 August 2006 (CDT)


 * The event was July 28 – 30, many of these builds were created in GuildWiki within the last week. At least if a build were added at the time of the event or immediately after, it could be arguable that it was tested during the event.  Anything added after that cannot be proven to have been tested - they are theoretical at best. --- Barek (talk • contribs) - 09:30, 23 August 2006 (CDT)
 * Agreed, i am merely stating that any created DURING the event should not be considered for deletion. The ones that are created w/o any testing should be the only ones targeted with this deletion movement. I know i EXTENSIVELY tested my Dwaynas Curse build. I still agree with moving to userspace as long as there is category set and a moderately easy way for users to find the category--Midnight08 09:38, 23 August 2006 (CDT)


 * I have no problem with removing the delete tag and inserting a category tag to any of these builds that were created in GuildWiki during the event or within roughly a week after the event (Aug 6th seems a reasonable cutoff). My primary complaint here has been with the several that have delete tags that were created more recently and that cannot be proven.  Those are, due to their late creation date, questionable on if they were even tested during the event. --- Barek (talk • contribs) - 09:45, 23 August 2006 (CDT)
 * Note: A build posted within one week after is the longest that I would support considering a build to have been actually tried during the event. If the community wants to tighten it to be within a day or two, or even only builds posted during the event itself, I have no objection to those closer cutoffs. --- Barek (talk • contribs) - 10:09, 23 August 2006 (CDT)
 * no matter how well tested, the skills will change, meaning they'll need to be re-evaluated and re-tested. if people are going to protest deletion, then let's get these out of main namespace and into an isolated category in user space. --Honorable Sarah [[image:Honorable_Icon.gif]] 11:51, 23 August 2006 (CDT)
 * For builds that were tried and posted during the event, I have no problem keeping them in the main namespace - although with their own category and a disclaimer tag (maybe the standard C3 and/or another disclaimer) - it's really no difference to me than a skill having the c3 tag. My primary objection on theoretical builds has been specific to those created after the fact (one was even created yesterday) that may or may not have even been tried during the event.  Because their posting date draws into question if they were actually tried (regardless of claims), those should be deleted or required to remain in the user space for now.  If in the user space, I have no opinion if the theoretical ones should be linked to the same or maybe a sub-category of those that are in the main space. --- Barek (talk • contribs) - 12:00, 23 August 2006 (CDT)
 * Sarah, you are promoting deletion based on the speculation that the skills will change. Many skills may not change. Even after a change the build may be viable. Should we delete any build who's skills MIGHT change? For that matter if you know for sure a skill is going to change should you just delete it? We knew EoE was going to change, and even after the change i have seen several requests for deletion on EoE builds that still work, Maybe even work Better after the change. We need to stop being so close minded about things around here. I have read several pressing arguments about why the builds should stay. But so far the only argument for deletion is based on the assumption (speculation) that there are upcoming changes to the skills. While that is a possible and likely outcome, it is in no way the ONLY outcome to the situation. --Midnight08 12:29, 23 August 2006 (CDT)
 * arguing BETA skills are not going to be refined between now and release is a hard sell, and it's just as difficult an arguement that builds based on those beta skills are similar to builds based on EoE, which is both stable and testable. --Honorable Sarah [[image:Honorable_Icon.gif]] 12:53, 23 August 2006 (CDT)


 * I'm arguing that we have no official word yet so assuming they are goes against the purpose of the wiki to begin with. up to this point the skills listed in such builds are current and the latest information we have recieved. I dont assume anything in my statement, i state that there is speculation stating an issue will exist later. That is truth, no room for argument in truth. I agree that the skills will likely be changed i just dont think that it makes any sense to delete until after the speculated changes take place. The changes are speculation, the skills in place now are currently fact, until changes are made and shown to the community. --Midnight08 12:58, 23 August 2006 (CDT)
 * the skills are not current, that was the point of my last argument. they were current as of the event, nearly two months go, but they are not testable, and we have no idea how much they are going to change. mapping uncertain ground by documenting the skills is one thing, constructing a town with these builds, quite another. --Honorable Sarah [[image:Honorable_Icon.gif]] 14:18, 23 August 2006 (CDT)

Personally I believe that builds for Nightfall should not be published until Nightfall is released, regardless of any preview events.  &lt;LordBiro&gt;/&lt;Talk&gt; 14:29, 23 August 2006 (CDT)


 * Forget it, im not bothering to contribute to this place anymore and i hope others follow... actually i dont have to hope that the community who runs this place will ensure that over time... Do you all not realize that a vote in an area like this is biased by nature? The regulars are the ones opposed to nightfall builds. They know they have more support because they have been acquaintances for a while here already. On the other hand those of us who are just here to give a little with the free time they have are ignored. Yes theer are less of us, we would not win a vote. I asked for comprimises, instead of a comprimise the elitist community behind this looks for the easiest way to get their way... I'm done, you all are not worth my time... I'll let gw.gamependium.com store my ideas, at least they dont let their ego's get ahead there. Adios, i loggin out and wont be loggin back in. I think GWO Wiki will have any further suppot i may want to give. Sux too as i was also contributing to Neverwiki. --Midnight08 15:19, 23 August 2006 (CDT)
 * Sadly I've reflected the same sentiments as you, Midnight, as a “new contributor”, but if you leave, you'll most assuredly be damning the ‘elitist community’ that exists here to continue to degrade. I’ve used Guildwiki since Guild Wars was released and know first hand that most of the Guild Wars community I interact with daily, absolutely refuses to use Guildwiki for anything more then facts about the game.  If you want to know what a spell does or where monsters are or about a mission, that’s about all they rely on Guildwiki for.  If the Community wishes to add content, let it be added.  The fact this is even up for debate is rediculous and doesn't bode well for disproving the infamous reputation this site has among the real Guild War's Community.--Amokk 15:53, 23 August 2006 (CDT)
 * elitist is an interesting word. my first contrib was 01:43 CDT, 15 March 2006, far from an old hand. no one ever told me i was not welcome, no one ever acted like they were better then i was. some five months later, i have 2500+ edits and, judging by midnights comments, i'm considered a force in the community. not really elitist beheviour.
 * on the other hand, i have never flamed out over a vote or resorted to personal attacks, and i don't feel my contributions should be afforded special protection. i've submitted builds that are deleted or unfavored, articles that were gutted and rewritten, and i have not fought those changes.
 * on the subject of usefulness, you sugguest that your community only checks guildwiki when the need information on a skill, mission or monster, and they don't use it for anything else. i'd consider that a success, considering that once you exclude skills, missions and monsters, there isn't much left of Guild Wars. i'd ask what you think we're missing? build advice? strategic information? a language reference? a Wiki is not a forum, and structured content can only be structured with the exclusion on unstructured content. --Honorable Sarah [[image:Honorable_Icon.gif]] 16:15, 23 August 2006 (CDT)

Deleting the C3 build pages while keeping the C3 skills is, IMO, hypocrisy. The reasons cited above against any Dervish build are equally applicable against all Dervish skills, so should those be deleted as well? Plus, even though they will likely change in the final game release, editing an existing article to reflect said changes would be much easier than creating one from scratch again. Why are people so afraid of these builds anyway, they don't take much storage space, they don't use bandwidth unless someone actually want to read them, and it's not as if people will make chars according to the builds and then find out they don't work--so what's the problem of stashing them somewhere until they can be properly tested? - 72.195.132.41 16:37, 23 August 2006 (CDT)

Still cant see what the problem with leaving builds that were tested is? Because it cant be tested at the moment? When the next event comes wouldnt it be nice for people to have some ideas to work with... not everyoe has teh patiance to sit and construct a build over a period of 6 hours like i do. I love making builds and even if you delete them i will be fine. But damnit the community (not the Elites, im talking about the noobs) could use a place to get ideas. Elitest - http://en.wikipedia.org/wiki/Elitist think about it some. The Mod and high end user here seems to band together on issues here. At the least they will draw people who see eye to eye into a discussion. I cannot say the same for a low end user who rarely contributes. They u0sually dont who who to contact or how to fight for an issue they believe in. All they can hope to do is explain their side and hope others see the same. Personally i will never agree with people who look at something that might be useful and say i cant guarantee its userful get rid of it. The more that is availible that is of good quality for the community the better. I have seen alot of people her look at a good build and say... hmm it doesnt have xyz i dont like it. then they vote unfavored often after explaining they never tested the build. The worst part is watching the same people follow this and do the same. They often dont offer criticism, they just shoot down the idea. Peopl need to learn to treat a community as a whole with respect, and to work together more. I'm the gass is 1/2 full type, i like content, i like all the info i can get. I so far have not had any issue with the way devs run any game ive played with the exception of the extensive CoH nerfs... The high end user here seems (with some exception) to lean towards th glass is 1/2 empty pov. They want perfection. The Optional Slot discussion is one example of this. It makes no sense. Optional is a real word, its there for a reason. The same goes for alot of things here. The Extreme perfectionists here help build the wiki to the high standars it has, yes. But at the same time perfection can be suffocating. I have been scolded for missing a signature on 1 of my comments.... out of the maybe 30 i had done that day. I have watched people flame a build because of 1 optional slot. And now i am watching sadly as the work of about a dozen people is being trashed because a few of the high end users are saying "whats the point". The point i Inspiration for the next event, the point is to have things to mull over so we can brainstorm the next gamebreaking build. The point, is to have a place thats not a generic forum, where people can go to get all of the info they need without having to randomly dig. The Documentation for MMo's is horrid and the strat guides are pathetic. The wiki's are the best source of info for a community, ad you perfectionists are doing a great job of making it difficult for us newer users to provide that information to the community. -- Midnight [/rant]


 * I think the biggest problem here is that we're dealing with subjective pages on a wiki that tries to remain objective. The idea of being an online encyclopedia for all that is Guild Wars comes into direct conflict with almost the entire Builds category. However, the builds include great references for popular builds and terms seen in game. When I started seeing calls for "BP Rangers" and didn't know what that was, I could search here for that and find examples. However, the subjectivity increases as people post builds that have never been tested. While this isn't always a bad thing, it generates a lot of work for others to sift through to actually test to post their experiences with the build. For me, I like to play at least two or three hours with a build before making a decision, and I appreciate when the poster has taken some time to verify if the ideas the build is based off really work. It is quite possible that a particular build that was never play tested has some good ideas, and as a result, I've shifted my opinion to at least keep the builds. But it would be helpful to remind those looking at them that the ideas are theoretical, marking them as very subjective ideas in an predominatly objective wiki. Thinking about it, I don't mind keeping them where they are with the ch3 tag as that reminder, but moving them to another category would work too. I would appreciate authors who never tested the build ideas (ch3 or otherwise) to say so in the build's talk pages, but that's probably asking too much and unenforcable. --Thervold 17:53, 23 August 2006 (CDT)

The Vote
Democracy ftw! &mdash; Rapta   (talk|contribs) 14:32, 23 August 2006 (CDT)
 * Vote to End 11:59 PM August 26th 2006 PST (01:59 AM 27th CDT) . --Honorable Sarah [[image:Honorable_Icon.gif]] 15:06, 23 August 2006 (CDT)

Delete all Nightfall builds:
 * 1) &mdash; Rapta  [[image:Rapta_Icon1.gif|19px]] (talk|contribs) 14:32, 23 August 2006 (CDT)
 * 2) --Honorable Sarah [[image:Honorable_Icon.gif]] 14:35, 23 August 2006 (CDT)
 * 3) --Theeth (talk)   16:38, 23 August 2006 (CDT) or move to user pages. Builds that can't be tested are pure fabrications. At least wait until the next public beta, when the dervish will be nerfed skills will be more balanced.

Move to Category:Archived builds:
 * 1) (your vote)

Move to their own category:
 * 1) Keep them, but out of the way --[[Image:Gem-icon-sm.png]] (talk) 15:34, 23 August 2006 (CDT)
 * 2) Ditto. Also, best compromise. --Spot 15:41, 23 August 2006 (CDT)
 * 3) I don't see the point of keeping them, but several people seem to want to - best compromise is to move them out of the way. --NieA7 15:32, 23 August 2006 (CDT)
 * 4) This seems like a good compromise. Builds shouldn't be moved out until retested on release. --Thervold 16:45, 23 August 2006 (CDT)

Leave as is:
 * 1) It'll all be in its place when the game comes out. The less people use their "Administrative" privileges the better. --Amokk 14:53, 23 August 2006 (CDT)''
 * 2) --Midnight08 15:21, 23 August 2006 (CDT) (tho i doubt this will win over the voices of Rapta, Sara, and Skuld)

Issues with Vote
I have three issues with the vote --- Barek (talk • contribs) - 14:56, 23 August 2006 (CDT)
 * My stance on this isn't reflected as a vote option.
 * No close date for the vote is listed.
 * As stated on Category:Votes, "Please note that votes are non-binding, and the existence of votes is being contested at Category talk:Votes."
 * erm... add a new heading, this whole discussion sprung up in 24 hours so 3 days seems good and round, it's a summary of opinion not a legal process. --Honorable Sarah [[image:Honorable_Icon.gif]] 15:05, 23 August 2006 (CDT)


 * Yes, but everyone's opinions are already seen above in the discussions. As votes are non-binding, the outcome shouldn't be a basis for any determination, and is not a means of reaching or determining a concensus.  I really don't see the point in having the vote. --- Barek (talk • contribs) - 15:46, 23 August 2006 (CDT)