Droid Engineer Archive
Thread: Droid Module Socket Clusters?
Im not sure I know exactly what this is, if my guess is correct it means you can put 3 modules into this cocket cluster then the socket cluster only takes one module slot but has 3 modules in it, am I right? So a probot could have potentially 6 modules instead of 2? I thought i heard someone saythat a probot with 6 modules was a exploit but If what I say here is correct then it is not an exploit at all!
Thanks for helping a DE noob, pretty much got everything figured out now except this.
I have a hard time accepting the term "exploit". Exploits get fixed. For months, the Devs didnt even know whether it was intended or not. It is now labeled as a bug. TH didnt say exploit, he could have. He didnt.
Still will be happy to see it go.
Actually, the term exploit is used to describe the use of a bug for ones own benefit. The issue itself is a bug; however the moment that it is used to stack modules or used in a droid that is not designed for a cluster module, it becomes an exploit. Think of the bug/exploit relationship as present and past tense verbs.
Lonkley wrote:
I have a hard time accepting the term "exploit". Exploits get fixed. For months, the Devs didnt even know whether it was intended or not. It is now labeled as a bug. TH didnt say exploit, he could have. He didnt.
Still will be happy to see it go
on an off note, i laughed last night because I tried to make an R3 w/ Item 6 and Food/Chem and I figured since the cluster works in general, a general should work in a cluster. Nope.
Id just never had anyone order an R3 with less than 3 modules before ![]()
I have a feeling that's the way it's 'supposed' to work. Intentionally hampering the final droid by putting a single module into a socket cluster would not bother me in the slightest. Someone just got their boolean logic wrong somewhere. This would allow any 0/0/0/3 DE to manufacture R2s with SOME level of function.
Oh im not saying it shouldnt be like that. I know thats the way its supposed to be.
I just find it funny that it actually worked that way. Its interesting to see how exactly its broken.
MachineZed wrote:
It is an exploit, TH said so. Although the Cluster fits into the General Module Socket. It was not meant to fit into the General Module Socket. It was meant to fit only in a General Module Cluster Socket
To be precise, what TH said was that stacking GDMSCs was a bug. He never addressed putting them in non-cluster sockets.
GnomeAd wrote:
To be precise, what TH said was that .........
*** /emotemumbles something inaudible under a gag ***
GnomeAd wrote:
MachineZed wrote:
It is an exploit, TH said so. Although the Cluster fits into the General Module Socket. It was not meant to fit into the General Module Socket. It was meant to fit only in a General Module Cluster Socket
To be precise, what TH said was that stacking GDMSCs was a bug. He never addressed putting them in non-cluster sockets.
Re-read the question that was posed and answered.
There's the part in the question "as well how they fit into a droid".