Tailor Archive
Thread: Our question answered 5/26/04
The answer is both encouraging and discouraging at the same time.
One one hand they say they are aware of the issue and want to squash it with the migthy foot that is all SOE development.
On the other hand they note how difficult the issue is and that its on the bottom of the high priority stuff.
My real question for the next bi-weekly is this.... If the necklace bug is on the bottom of the high priortiy list does that put it lower than the issue which is highest on the low priority list? (lol can anyone follow that?
)
Love the idea of a forum party when/if this finally gets fixed, I will bring cake
My poor boyfriend is so sick of hearing me complain about tailor problems now (Wookiee TKM with no love of crafting since his holo told him to master architect) that he will probably celebrate too.
hahahaha..thanks! I needed that!
Rizzaka wrote:
My real question for the next bi-weekly is this.... If the necklace bug is on the bottom of the high priortiy list does that put it lower than the issue which is highest on the low priority list? (lol can anyone follow that?
)
Rizzaka wrote:My real question for the next bi-weekly is this.... If the necklace bug is on the bottom of the high priortiy list does that put it lower than the issue which is highest on the low priority list? (lol can anyone follow that?
)
You makin my head hurt (hehe)
Syzygy-Gorath wrote:"Working on it" could mean anything. Without a firm timeframe the answer is meaningless and unacceptable.
Pappi wrote:I know that ood_bnar's been busy (i've barely seen him around, let along chat), and while I agree that this bug's been around way too long, most of the "we're working on it" responses dates after JTL. I know it's frustrating, but at least they're working on it
silly, noone gets a firm timeframe... although feel free to come over to my forum and /bonk some people for complaining even after i bugged TH to get a timeframe for our stuff =/
Should we start comming up with the next question?
My question would be:
Can we expect to get schematics forthe non craftable items such as the Metal bikini bottom, Newb Scout Vest, Robe (found on most EntertainerNPCs) , etc?
Pappi wrote:
Syzygy-Gorath wrote:
"Working on it" could mean anything. Without a firm timeframe the answer is meaningless and unacceptable.
Pappi wrote:
I know that ood_bnar's been busy (i've barely seen him around, let along chat), and while I agree that this bug's been around way too long, most of the "we're working on it" responses dates after JTL. I know it's frustrating, but at least they're working on it![]()
silly, noone gets a firm timeframe... although feel free to come over to my forum and /bonk some people for complaining even after i bugged TH to get a timeframe for our stuff =/
Thunderheart wrote:
Tailor: In response to our December top 5, the devs wrote: We are aware that items that have reached 0/0 condition are still equippable, it is not suppose to work this way. We consider this issue a priority for your profession and we are working to resolve it.
This issue is particularly problematic because completely decayed items not only are equippable but also still grant full bonuses from bioengineered panels or from skill tapes when equipped. In addition, there is a concern that if items become unequippable at 0/0, people will purposely try to "fail repairs" to get the item to 1/1 so it will never reach 0/0.
The Tailoring Community wants to know what steps have been taken to correct this problem, what additional progress still needs to be made, and when the bug fix will be patched in.
I’ve been pushing on this issue and it’s currently scheduled to be fixed in Publish 10.
It's exactly the kind of answer we knew we would get.
"It's difficult. We know you want it fixed. We're working on it. Go away."
We'll get the same answer for every question that has to do with bugs.
Shi'ann
Hot Pink Twi'lek of Mystery
NJ62 wrote:
The invisible necklaces are something that the art and programming folks are looking at.
my comment is... no they're not. Cause if they were this would have been fixed.
This is why I'd rather see us ask actualy questions about how things work etc. rather than these "are you going to do..." type questions. Because in the former case you might actually get some useful information out of the devs, but in the latter case they just answer "yes" and you know nothing more than what you knew originally, which is that it's not fixed yet.
Message Edited by ArthurDentOnBria on 06-02-2004 11:05 AM