Tailor Archive
Thread: Our question answered 5/26/04
Page 3 of 3
NJ62
Wed Jun 02, 2004 11:25 am
#27
I don't think that trying to nail down a timeframe is a useless exercise. Plus that is what the community wanted, and voted for.
Sometimes a question is just a question. Other times, it's a bargaining tool, and a way for me to pressure and negotiate behind the scenes. Both are valid.
ArthurDentOnBria
Wed Jun 02, 2004 11:32 am
#28
NJ62 wrote:
I don't think that trying to nail down a timeframe is a useless exercise.
Well, that's the whole thing right there. Our attempt was to nail down a timeframe, and we failed to do that. We got the usual "we're working on it" with no timeframe at all, which is the same as getting no response at all. If we would have asked this same question last summer, we would have gotten the exact same answer.. oh wait! we DID ask this question last summer, and we DID get the exact same answer, lol.
http://forums.station.sony.com/swg/board/message?board.id=tailor&message.id=6655&highlight=
Message Edited by ArthurDentOnBria on 06-02-2004 11:39 AM
ArthurDentOnBria
Wed Jun 02, 2004 5:11 pm
#29
you're really splitting hairs there. To me "we'll fix it" and "we're working on it and should have it completed sometime in the next couple of publishes" are one and the same. But to me it's unimportant anyway. Even if they were to tell me that "on June 15, 11:46am the fix will be pushed out live with God as my witness", I would be happy about it, VERY happy about it, but it would still represent a wasted opportunity to ask a meaningful question and get a meaninful answer back, as (presumably) this fix would have happened irregardless of our question, and me having prior knowledge of its release really does very little for me as a tailor.
Syzygy-Gorath
Wed Jun 02, 2004 5:37 pm
#30
ArthurDentOnBria wrote:
you're really splitting hairs there. To me "we'll fix it" and "we're working on it and should have it completed sometime in the next couple of publishes" are one and the same. But to me it's unimportant anyway. Even if they were to tell me that "on June 15, 11:46am the fix will be pushed out live with God as my witness", I would be happy about it, VERY happy about it, but it would still represent a wasted opportunity to ask a meaningful question and get a meaninful answer back, as (presumably) this fix would have happened irregardless of our question, and me having prior knowledge of its release really does very little for me as a tailor.
I have to disagree with that; and judging by the voting, most other tailors do as well. See, "we're working on it," and "next couple of publishes," and not even asking really do mean the same thing—they may hack at it for a bit here and there, but it's not scheduled for releease, so delays of any sort are acceptable. On the other hand, if it's firmly slated for a release delays are much less likely (although still possible.) To me, getting that public answer of a firm date is worth not asking about something else that we'll get the brush off on anyway.
Let me give you a for-instance. Let's say we ask about socketing in general—we've already had an answer about that. It's now working as intended. Let's say we ask n'Jessi's proposed query—we won't get an answer. Thunderheart stated flat-out in response to another question that he won't give numbers because "some players enjoy figuring that out for themselves." (Personally I think that's a load of **self-edit** and the truth is he doesn't know the numbers and nobody will tell him what they are…)
ArthurDentOnBria
Wed Jun 02, 2004 6:28 pm
#31
Syzygy, guess what, when the only things on a ballot are wish list items and bugs, the winning item is probably gonna be either a wish list item or a bug, lol.
That's fine though that we disagree. Personally I think that we can get some very useful things answered without having to get into the underlying algorithms. Just knowingwhether or not there is a relationship between clothing assembly and number of sockets or any other such question pertaining to knowledge about our profession could be useful in enriching our play experience. Chosing a different bug each month and asking "so how's it coming on that bug?" and hearing back the obligatory "we're working on it" does nothing for me.
NJ62
Wed Jun 02, 2004 6:43 pm
#32
Hindsight is 20/20.
First we thought we were limited to our original list submitted in January.
Then we learned it could be expanded to other community issues, issues that the majority cares about, hence their position in the top 20.
Let's not forget that our last submitted question was due over a month ago, and the voting on that started 6 weeks ago.
In response to question 1, we got a firm date. Whether we were actually in the schedule for that publish before we pushed for a public answer... maybe.
DanceRulez
Thu Jun 03, 2004 12:32 am
#33
ArthurDentOnBria wrote:
NJ62 wrote:I don't think that trying to nail down a timeframe is a useless exercise.
Well, that's the whole thing right there. Our attempt was to nail down a timeframe, and we failed to do that. We got the usual "we're working on it" with no timeframe at all, which is the same as getting no response at all. If we would have asked this same question last summer, we would have gotten the exact same answer.. oh wait! we DID ask this question last summer, and we DID get the exact same answer, lol.http://forums.station.sony.com/swg/board/message?board.id=tailor&message.id=6655&highlight=Message Edited by ArthurDentOnBria on 06-02-2004 11:39 AM
See, now here's where I disagree. Here is the relevant quote from your post
6) Necklaces – Currently invisible in the inventory and examine windows. The only way to view them is to wear them.
This is a bug and will be fixed.
Kevin "Q-3PO" O'Hara
SWG Community Relations Manager
And here is the the quote from the answer we got this time from TH
It is a strange bug in a complex 3-D rendering system and while it has been around a long time, it should be fixed in the next couple of publishes.
So I would argue that this does represent a timeframe for a fix. That's why I'm not upset about this answer. I definitely agree that this bug should never have been allowed to persist for this long, but I don't agree that this answer is some kind of brush-off to hopefully keep us quiet for a while. It sounds to me like a reasonable answer to what might be a complex bug.
Shi'ann
Hot Pink Twi'lek of Mystery
Page 3 of 3