Droid Engineer Archive
Thread: Problem with General Droid Socket Cluster ???
It's not a bug, it's a ner... uh, feature.
Basically, if you want to make R2 (and R3) units, you'll have to put modules in a combat-capable cluster.
Chronic wrote:
don't know if anyone else has noticed this but not one droid will take the General Droid Socket cluster any more, I was going to makea new R2 unit for someone and I can't do it now..
So SOE! is this a Bug or a what as this needs fixing ASAP!
I think the Advanced Surgical should take the GDSC still, but yeah, I don't think anything else can.
I'm guessing this is a bug and GDSC are suppose to be able to go into the combat cluster slots just like service modules can go into combat module slots.
I would also appreciate a clarification as to whether this is a bug or oversight that will be changed, or an intentional change. I can see having a requirement for the combat socket cluster in the probots, but it is silly to *require* them for the R-series astromech droids, just because they were selected as filler combat droids. Astromechs should be able to accept the general purpose socket clusters.
And, yes, I too have a nice supply of factory crates containing pre-configured general purpose socket clusters. It is difficult enough for a relatively new DE to become established in business, without ill-conceived changes that result in invalidating existing components.
Malitevv wrote:it has been stated by TK elsewhere that this is NOT a bug, but a new feature. Personally, since the only chassis the old cluster module is usable in are useless droids that no DE ever crafts more than once or twice, its pretty darned silly that they left the thing in the game at all. They should have just never created the combat cluster and instead removed the cluster socket from the few droids that have it which are not combat capable. It would make more sense, and would cause much less pain to the people who actually play this profession.I know its a useless point, because it's over and done with now. But its so exasperating. There is little chance that anyone who makes the decisions about these things back at SOE has ever played this profession seriously. If they had, they would have known to put these sorts of things at the top of the patch notes list./end rant
It's a weird feature, but I'm starting to see the sense in it. Any given higher end droid would take a module cluster, but the way the game is designed, if you put a combat module in a cluster, you could install the cluster in any droid that would take them. SO, they made the combat capable droids accept only the new combat clusters, the only cluster type that will accept combat modules. You can, however, install standard modules in combat clusters. Unless they change something, I just plan on keeping a crate of standard clusters and a crate of combat clusters around. I'm not happy about the increased resource use AND the extra factory runs though... Here's to hoping the devs will change things to allow all droids that take clusters to accept standard clusters again, and make it so any combat capable droid will accept either, only requiring the combat cluster if you're installing a combat module.
Chris
Actually...it's been like 1 week.
DarthIguana wrote:
The poor SOB has been our correspondant for like 3 weeks.
/bow
Respectfully,
TheRealTK421 wrote:Actually...it's been like 1 week.
DarthIguana wrote:
The poor SOB has been our correspondant for like 3 weeks.
/bow
Respectfully,
OK, a week then. So you've had even less influence on Pub 7 than I thought
Chris
Dyna_Jones wrote:This is a bug not a feature. I can't believe TK rolled over so easily on this.
OMFG you can not possibly be blaming TK for a change that you dislike in the latest publish. The poor SOB has been our correspondant for like 3 weeks. The features in this new publish were in play long before he got here. He didn't have time to have any real influence over how this publish effected our profession.
Chris