Weaponsmith Archive

/doublesign

You know 5 armorsmiths said no to the restriction of bags on vendors, and they removed that the next day.

---

yojimbosunrunner wrote:
just became a master chef and now they are going to change my recipes....

WFT!!!!

yojimbo

---

I think we all know what WT F means...but what is WFT?

Although I feel your pain bro...I can't speak because I am so baffled too.

Message Edited by HoxStarclipper on 03-11-2004 12:21 PM

/sign

Lets keep the little diversity ther currently is in crafting instead of the all or nothing that this nerf is going to force.

---

Quinnt13 wrote:

First, let me /sign.

Second, believe it or not, the longer they go without putting out some sort of communication about this change (which was supposed to come out yesterday), the better the chance of this change not going live. I envision alot of discussion going on at SOE right now, and the fact that they are not talking to usat all about this leads me to believe the chances of this change going live are getting slimmer...

Of course, this is partially just wishful thinking on my part, so we'll see.

---

OK why don't we split up the work load here...I'll keep thinking and you keep wishing...I need a bunch of you to chant...and the wookies neet to grab their robes and do their little cerimonial dance...Let's make a burnt offering to the devs and maybe we can stop this thing.

i am not a weaponsmith yet but if this nerf goes thru i know of at least 8 people on the flurry server alone who have said they will cancel their memberships and start playing a game where the developers aren't screwing the gamers over every couple months. I dropped CH after one of the last nerfs because the dev screwed that profession, after spending 3 weeks to almost master it. the nerfs have to stop because one nerf causes there to have to be other nerfs in the future. if they want to keep players playing the game they better stop with the nerfsor they will cause the people to play games where the games wern't rated 1 out of 10 by the magazines

/sign

---

Quinnt13 wrote:

First, let me /sign.

Second, believe it or not, the longer they go without putting out some sort of communication about this change (which was supposed to come out yesterday), the better the chance of this change not going live. I envision alot of discussion going on at SOE right now, and the fact that they are not talking to usat all about this leads me to believe the chances of this change going live are getting slimmer...

Of course, this is partially just wishful thinking on my part, so we'll see.

---

This is funny, but not likely. Being a SW developer myself. I think it is more likely that the guys that actually wrote this are now working on Publish 9 or 10 on a completely different branch of the code, and could care less, manily because they have adev schedule to follow.As far as the boys in QAgo, well they are already pushing code. Nobody likes having to make a major change to thebranch, (i.e. rip out the nerf). Puts everything else too far behind. Also they can't even make a promissed spin response on time, how can you expect them to actuallywrite thecode to rip out the nerf. That's just crazy talk. This has got the looks of the classic "Lets just get this pushed out and in place first, and we will deal with the fallout afterwords" strategy. On a personal note to TH. I've played the customer relations dance for many years, and my experience has taught me this. To quote the Godfather. "The Don is man who insists on hearing bad news immediately." The sooner you tell your customers the bad news, the sooner they will get over it, and the more integrity you gain. By waiting and dragging out your response on this you make its content meaningless.

How do you expect the devs to make something useful when they are not even able to correct the PSG problem...the programming skills level must be very low at SOE...

Not very happy with that asa two days old Armorsmith...

/sign x2 accounts (who can be cancelled very quickly...)