Droid Engineer Archive
Thread: Clustering? exploite or not ? What have the DEVs say
So it's bad language describing a bad situation.
Kitsunetsuki wrote:
What are we to do.
Fix it.
I think the description you're talking about is intended to indicate that you can put a variety of droid modules into the socket cluster. Two is not a "variety." Why would they have bothered making schematic slots specifically for clusters? Why include more than one module slot in any droid schematic if it is intended for players to be able to use clusters in any droid?
Saying, "I agree that it doesn't make sense and it's bad, but I think it's a design mistake so I'm going to do it anyway" is just rationalization. It's a thinly veiled version of the same argument exploiters always make, "it's the devs' fault for putting exploitable bugs in the game, not mine for exploiting it." This is in turn no different from an argument that if someone forgets to lock their house, then it's okay for you to walk right in.
But the description doesn't say it accepts a variety of droid modules. It says it fits a variety of sockets. That is what the description says and that is also exactly what the module does. I am not saying it is a design mistake. I am saying I believe it is working as designed. The question was is it working as designed and since the description says it fits more than one socket and in fact it does fit more than one socket tells me the answer the the original question is yes.
That being said it doesn't mean it is a good design, but that is a entirely different question.
Kiom wrote:
Hehe. Where's my lawyer? Opps.... I think I'm trouble as I hired a guy named TH.
No comment.
Kiom wrote:
Droid_Engineer_Rho wrote:
Technically, doesn't it say 'fits a variety'? That could kinda-sorta be interpreted either as 'fits into a variety' or 'can be fitted with a variety'.
So it's bad language describing a bad situation.
It says "This is an array that can fit a variety of droid sockets".
Is it possible the wording AND the function are wrong? Sure it is possible. Does anyone here know? Nope. We can only go on the descriptionand what it doesand in this case it does exactly what it says.
/agree
I also agree with those who say this is a poor design that should be fixed. It makes no sense that a low-end droid can hold more modules as a higher end droid. But I don't think we have a definative answer, especially in light of the express language quoted above.
Lets get some perspective. LE Repairs don't repair, Surgies dont store items or repair, double armor slots were nerfed, droid tracking is whacked, battery binge drinking is common, and BLLs don't do crap! Selling a functional cluster-loaded droid is not a crime.
THE ANSWER is in two parts
1) FACT it is a oversight in sloppy codeing that allows such an endevor to happen. it is and never was inteanded for you to be able to cluster stack, nor for you to use clusters in a single module slot.. the expression "fits a varaeity of modules" implies that you can choose 1 of many, any other interpitation is pure ignorance. The stupidity of some people , and then the attempt to make an excuse to justify their actions in thier exploits is beyond me.
2) FACT nothing anyone says , even a DEV, or CRS, or even C3PO says will change the fact people who exploit, will continue to do so, and attempt to rationlize it for their own pittiful sense of self worth, untill the flaws in the game are fixed.. people are going to use them.
3) BONUS be happy I am not a CSR, as I would make sure in my off time I took notes of bug users, and exploiters, I would simply ban their account, and be done with it, game is better off without them anyway.
Gveedo ( pardon my spelling I dont care enough to use a spell checker. )
TheWoody wrote:
At a minimum that is enough to be able to stand up in court and claim innocence with!
Fortunately, though, this is not a court of law, and thus we have a little more latitude to use our common sense and to point out when people are using selective interpretation and transparent sophistry to arrive at an conclusion they personally find convenient.
I calls 'em as I sees 'em.
Given the way the rest of the profession works, yes, I find it more plausible that the description should properly say "module" rather than "socket." That once sentence is the entire description of the Socket Cluster. If Kiom's convenient interpretation is accurate then the "description" of the module in fact does not describe the module at all. It'd be like "describing" an electrical appliance by saying only, "this is an appliance that plugs into a variety of wall outlets." That tells you nothing about what the appliance does. No other module's description talks about what kind of schematic slot it fits in, much less to the exclusion of describing the module's function.
Read the bold type carefully. It says "...can fit a variety", not "... can fit in a variety..."
Kiom wrote:
The definition of a cluster modulestates "This is an array that can fit a variety of droid sockets". Clearly that is plural as to mean more than one type of socket. There are three types of sockets and the cluster module fits in 2 of them.
Hehe. I know it doesn't say "in" but it also doesn't say modules either. It says sockets. Or are you saying a "Level 6 Droid Medical Module" is actually a "socket"?
Look we can disagree with the design or how locical or not it is to have a cluster modules fit in anything other than a cluster socket. But in this case the module does exactly what it says it is suppose to do. Saying that it doesn't make sense so therefore is must be an exploit just doesn't apply. Look at the BLL. Is that a "locical" droid? I think not.
Bottom line is until a DEV comes on here and says yes or no, none of us know for sure the correct answer.
Eutock wrote:
Using a bug to your benefit is the definition of an exploit, pure and simple.
Using an exploit just because your profession is 'broken' (read: bugged!) is a double exploit. Two wrongs do not make one right.
So, if I don't think it's a bug -- I'm in the clear! 
It's a design flaw. Along with stacking, which makes it possible for low-level DEs to make the best droids, and modularization which makes it possible for all droids to do all things, and the ability for all DEs to color droids without referencing their respective customization levels.
The whole profession is like this. Why assume that this one thing, the General Droid Module Socket Cluster, is somehow a bug, and then not assume that putting a repair module in an R2 is a bug? They are both design flaws.
Ok, we have two sides of this discussion, let's examine them.
Side A (For using clusters in Droid Service Module Harnesses):
1. The interpretation that the description says it should fit: "This is an array that can fit a variety of droid sockets"
2. That the clustercan currently be placed in the Module Harness.
Side B (Against using clusters in Droid Service Module Harness):
1. There are two slots for modules, one is named "Droid Service Module Harness", the other is General Droid Module Socket Cluster". It doesn't take much common sense to see where the cluster is meant to be placed.
2. The normal modules are installed in a "Harness", whereas the description of the cluster states it can fit a wide variety of sockets. No where does it state that the cluster can fit in a wide variety of harnesses.
3. Using the cluster in just the "General Droid Module Socket Cluster" we have a natural progression of Droid capacity:
Modules Droid
1 MSE
1 DZ70
1 Power
1 ADV Power
1 R5
1 R4
1 Treadwell
2ADV MSE
2 ADV DZ70
2 ADV R5
2ADV Treadwell (WED)
2 LE Repair
2Surgical
2 Probot
2 ADV Protocol
3 ADV R4
3 ADV LE Repair
3 ADV Surgical
3 R2
3 R3
5 ADV R2
6 ADV R3
I think it's fairly easy to see where the cluster is supposed to fit. I do hope the Devs pick this issue up and fix it soon, and for the sake of those of you who have been using this bug I hope they don't make your old Droids non-functional in the process.
Ockale_MDE wrote:
1. There are two slots for modules, one is named "Droid Service Module Harness", the other is General Droid Module Socket Cluster". It doesn't take much common sense to see where the cluster is meant to be placed.
You're misreading it. Look at the R4. The name of the slot is "General Droid Module Socket (requires 1 Droid Service Module Harness)".
So how is it wrong to put a 'General Droid Module Socket Cluster', which fits into a 'variety' of slots, into a 'General Droid Module Socket'?
This is no different than stacking level 4 item storage modules.