Tailor Archive
Thread: WARNING: Do not try to make BE clothing or cloth at this time!
ShennySG1
Thu Jul 28, 2005 10:24 am
#131
I keep posting, or rather I did keep posting (only like 4 times) saying fix it cos i don't think enough emphasis is on the fact this problem really sucks. If we all kept quiet about it, maybe the devs would think "hmmm its all quiet on the tailoring front, lets leave that issue aside while we mess something else up".
Anyway, i've quit the profession and am now TKM and Pikeman, back to my combat roots ftw 
Have fun on waiting for the fix guys and enjoy the profession, like i used to.
Grreeta
Thu Jul 28, 2005 3:54 pm
#132
Gyopi wrote:
BrendanK wrote:
You were entirely too nice in that converstaion Greeta..I would've told that idiot to F off....either that or dueled, and db him..
Some of us tailors can't duel and db a chuba! "Aaah! Frog! Run!"
lol I have visions of me slapping the culprit around the face with my Long Uniform Gloves (black of course) and challenging them to "Knitting Needles at Dawn". Or sneaking up on them andembroidering something scathing yet witty on theirLuke Skywalker outfit using my finest needlepoint.
I have visions of me slapping the culprit around the face with my Long Uniform Gloves (black of course) and challenging them to "Knitting Needles at Dawn". Or sneaking up on them andembroidering something scathing yet witty on theirLuke Skywalker outfit using my finest needlepoint.With a CL of 7 I run from durnis ... and before they made the change that stopped aggro beasts following me into my tent I suffered the humiliation of being incapped by a vrelt in front of my own vendors (who looked on in that superior way that NPC vendors have). Fortunately I was rescued by a petite level 15 entertainer (suitably attired in a gold extremely revealing skirt and light bustier) .... Soon after this I abandoned my "bad boy" biker look in favour of a more flamboyant, devil-may-care outfit. I'm hoping this will persuade any self-respecting Rogue Bageraset to give me a wide berth.
Cheers,
Gawgax
S0ldad0
Fri Jul 29, 2005 12:22 pm
#134
OK, I got BE clothes (Melle/Ranged Defence):
1. I see the stats on the clothes
2. I see the stats transfer to my Avatar skills screen (CTRL+S)
Is it all saying I have the defences, but not actually giving the defences?
1. I see the stats on the clothes
2. I see the stats transfer to my Avatar skills screen (CTRL+S)
Is it all saying I have the defences, but not actually giving the defences?
Jutewr
Fri Jul 29, 2005 12:43 pm
#135
Melee/Ranged defense clothes don't appear to have any affect on actual defense. That issue is separate from the issue being discussed in this thread.
Currently, no new BE clothing can be crafted. Old BE clothing works, depending on the modifier. Ranged/melee defense are two modifers that don't work.
S0ldad0
Fri Jul 29, 2005 12:51 pm
#136
SO I beat 3 BH with these clothes on and they actually did nothing for me? In effect I was fighting in my unides? lol Great to know.
*cant wait until they work, lol*
*cant wait until they work, lol*
Ganryu
Fri Jul 29, 2005 2:05 pm
#137
It's been six weeks since this bug was introduced.
Is there anyone out there who could explain why this bug exists in live? I only ask because in my experience, bugs like this are typically caught in QC.
I am a programmer on a MUD (Multi-User Dungeon -- like an MMO without the pretty pictures). The process for getting an area through all the quality control checks and into live game is hellish. We go through Alpha QC, Bravo QC, Balance, World (for authenticity's sake), and then our fellow-coders test the new area. Then we go through it all again, and a select number of players test the new area on a test server for a full month before we have to go through the whole process... again. We get bug reps coming out our ears, and it takes no less than ten months for a new coder to get an area into the game -- unless he's a professional coder in real life, or he HAS no real life.
I have seen the dev cycle, and it is agony. If our area/item/NPC breaks in some way, shape, or form, we are told to go and fix it until it works. We test and retest and then have players test and retest. Granted, the game is nickel-and-dime. We don't charge money to play, everything's volunteer, and we're certainly not earning anything by it. Plus we don't have those tricky graphics issues to worry about. But the game world is massive. And detailed. And 99% bug-free.
I can allow that changes to the CU weren't supposed to -- in an ideal world -- have affected crafters. I can also allow that test players, who are totally volunteer, might not have thought 'Oh, I should be testing the Tailor profession as well as all these combat classes.' I can even allow that maybe tailoring worked on the Test Centre.
However... If, on the MUD where I code, our area/item/NPC breaks the game in some way, the offending code is automatically and immediately taken out of the game and the world -- not the players, the world -- is rolled back into place. It doesn't affect the players, because their code is part of a different database.
Why, since this is deeply damaging to us as tailors, was the world not rolled back until this could be fixed? Obviously no one tested this... or if they did, and it was trouble-free, there is some difference between Test Centre and live servers. Doesn't that rather defeat the purpose of having a Test Centre? Does SOE even have a QC department? Or testers? We know that SOE can roll back the world... they've done it before, much to our chagrin. What happened in publish 18 that was so important that it needed to be live Right Now?
So! My questions are:
1) how did this get past QC?
2) why wasn't the patch rolled back right away?
3) what is the status on the fix?
If someone can answer this, I'll be very happy, and SOE can keep having my $100/month. If someone can't answer this, I will cancel all five of my accounts. I've been playing since launch, and it's just not worth the agony anymore.
/Ganryú
Is there anyone out there who could explain why this bug exists in live? I only ask because in my experience, bugs like this are typically caught in QC.
I am a programmer on a MUD (Multi-User Dungeon -- like an MMO without the pretty pictures). The process for getting an area through all the quality control checks and into live game is hellish. We go through Alpha QC, Bravo QC, Balance, World (for authenticity's sake), and then our fellow-coders test the new area. Then we go through it all again, and a select number of players test the new area on a test server for a full month before we have to go through the whole process... again. We get bug reps coming out our ears, and it takes no less than ten months for a new coder to get an area into the game -- unless he's a professional coder in real life, or he HAS no real life.
I have seen the dev cycle, and it is agony. If our area/item/NPC breaks in some way, shape, or form, we are told to go and fix it until it works. We test and retest and then have players test and retest. Granted, the game is nickel-and-dime. We don't charge money to play, everything's volunteer, and we're certainly not earning anything by it. Plus we don't have those tricky graphics issues to worry about. But the game world is massive. And detailed. And 99% bug-free.
I can allow that changes to the CU weren't supposed to -- in an ideal world -- have affected crafters. I can also allow that test players, who are totally volunteer, might not have thought 'Oh, I should be testing the Tailor profession as well as all these combat classes.' I can even allow that maybe tailoring worked on the Test Centre.
However... If, on the MUD where I code, our area/item/NPC breaks the game in some way, the offending code is automatically and immediately taken out of the game and the world -- not the players, the world -- is rolled back into place. It doesn't affect the players, because their code is part of a different database.
Why, since this is deeply damaging to us as tailors, was the world not rolled back until this could be fixed? Obviously no one tested this... or if they did, and it was trouble-free, there is some difference between Test Centre and live servers. Doesn't that rather defeat the purpose of having a Test Centre? Does SOE even have a QC department? Or testers? We know that SOE can roll back the world... they've done it before, much to our chagrin. What happened in publish 18 that was so important that it needed to be live Right Now?
So! My questions are:
1) how did this get past QC?
2) why wasn't the patch rolled back right away?
3) what is the status on the fix?
If someone can answer this, I'll be very happy, and SOE can keep having my $100/month. If someone can't answer this, I will cancel all five of my accounts. I've been playing since launch, and it's just not worth the agony anymore.
/Ganryú
Mishekal
Fri Jul 29, 2005 5:40 pm
#138
Ganryu wrote:
It's been six weeks since this bug was introduced.
Is there anyone out there who could explain why this bug exists in live? I only ask because in my experience, bugs like this are typically caught in QC.
I am a programmer on a MUD (Multi-User Dungeon -- like an MMO without the pretty pictures). The process for getting an area through all the quality control checks and into live game is hellish. We go through Alpha QC, Bravo QC, Balance, World (for authenticity's sake), and then our fellow-coders test the new area. Then we go through it all again, and a select number of players test the new area on a test server for a full month before we have to go through the whole process... again. We get bug reps coming out our ears, and it takes no less than ten months for a new coder to get an area into the game -- unless he's a professional coder in real life, or he HAS no real life.
I have seen the dev cycle, and it is agony. If our area/item/NPC breaks in some way, shape, or form, we are told to go and fix it until it works. We test and retest and then have players test and retest. Granted, the game is nickel-and-dime. We don't charge money to play, everything's volunteer, and we're certainly not earning anything by it. Plus we don't have those tricky graphics issues to worry about. But the game world is massive. And detailed. And 99% bug-free.
I can allow that changes to the CU weren't supposed to -- in an ideal world -- have affected crafters. I can also allow that test players, who are totally volunteer, might not have thought 'Oh, I should be testing the Tailor profession as well as all these combat classes.' I can even allow that maybe tailoring worked on the Test Centre.
However... If, on the MUD where I code, our area/item/NPC breaks the game in some way, the offending code is automatically and immediately taken out of the game and the world -- not the players, the world -- is rolled back into place. It doesn't affect the players, because their code is part of a different database.
Why, since this is deeply damaging to us as tailors, was the world not rolled back until this could be fixed? Obviously no one tested this... or if they did, and it was trouble-free, there is some difference between Test Centre and live servers. Doesn't that rather defeat the purpose of having a Test Centre? Does SOE even have a QC department? Or testers? We know that SOE can roll back the world... they've done it before, much to our chagrin. What happened in publish 18 that was so important that it needed to be live Right Now?
So! My questions are:
1) how did this get past QC?
2) why wasn't the patch rolled back right away?
3) what is the status on the fix?
If someone can answer this, I'll be very happy, and SOE can keep having my $100/month. If someone can't answer this, I will cancel all five of my accounts. I've been playing since launch, and it's just not worth the agony anymore.
/Ganryú
Simple answer, and we have all experienced it.
Corporate socialgeo-politics.
Keep in mind, that for the most part, the devs want to do good things for the game. After meeting some at Fan Fest, it is obvious that they are handicapped in several ways.
1) Staff is too small for the job at hand, espcially to fix post CU game breakers in any resaonable time frame.
2) Coporate Management is more interested in a quick buck than a long term quality service.
3) Dev staff is constrained by a leadership more interested in fixing grahic quirks instead of game function.
4) The dev staff we have now is not the staff, for the most part, the originally wrote the code. The combination of limited QA testing from the get go, and the loss of the master coders, has resulted in spagetti code that breaks in unknown areas when modified as intended.
Don't know about you, and this is like every place I have worked that had a core service based in the computer business.
And people wonder why 65% of IT projects die, get canceled, are so late as to loose relvence, or cost so much the product never has a ROI.
Not much we can do to SOE directly, andone course of action has been to investigaterights as a consumer with the state of California.
Maybe we should all do something similar?
NJ62
Sat Jul 30, 2005 6:33 am
#139
Bleh I was hoping not to do this...
...
I updated the FAQ to reflect the fact that BE clothing cannot be made at this time.
I am holding the devs personally responsible for making me do this heinous chore of updating the humongous FAQ. I mean, I had to manually type in HTML! What is this world coming to?
In short, as those cheesy movies say, "now it's personal."*
*just trying to lighten the mood
...
I updated the FAQ to reflect the fact that BE clothing cannot be made at this time.
I am holding the devs personally responsible for making me do this heinous chore of updating the humongous FAQ. I mean, I had to manually type in HTML! What is this world coming to?
In short, as those cheesy movies say, "now it's personal."*
*just trying to lighten the mood
MirthDragonfire
Sun Jul 31, 2005 3:12 am
#140
NJ, I know you are already upset and I dont want to pick on one of the "goodies" but, when you wrote in the FAQ
Warning - Do not make bioengineered panels or clothing at this time. All stats are lost when bioengineered tissues are combined into synthetic or fiberplast panels. If you put enhanced panels into clothing, the bonuses are also lost in the combine. We are waiting for a fix on this issue.
I just wondered if it should be in BIG RED LETTERS, as it sort of blends into the rest of the post atm. I know I am being very picky, but this is the MOST important piece of info for anyone who is considering Tailoring as a prof right now.
Sorry m8
Mirth
MirthDragonfire
Sun Jul 31, 2005 4:57 pm
#141
This is exactly why I always liked you NJ. As a correspondent and now in your still active "after-life" .hehe
Even when I was having a moan , you listened to my point of view
/big respect
/bow
Mirth
revatitarq
Mon Aug 01, 2005 6:58 am
#142
Well it's now what 2 months since this problem hit us? Personally I'm starting to believe what a friend of mine has been saying since the BE issue hit. He says they are phasing it out and basically BE clothes will be gone for good. I'm hoping he's wrong but 9 times out of 10 this person has been right on the money. In fact when I hear rumors I usually go straight to him to hear the truth. He's a major forum reader goes to the Fan Fests etc so I trust his judgement. I just pray that this time he's off the mark. But the way things are going I get the feeling he's right about this one too. I know I wont' drop tailor but I do know many people will, which in turn puts a strain on the tailors that are left. As it is we are a rare breed, so rare that I will not wear my Master Tailor tag while out and about because I get swarmed by people who want clothes made.
Please SOE fix our BE clothing, we want it and need it!! Give us some sort of update it's been a month since we heard Freeman's reply and we need some news! Thank you!
Ganryu
Mon Aug 01, 2005 7:11 pm
#143
Mishekal wrote:
Simple answer, and we have all experienced it.
Thanks, Mishekal. I wasn't aware that the dev turnover at SOE was so high, although I suppose I should have expected that. I guess one can hope, but until I hear that the problem has been fixed, I've cancelled all five of my accounts. This simply isn't the game it once was, and I doubt things will soon be returning to a state where I actually enjoy playing.
I appreciate your thorough reply, and you have made an interesting suggestion, in terms of investigating our rights as consumers. It may definitely be worth looking into.
Cheers,
/Ganryú