User talk:Xeeron16725

Archive1

Congratulations!
I am hereby granting you the "finally provided me with a convincing reason to use an account" award. While you are not the first to mention marking minor edits, you were the first to do it while I was actually making many edits. --68.142.14.80 08:12, 25 August 2006 (CDT)
 * Hehe, welcome to the account-using-wiki then, I guess ;-) --Xeeron 08:23, 25 August 2006 (CDT)

unfavored in categories
i just went through there not two weeks ago removing categories from unfavored builds. how did those get back in? --Honorable Sarah 09:27, 25 August 2006 (CDT)


 * No idea, maybe you missed them or someone moved them after you checked. I looked at the whole category, but only about 5 builds had categories. The rest of all my edits is from untested. --Xeeron 09:30, 25 August 2006 (CDT)
 * ya, i'm seeing that now... i love your enthusiasm, but i think that was a bit premature. if untested is made into an isolated category, those builds may never get tried, and will sit in untested forever. --Honorable Sarah [[image:Honorable_Icon.gif]] 10:21, 25 August 2006 (CDT)
 * It is linked from the builds portal, plus those actually testing are mostly those who know the wiki structure. Lord Biro was right that the categories should not be cluttered by untested builds. --Xeeron 05:10, 26 August 2006 (CDT)
 * seriously, stop messing with the categories on untested, that discussion is still floating. --Honorable Sarah [[image:Honorable_Icon.gif]] 13:28, 26 August 2006 (CDT)
 * Seriously, I didnt continue since I stopped yesterday ;-) --Xeeron 17:16, 26 August 2006 (CDT)

Blech, it's all your fault...
Ok, so this guy made the following vote: Talk:Team - 55/Famine

The vote DOES say "unfavored" so he expressed his disfavor for the build, despite admitting it DOES work. What gives?

The way you ask the question "Is the build tested or unfavored?" is like the question "Is your brother tall or blond?" You make an either-or of two unmatching things. I think you need to either word the question as "Does the build work?" or "Do you like this build?" --Karlos 08:32, 29 August 2006 (CDT)


 * I guess his reasoning is: Yes, it does work, you dont die. But, it takes to long to be effective, you could achieve the same result with much less time using another build -> Since time is a major issue for farming builds: unfavored. Seems pretty logic to me. --Xeeron 11:50, 29 August 2006 (CDT)


 * But the finding and the conclusion do not match. If he tested it, he can't find out that "SS is way faster." Right? --Karlos 18:58, 29 August 2006 (CDT)


 * Wait so you're essentially saying that "Tested vs Unfavored" is actually: "Tested and favored" vs "Tested and Unfavored"?--Karlos 19:02, 29 August 2006 (CDT)


 * I would like to have more strict guidelines. However, on this case he can't say that 'SS necro is better' becase a ranger wanting to get to UW can't be a SS necro, so he needs another build - this one for example. A build can't be unfavored, because there is a build for another profession which is better in the same task. If there is a similiar but better build for the same profession, then you could vote with that reason. This is all my point of view ofcourse, but I would like to see it made official in some way. --[[Image:Gem-icon-sm.png]] (talk) 19:13, 29 August 2006 (CDT)


 * Yes. Yes. No. ;-)
 * He can find out, by testing this build, testing SS and comparing the time. Yes it is "Tested and favored" vs "Tested and Unfavored". A build can be unfavored because there is another profession is doing a better job, or else we would be flooded by W/mo healers. I see your point though that this might be a special case if there is no other possibility for rangers to farm there. --Xeeron 03:36, 30 August 2006 (CDT)


 * There is the UW trapping team, but if a ranger wants to go with a 55hp, it's this or barrage. SS is not an option, so it shouldn't be a reason for unfavoring. We really should make ome sort of guideline for this. --[[Image:Gem-icon-sm.png]] (talk) 07:43, 30 August 2006 (CDT)


 * Well I dont want to go on defending a build that I have neither read, nor tested, but I can understand that there needs to be something here that enables rangers to farm UW, but why is "go with a 55hp" a goal in itself? Maybe 55 and rangers just dont fit together well. Noone would want us to have an all mesmer team for Defend denravi just for the sake of it.


 * Btw, I wanted to write something like Builds on the wiki for a bit now, but the vote here and the discussion here should end first. --Xeeron 07:53, 30 August 2006 (CDT)


 * Good that you are on to it sooner or later. And the goal isn't to "go with a 55hp", but to go duo and be fast. Trapper duo is really slow compared to anything with a 55hp tank and ranger damage dealer. I tried to discuss with the voter, but he hasn't replied to me yet. If he does, Iw ill try to explain this to him. --[[Image:Gem-icon-sm.png]] (talk) 07:56, 30 August 2006 (CDT)


 * Ok, that is a valid point. If the build is faster than all other ranger farming builds and is fast enough so ranger farming is not at an huge disadvantage compared to other classes farming, it should not be unfavored. Still puzzled how all this is my fault thought ;-) --Xeeron 08:08, 30 August 2006 (CDT)


 * Ehhh, yeah. Why are we actually talking on your talk page? I thought that this is some kind of inside thing that you were awear of. --[[Image:Gem-icon-sm.png]] (talk) 08:11, 30 August 2006 (CDT)


 * I think Karlos is refering to his (failed) attempt to assassinate me and rewrite the (unwritten) build policies to make build include only skills from his user page. --Xeeron 08:14, 30 August 2006 (CDT)


 * Ach so, jetzt versteh ich. Danke. --[[Image:Gem-icon-sm.png]] (talk) 08:36, 30 August 2006 (CDT)

Looking For Input
Just asking, would you mind giving some input on Talk:W/Mo_Troll_Farmer? Since we have W/Mo Solo Farmer, being a better written build than the Troll Farmer build, with very much identical skill choices+variants and identical usage, it's rather redundant to have two builds for the same purpose (well, technically, the Solo Farmer covers more ground).

Thanks.&mdash; Rapta   (talk|contribs) 14:16, 31 August 2006 (CDT)

A little misunderstanding
I', not blaming anyone, this is just a little misunderstanding. Look: talk:Me/Mo Faster Caster you voted for unfavored and the plea was that "it doesn't make the spells recharge 50% faster" but actually, it does. The elite skill Mantra of Recovery lowers the recharge of spells by 50%. I'd suggest to remove your vote or change the plea. That's all. --I Follow The Blind 12:38, 6 September 2006 (CDT)
 * You are correct. I missread Mantra of Recovery for Mantra of Recall, sorry. --Xeeron 16:06, 6 September 2006 (CDT)

Re: your post to your user page
zaishen 12:43, 7 September 2006 (CDT)
 * 1) The discussion in Talk:Builds is not predicated on there being too many of them but that builds are not factual. My argument to move them off this wiki is based on my belief that the current status quo is impossible to change. You have very little to fear as the most likely outcome is that nothing will change.
 * 2) My proposal on GuildWiki talk:Builds will likely not be approved as no one has agreed with me.
 * 3) Your argument for the current voting practices has always been that we will never (be able to) vet builds (in time) without this process. This begs the question.

Holy cows
Just so you know, Xeeron, I do remember when you and I pretty much revamped the builds section by ourselves (you more than me, I don't mean to rain on your parade). I remember what it looked like before. And I feel your pain. I, too, know what the voting process changed. But on the other hand, I think it is cool that a lot of people now want to get involved -- that is really not a bad thing, but a good one. Not only does it mean there's more hands and eyes on the builds project, but that what we turned it into worked. The section grew and prospered. It also ultimately means that maybe something new is needed, once again, to replace what used to be good enough.

When the builds section was last redone, we needed to make the process more interesting, more streamlined, more attractive to all those people who thought builds on GuildWiki were a joke. Remember how they used to say that was the one thing that was crap? Not any more. But maybe now it is time for yet another revamp. Just because what we did back then was better than what came before, it doesn't have to end there. Why not give some of the other ideas and people a whirl? Let the young bloods at it for a while. If they break it, fine. We can come back and fix it. But they probably won't. They'll just make it different. And it might even be really cool.

Personally, I read most of the discussions. And I stick my head up from time to time. But mostly, I let those with the new ideas and the drive do the driving (pun intended). Part of that is, obviously, because I am now spending most of my wikitime on HammerWiki -- but it is also because some of the changes that I helped implement some times get axed, and once in a while I need to take a step back and realise that they're not mine, they belong to the wiki. If I don't step back, I end up feeling that I'm getting cut, which is obviously not the case. It's really just like the first time one of your builds is voted "crap of the month" and you just want to hit people for not trying hard enough to see how brilliant it is. But in the end, you have to let it go. Something better takes its place.

And some times, you just have to slaughter one of those holy cows.

--Bishop 13:35, 7 September 2006 (CDT)