User talk:Tennessee Ernie Ford/Archive 05

incomplete edit
[ It] stops abruptly and is unsigned; I suspect some glitch rather than intention? -- ◄mendel► 01:32, August 27, 2010 (UTC)


 * The unsigned part was unintentional. (I had written more, but then realized it wasn't adding anything to the discussion and deleted it from the preview. Naturally, the ~ went out with the bath water.) &mdash;Tennessee Ernie Ford ( TEF ) 01:49, August 27, 2010 (UTC)

[ appositives]
You only use commas to set off non-restrictive (parenthetical) appositives. In this case, your subsequent edit made it quite clear that the quest name was the restrictive (essential) appositive &mdash; it was the part you kept, while you were able to leave out "the primary quest" without changing the meaning &mdash; thus it was incorrect to set it off with commas. &mdash;Dr Ishmael 01:03, September 1, 2010 (UTC)


 * That sounds good. However, my take is that the original suggested that the important point was that it was a primary quest. Commas or not, it failed the newspaper editor's rule of avoiding unnecessary adjectives. (Although some would write that as, avoid adjectives.)


 * Anyhow, the point of the edit was to avoid the debate. The point of the edit summary was to poke fun at the person who called the original grammar, "incorrect," not so much b/c I thought it was a bad edit. (Although I admit to a prejudice against seeing that many adjectives/nouns strung together w/o any punctuation.) &mdash;Tennessee Ernie Ford ( TEF ) 02:50, September 1, 2010 (UTC)


 * The thing here, though, is that "primary quest" is a standard phrase used by the game, it is part of the game's jargon. Isn't jargon necessarily exempted from editorial rules like that?  Also, identifying it as a "primary quest" emphasizes the fact that you must play through the storyline past a specific point in order to vanquish the area; to someone who doesn't already know that AGTF is a primary quest, the current wording might make them think they can just get a run out there, complete some dinky side quest, and then be able to vanquish.  &mdash;Dr Ishmael Diablo_the_chicken.gif 03:45, September 1, 2010 (UTC)


 * The critical question you ask is, "what about letting peeps know that they have to play through storyline to specific point?" I thought about that before I removed the phrase and I'm rethinking it. On the whole, I imagine that ppls who get to the VQ point have either completed the quest or know that it's in the storyline (esp. w/the various bounties etc around). On the other hand, how hard would it be to find a phrasing that avoids the appositive and too-many-modifiers issues and gets the job done?


 * I think the editors that eschew adjectives would argue that jargon is out, too, b/c we can find plain-speaking words that manage to convey the same meaning. So, what about,


 * In order to VQ the area, you must have progressed the eotn storyline through completion of AGTF.


 * The phrasing could be better, but that gets the idea across in about the same # of words and w/o anyone else stumbling over grammar. &mdash;Tennessee Ernie Ford ( TEF ) 04:42, September 1, 2010 (UTC)


 * (edit conflict) You'd need to look up AGTF anyway in order to find out where to get it, and what the prerequisites are; this is the point where you'd learn it's a primary. (Or you would if the quest page mentioned it; as it stands, this point can only be deduced from the navbox.) And you'd also learn there's a single prerequisite quest, so it's not actually very deep into the storyline?
 * There's more important info the note is lacking: Why does the quest have to be completed? Does it unlock some area? Do I have to have completed it at some point in the past, or does it need to be active while vanquishing (it's a repeatable quest)? Is it enough if one party member has it? -- ◄mendel► 04:56, September 1, 2010 (UTC)

The rush
When we have a question we can decide, and one we can't, I think it folly to delay the first decision waiting on the second, especially given that many Internet/wiki projects get stuck indefinitely. (And seen in the light how long that first decision has already been delayed.) Deciding the merge now doesn't prevent you from organizing teh material better in any way; it requires another decision process, but we have one now (and need the new one then when prototypes/mockups are available), so we're not actually saving any effort; not deciding the merge now just means we had a lot of talk and no result to show for it. -- ◄mendel► 17:26, September 1, 2010 (UTC)


 * Erm, I think I mentioned that I thought the two questions were linked. You disagree, which is fine. But that doesn't mean we couldn't have waited another few days, as I requested, in order for me to present a proof-of-concept of an alternative way of accomplishing the stated goals of the merge.


 * I don't see indefinite delays being a risk here. Nor is the original decision "delayed" &mdash; there was no consensus yet to merge (pretty much 1-2 people's opinions arguing for it, another against). So, again, why the need to rush into a decision today?


 * I do see that, having made a decision to merge, that it will be much harder to undo. I generally believe that the burden should be on the vanguard to prove the need, not on the conservatives to support the status quo &mdash; even I would find it hard to support unmerging after the fact. That is (imo) extra effort.


 * Finally, why are we having the discussion on my talk? &mdash;Tennessee Ernie Ford ( TEF ) 23:10, September 1, 2010 (UTC)


 * We are having the discussion on your talk because it is meta to the discussion actually going on. I didn't want to mix the meta-discussion with the discussion.
 * I don't see the link between the questions that you claim. The pages are now in "state A", the "simple" merge would be "state B", and your proposal might be "state C". I don't see that it's any harder to go from B to C than it is to go from A to C, unless you want to argue that the advantage of C over B isn't as clear as the advantage of C over A -- which implies that you prefer B over A; also, you wrote, "I agree the current system is bad."
 * Given that, I see Rose, Darksyde, Dr Ishmael, Jon, myself and yourself in favor (more or less).
 * Vipermagi proposed adding the artisans to the material pages, which would probably entail taking the material's line from the Artisan table, and the relevant artisan's lines from the artisan list table. This can be done merge or not, and would probably lead to the materials table being removed from Artisan, while the artisan list might stay on. This means Vipermagi really hasn't spoken either way on the merge. So I do see a consensus to merge, at least if I can get you to admit that you really don't oppose it. ;-P
 * Your wrote, the burden should be on the vanguard to prove the need -- Rose expressed the need; Darksyde seconded. By subject matter, the list is more appropriate to the Artisan page than the materials table is. -- ◄mendel► 07:08, September 2, 2010 (UTC)


 * Hmmn. I don't see it. The argument is that it's hard to find where to go to craft &mdash; I'm saying that such info is entirely disconnected to merging or not. I would therefore like to postpone the question of whether a merge is sensible until we have addressed that more important issue. I believe that it is likely that no one will care about merging afterward.


 * In other words, merge is a means to an end and, if we find another (better) means to that end, the merge itself becomes its own issue. So, yes, from my point of view, it's all linked. Taking it to "state B" would, in fact, make it all but impossible to get to a state C that has unmerged pages and yet solves the hidden NPC issue.


 * Accordingly, for me, this discussion is directly related to the issue rather than a meta discussion about the discussion itself.


 * Finally, I still don't see any harm in waiting another short while. I think it folly to delay...given that many...projects get stuck... &mdash; that usually happens when ppls aren't seeing the bigger picture and no one is boldly taking steps forward. My argument is that the bigger picture might be better addressed by a non-merge solution and that, should we merge now, we might actually find it harder to see (let alone implement) that alternative.


 * Mind you, I might be entirely wrong, but can I ask your indulgence for a wee bit longer? Thanks. &mdash;Tennessee Ernie Ford ( TEF ) 15:42, September 2, 2010 (UTC)
 * Would a week be ok? -- ◄mendel► 19:44, September 2, 2010 (UTC)

dungeon chests
Please see sections 6 and 7 on Template talk:Dungeon chest contents. -- ◄mendel► 08:43, September 6, 2010 (UTC)

blank parameters
Why are you leaving all the blank parameters in the ItemInfo template? It's not necessary, and for the icon parameter, it completely screws up the icon display. &mdash;Dr Ishmael 03:55, September 22, 2010 (UTC)


 * Erm, it's not clear to me when a parm should be blank, when not. I didn't see anything odd in the display when I previewed, so it didn't seem like a problem. However, this is exactly why I stopped after doing only a few &mdash; give you a chance to repoint me. &mdash;Tennessee Ernie Ford ( TEF ) 05:20, September 22, 2010 (UTC)


 * As a general rule, it's a bad idea to supply blank parameters to templates. &mdash;Dr Ishmael Diablo_the_chicken.gif 13:34, September 22, 2010 (UTC)