Droid Engineer Archive
Thread: why people so mad at thunder??
loomis001 wrote:
LISTEN PEOPLE ! thunder has no say to what stuff will go live or not hes not REAL DEV hes here to give devs feedback
And he failed miserably.
Bottom line: He lied.
Never was a Droid Handler profession a consensus among DE's. He stated it was clearly what we wanted. It couldn't be any more clear that DH is something most DE's do NOT want.
lied? how he didnt say 100% for sure it will go in, devs have to approve it first
YOU GUYS ASK FOR THIS stop crying....... i seen post on this forums saying that you want de to be a crafting professon not a combat....
loomis001 wrote:lied? how he didnt say 100% for sure it will go in, devs have to approve it first
So we shouldn't be mad that he's misrepresented us, and has telling the devs that we want things we really don't?
Should I wait till it hits the live servers to be pissed?
Loomis please red carefully... We are not talking about the proposal hitting live or not, we already know its just a proposal.
TH lied when he said DE community had said very clear they wanted a separate DH professionafter we said him specifically we didnt want it.
Ellesa
Long version:
- Because at the end of december he created an impression that there would be a lot of discussion WITH the DE community regarding new droid changes. He even called it "the droid invasion"
- Because he created an expectation that there would be an in-concept thread in early July to discuss ideas
- Then, after creating the expectation, no post was made and no communicatin was made as to why it was delayed.
- Finally, last week we got some word on DE changes, but it was only bug fixes -- which was very good but far short of the expectation set.
- Then, yesterday when someone asked why there was a delay, TH implicated the DEs as the reason saying DEs "clearly" stated they wanted two professions in spite of the fact that several communicated the OPPOSITE with him.
- As a result, he failed to meet an expectation HE set and lost credibility with the DE community. Many DEs have worked hard trying to come up with WORKABLE ideas to improve the profession and this experience has probably left most feeling like all that work went unheard in the past and possible in the future.
Short version:
- He aimed a gun at his foot.
- He pulled the trigger.
loomis001 wrote:
YOU GUYS ASK FOR THIS stop crying....... i seen post on this forums saying that you want de to be a crafting professon not a combat....
We asked not to have DE turned into a combat class. We also asked for a cert system to ensure that something like a Droid handler class didn't emerge.
So Yes, I think I will be angery as what we've been said has been given a cursory glance over, no feedback, no other questions, no checking to see if that's what we meant, and then to be told that we specically said that we wanted a DH class (Strange, I never remember TH bringing up the idea of that class)
loomis001 wrote:
YOU GUYS ASK FOR THIS stop crying....... i seen post on this forums saying that you want de to be a crafting professon not a combat....
Have you read the poll????
I said I want to be a crafter. As I've already said to TH, that doesnt mean I cant use droids!!
I remember you from TC when posting about vehicle schematics... please dont begin posting in the same way you did there...
Ellesa
Today, TH has said that "a cert system probably won't work".
This means that DE's can either be a CH clone, or a BE clone.
This is NOT what we wanted.
We wanted to make droids in the Star Wars universe - where you don't have to go to school to tell a droid, "Attack that beastie". We wanted slicer droids, we wanted juke box droids, we wanted survey droids - the list goes on.
Why am I personally mad? Because it is obvious that the tens of thousands of constructive posts that have been made have been ignored. Because droids were not taken into consideration while everything else was ballanced, and now droids must fit the SWG ballance mold, not the Star Wars theme. Because of the tactics that I see again and again - promise X by time A, and wind up getting Y at time B - with Y not being as good as X, and B being a lot later than A.