Droid Engineer Archive
Thread: Droid Report: Understanding Combat Clusters vs. General (Utility)
Page 1 of 4
TheRealTK421
Tue Mar 16, 2004 9:33 pm
#1
Heya, all...
I'm seeing some confusion on this, so I wanted to kick something out and let you know the deal...
Enjoy!
I'm seeing some confusion on this, so I wanted to kick something out and let you know the deal...
Enjoy!
Modules - Combat vs "Service"
Droid Combat Modules:
These babies are crafted up as single components (or factory crated), installable only into Combat-Capable Socket Clusters (below).
Combat modules are discussed in more detail (stats, etc.) in other threads, so I won't get into that here. Suffice to say, you want to make the best one you can.
Droid Service Module Harness:
This type of module is a "utility" (non-combat) droid module:
- Any type of crafting station
- Droid Item storage (any level)
- Droid Data storage (any level)
- Droid Repair module
- any non-combat utility module (that might appear in the future)
Clusters - Combat vs "General" (Utility)
Combat-Capable Socket Cluster (CCSC):
This type of cluster can accept both Droid Combat Modules and Droid Service Module Harness. If you need to, for example, create a "utility"-only droid...but in an R2 chassis (for a player that wants it that way), you'dhave to use this cluster.
If you'll be installing crafting stations, Item storage, etc. (i.e. ANY non-combat modules), you'll still have to use this. The Cluster has to stay with the chassis it's assigned to...
So, you should use these to create 'mixed' droids (some combat, some utility) or "all utility" droids, whenthe desired droid type is a Combat-Capable Chassis listed below.
Combat-Capable Chassis (to accept only CCSC):
- DZ70 Droid (note: these do NOT accepct "Clusters", only non-clustered combat modules)
- LE Droid
- Probot
- R-Series
General Droid Module Socket Cluster (GDSC):
These clusters will only accept Droid Service Module Harness parts. They can only be used in the General Droid Chassis listed below:
- BLL Adv Droid
- MSE Droid
- Power Droid
- Surgical
- Treadwell
Note: "Generic Item" (Bounty Hunter) droids, the Arakyd Probe Droid and Seeker, cannot accept any type of droid module or cluster.
/bow
Respectfully,
Message Edited by TheRealTK421 on 03-17-2004 09:51 AM
Malitevv
Tue Mar 16, 2004 9:38 pm
#2
this has me enormously angry. they should have told us they were going to break it so that all of our existing general socket clusters are going to be useless. the fact is that the only utility droid worth making that takes a socket cluster is the R-series units. I busted my ass making 17 of them last night for an order for 17 R3 droids (place by the mayor of a player city). WIth the intention of finishing the droids today, and now I can't. All that work flushed down the toilet.
Dyna_Jones
Wed Mar 17, 2004 12:05 am
#4
ok finally read this after posting in the main thread
A little heads up would have been nice at least I can throw my socket cluster in a lumbering BLL and give it to a good home 
biggie2
Wed Mar 17, 2004 12:05 am
#5
my simple solution- i have 6 factories to make my crap so i never ever grind out crap
Mightion
Wed Mar 17, 2004 12:49 am
#6
So this is intended? My crated level 6 data/item/medical clusters can't be used in astromechs anymore? I have to remake them in combat-capable clusters, using ....Joy! more droid brains?
Why? Why can't a combat-capable socket cluster still take a GDSC?
Neroir
Wed Mar 17, 2004 2:27 am
#8
It does not make sense at all.
If a combat cluster can have both utility and combat modules, a cluster shocked MUST be able to use both Generic and Combat clusters in Astromechs at least
Ellesa
If a combat cluster can have both utility and combat modules, a cluster shocked MUST be able to use both Generic and Combat clusters in Astromechs at least
Ellesa
Message Edited by Neroir on 03-17-2004 01:29 AM
DarthIguana
Wed Mar 17, 2004 8:42 am
#9
Why the hell do we need CCSC *AT ALL*? Why do we need yet ANOTHER componant added to an already long list of subcomponants need for higher end droids? A module should be a module, be it crafting, storage, data, or COMBAT. Everything involved with creating a max power combat droid involves something special or different than the componants and resources the droids previously required. It's overkill and absolutely not worth the effort, cost of production, and price at market when you look at the final product. I'm happy, to a degree, that they've given droids some fighting potential but do we really need to jump through all these flaming hoops to make them when they suck next to BE non CH pets? What is the next publish with new utility modules going to require? Will the droid that provides the portable light show created by the new entertainer module going to require entertainment capable socket clusters? Will I have to created two and install three fully experimented entertainer modules (requiring even MORE named gasses, ores, and metals) into each so the light show will display a full array of colored lights?
Chris
Chris
Darth_Raptor
Wed Mar 17, 2004 8:54 am
#10
For as little as we provide to the community, we sure do have alot of stuff that we have to craft / make factory runs of to make these guys. If they would loose just a tad of this complexity, I would bet that we would be happier and would save some money for sure.
TheRealTK421
Wed Mar 17, 2004 8:57 am
#11
Because of how some chassis now are 'combat' and some are 'non-combat'.
DarthIguana wrote:
Why the hell do we need CCSC *AT ALL*?
Basically, the cluster type has to go with the chassis type.
I don't see this changing in the shorter term. We have bigger fish to fry right now, everyone. Just use the system a bit and you'll be able to work it in to how you do your thing.
/bow
Respectfully,
DarthIguana
Wed Mar 17, 2004 10:10 am
#12
TheRealTK421 wrote:Because of how some chassis now are 'combat' and some are 'non-combat'.
DarthIguana wrote:
Why the hell do we need CCSC *AT ALL*?
Basically, the cluster type has to go with the chassis type.
I don't see this changing in the shorter term. We have bigger fish to fry right now, everyone. Just use the system a bit and you'll be able to work it in to how you do your thing.
/bow
Respectfully,
I find this to be really funny. The devs have been saying for months that droids are tough to mess with and fix because they touch so many different games systems. This arguement makes sense to me and, even though I wanted things fixed, I was glad they were taking their time and trying to do it right because of the ripple effect a problem with droids could create. So what do they do now?
Make things more complex.
What a pain in the **self edit**
I agree, we have bigger fish to fry, but I don't understand why the devs went out of their way to create further complexity in an already complex profession. How many factories should we be expected to have running at a given time so we can produce the majority of our wares in a reasonably short delivery time? I'm glad that I was busy stockpiling resources in advance of this publish rather than stockpiling factory parts like some people...
Chris
OrionsByte
Wed Mar 17, 2004 10:36 am
#13
TheRealTK421 wrote:
Heya, all...
Combat-Capable Chassis (to accept only CCSC):
- DZ70 Droid
- LE Droid
- Probot
- R-Series
Say it isn't so... they didn't bork it up and allow Combat-Capable Socket Clusters to fit in to a Combat-Capable Socket Harness, did they? The DZ70 only takes a Combat-Capable Service Module, not a cluster. If the clusters are fitting in to this socket, we've regressed a month in terms of progress.
Page 1 of 4