Droid Engineer Archive

This is why we have discussions, and bug lists, and FAQs, and manuals, etc. So everyone can be on the same page.

What exploit?

Hiding items in droids to avoid the crackdown?

It makes sense to me...why should only Smugglers benefit? Still, you know all the whining is just going to get yet another droid module 'fixed' - in the 'neutered' sense of the word.

Wepps, just so you know that is not what they are talking about. They are talking about putting socket clusters(3 modules) into a slot that should only take one. Thus you could put infinite amounts of modules into a droid(theoretically). It was a huge debate that should have ended a long time ago. Please dont post again anyone. Its over. Done.

Message Edited by Ackis on 02-13-2004 10:27 AM

Uhhh at least I think.I guess Im not sure about that, I wouldnt want to sound dumb correcting you on that, if I was accually wrong, but the Socket Cluster reffered to in the original post is unrelated to the smuggler and ip crackdown.

No, the socket cluster bug was a rather hot issue here that has now been fixed. It has nothing to do with Smugglers or the Imperial Crackdown at all, other than the fact that it was fixed in patch 6.

---

Ackis wrote:

Those who read the forums and continue to use it are the exploiters.

---

---

Ackis wrote:

I have to say my posts after the patch about this issue have been less passionate than before the patch because it has been fixed. A lot of people who don't read the forums did not know this was an exploit. They were using the exploit, but they weren't exploiters. Those who read the forums and continue to use it are the exploiters. Now, a lot of DEs who didn't know about this are coming onto the forums trying to find out what's going on. Fair enough. I don't think this issue will drop anytime soon... at least until the word spreads to all the DEs out there.

---

See Ackis, this is exactly the problem. This was never "officially" and exploit. Something can't be an exploit until it's officially labelled a bug. Even in the patch notes, they never stated that putting clusters in non-cluster slots was a bug, they just said that stacking clusters was a bug. The DE community cannot declare anything a bug or an exploit. We can just identify suspected bugs and exploits. Anyone who stacked a cluster after reading the TC patch notesconfirming that it was a bug did exploit the bug. Since the patch notes NEVER stated that clusters into generals was a bug, and since you can't do it now anyway, this was never an exploit since it has never to this day been identified as a bug. I could just as well say that the ability to not place them into general sockets today is a bug caused by the last patch, right?

The simple truth is that we need to let this die. It was never really an important issue anyway. Who cares if you can build a MSE with all the modules in it? It's not like they do much anyway, right?

---

GnomeAd wrote:

See Ackis, this is exactly the problem. This was never "officially" and exploit. Something can't be an exploit until it's officially labelled a bug. Even in the patch notes, they never stated that putting clusters in non-cluster slots was a bug, they just said that stacking clusters was a bug. The DE community cannot declare anything a bug or an exploit. We can just identify suspected bugs and exploits. Anyone who stacked a cluster after reading the TC patch notesconfirming that it was a bug did exploit the bug. Since the patch notes NEVER stated that clusters into generals was a bug, and since you can't do it now anyway, this was never an exploit since it has never to this day been identified as a bug. I could just as well say that the ability to not place them into general sockets today is a bug caused by the last patch, right?

The simple truth is that we need to let this die. It was never really an important issue anyway. Who cares if you can build a MSE with all the modules in it? It's not like they do much anyway, right?

---

---

Kollos wrote:

You are correct that this just needs to die. However, it was very clear all along that the only reason clusters could be stacked was due to a bug that allowed clusters to be placed in standard module slots. The Devs that posted about the subject chose poorly phrased explanations, but the true issue was always very clear.

Stacking of cluster modules was never really the issue, that's just how people phrased it. The issue was ALWAYS the ability to place cluster modules in general module sockets - stacking clusters was simply a side effect of that issue.

---

I think that the fact that we have had so many heated discussions over this matter disproves your assumption that "it was very clear". It might have been clear to you, but we can't assume that it was clear to everyone. AsI said, the fact that we've been debating it so long makes it clear that reasonable people can disagree this. It's over and done and the only window of "exploiting" was so small as to not make it worth talking about. If anyone has a droid made like this, good for them. At least it's a little more useful than most other droids. At this point, it's like calling a pre-nerf probot an "exploit". Just because you could do something before and can't now, doesn't mean it was an exploit. It just means that you can't make them anymore.