Droid Engineer Archive
Thread: Next Set of 19 Questions answered...
JavelinCatcher wrote:
TK asked my question ....I'm touched.
Hehehe...as well you should be. ![]()
But seriously, you put forth the MA concern pretty well (and TH sorta dropped this on us at the last minute, so I went with it)...
Next time, I'll have a chance to poll you all about what we'll ask.
We've now had:
- DC guidelines (on which we are still waiting)
- Extra droids in datapad or 'called'
- MA interdependence
AudioOrgana wrote:
I'm not sure what kind of "case" TH wants us to make - Developers have posted before and said "Yes, we know you have an overdependence on MA parts". The case is - it's an admittedproblem, and it sucks, it needs to be fixed.
Not sure how much more there is to say, hehe.
AO
The case is why we need to have this reduced when we may be the standard to which other crafting professions are raised.
A long time back, TH stated that crafting interdependence would go up or down (paraphrased). It appears that they will ALL go up. Maybe we won't see that quite as harshly. /shrug
I think the "case" he would want us to make is:
- Just how imbalancing/problematic is the dependence to MA
- Is there a solution that reduces this while still keeping our interdependencies at the level that they are getting to...
/bow
Respectfully,
Message Edited by TheRealTK421 on 06-10-2004 07:18 PM
This is sounding like where they want to head on the MA issue...
Bearalag wrote:
I don't think we shouldscale back the interdepedence with MA, I think other Professions should be brought in line with us DE's. Make other Professions more Interdependent on other Professions. More sales for everyone!
Still, I think the dependence to MA for EMMs and EGPs is overly draconian and 'saddling' (to paraphrase TH).
I'll continue to bang the drum on this but I wouldn't expect much to change in the near term.
/bow
Respectfully,
psikobunny wrote:
Moving back onto the topic of 19 answers, I want to note that this week there was yet another question/answer that related to a minor and annoying functionality/bug fix (Architects and storage items). This is at least twice now whereI have seen apparent response and movement based on a 19 answers question (the other being the second Tailor question about necklaces iirc). Nothing has materialized in the way of fixes yet, but at least the answers given entertained the notion of getting it taken care of before JTL. I know TKsaid a specific thread will be forthcoming askingfo opinions on our next question, but I want to jump on my soapbox early. I propose we ask specifically and directly about our issues with Conversation Droids. The naming of them, and the Surgical Item storage bug to be exact.
It's been a thorn in out sides too long, and I think we can get some help if we ask for it clearly, distinctly, and publically.
The bunny is dead-nuts!!!! The medicaldroid storage item may seem like too small of an issue to "waste" a question on, but I think it will kill3 dev..er birds with one head shot:
1.) Surgical droids will no longer be the "exception" when someone asks you about making a storage capable droid. This adds versitility to a droid frame which equals more configurations to sell.
2.) No more wasted in-game time explaining the "storage in surgical droid" bug. Less time talking, more time selling droids ![]()
3.) Removing this bug will simplify the "BIG DROID MYSTERY" that some players experiance when asking about droids, and from reading the posts, simplicity is something we all seem to agree on.
Its a simple question, its concise, it is a well known and identified problem, and It (seems) it might be easy to fix.
....sounds like a good '19 ? thread' that would be hard to JTL away!
...thanks
CHODA----MDE/Droid teacher to the Kettemoor massess