Droid Engineer Archive
Thread: Some answers from the Devs
Yes, we're looking at droid modules and will be upgrading them as time permits
We're very excited to see the interest in combat droinds being used by crafters and non-combatants and will be making adjustments to make them more viable in that regard.
Yes, droid armor is being fixed as we speak.
"as time permits" It took over a year and 2 publishes ti fix the first time, that answer is BS and you need to through it back in their face. Not acceptable.
I personally would like to see things actually answered. Not to say I don't appreciate when they are doing, but I would appreciate it more if they didn't beat around the bush.
/puts on SOE translation cap.
Jenden wrote: As many of you noticed from the questions thread earlier, we had a chance to get some questions for the devs to answer. Here are the ones that I went with (pulled the experimentation one and HAM one from the list since we've already gotten some feedback on them). Not the most detailed of answers, but better than the "outside the current focus/timeline" that a lot of the questions ended up with.
Yes, we're looking at droid modules and will be upgrading them as time permits
Time permits is bad, don't look for this "soon."
We're very excited to see the interest in combat droinds being used by crafters and non-combatants and will be making adjustments to make them more viable in that regard.
Translates as.. this actually may happen within a short period of time. Unfortunatly it will be a quick band-aid thing to stop the flood of crafters leaving, and not really designed as "droid love."
Yes, droid armor is being fixed as we speak.
Give it a week or 2, pet rmor is borked too, probably all being worked on together.
Straker...too funny, but too real. I manage development teams. The answer to the first question is awful. "as time permits". That is speak for "we have no time tothink aboutthis now, so this is the answer we will give to passify you. We have other, more recentproblems that we created that we have to fix."
It's great to get feedback from the devs, don't get me wrong, but please - we don't need our intellgence insulted. I may have been born at night, but not last night. Personsally, I'm a very honest guy. My client's would much rather hear me say what we believe our priorities to be and the direction we're headed than to hear me rattle off vague quotes like this, only to dissappoint them later on. If our modules and, ultimately,our professionare not on their radar, then tell me so. I'll either accept it, move on to a new profession, or leave the game. But quotes like this do nothing but create more mad customers down the road.
Jenden wrote:
Given that they actually gave "out of the current planning scope" or "not currently being planned" response to many of the questions others asked, I take this as a sign that this stuff really is being worked on/concidered. Its not a lot of details, but its hard to give details before something's actually implemented.
They are blowing smoke up your skirt. BTW, what the hell are the AS's doing right? They've gotten a TON of answers, adjustments and fixes.
Do we know if the yare going to fix the armor schematics when they fix armor?
Do we know if they are going to fix harvesting droids?
We also have the huge problem of bomb droids not working and droid stimms not working.
/bow
Napard wrote:
Straker...too funny, but too real. I manage development teams. The answer to the first question is awful. "as time permits". That is speak for "we have no time tothink aboutthis now, so this is the answer we will give to passify you. We have other, more recentproblems that we created that we have to fix."
I'd have almost preferred that they actually just pony up and say that. It's always been the sort of communication that's most effective.
It's great to get feedback from the devs, don't get me wrong, but please - we don't need our intellgence insulted. I may have been born at night, but not last night. Personsally, I'm a very honest guy. My client's would much rather hear me say what we believe our priorities to be and the direction we're headed than to hear me rattle off vague quotes like this, only to dissappoint them later on. If our modules and, ultimately,our professionare not on their radar, then tell me so. I'll either accept it, move on to a new profession, or leave the game. But quotes like this do nothing but create more mad customers down the road.
Yes..."patronizing", I think it's called (the literal definition, anyway). I'm sure it is the best answer that they can give for our woes currently...which is truly the saddest part of all.
Those answers were right out of the HoC Dev response handbook.
Respectfully,
Zilod wrote:
I think a simple solution will be to consider droid level for group level this way a lv1 artisan grouping with a lv 18 combat droid will have lv18 and will not be insta incapped
ASHRID wrote:
Zilod wrote:
I think a simple solution will be to consider droid level for group level this way a lv1 artisan grouping with a lv 18 combat droid will have lv18 and will not be insta incapped
Isnt this they way its supposed to work at the moment anyway?
Don't think so, pets are supposed to not modify group level so i suppose is the same for droids...
Combat especially should be the first thing on there list, and there are other bugs out there I'm sure that would come first ahead of all other things.
But straight answers is much better then, beating around the bush.
