Droid Engineer Archive

Since my other thread didn't seem to get much attention, I figured I would start one with a more descriptive title. I just feel like everyone should know exactly what the current situation is... beyond the myriad of 'bugs' that plague this profession. As it stands, a single MSE Mouse Droid can curently be constructed possessing every Droid Module possible. This is possible because you can currently use a General Droid Module Socket Cluster in any open General Service Module slot. Therefore, you can create several Socket Clusters and then simply 'EMBED' them all within other Socket Clusters. Ultimately creating 1 single Socket Cluster that contains all of the original Modules.

In other words, I could make one MSE Droid mouse that had within it the following (not sure if any of these stack, but if they do then things are even worse):

1. Unlimited # of Armor Modules (any level)

2. Unlimited # of Item Storage Modules (any level)

3. Unlimited # of Data Storage Modules (any level)

4. Unlimited # of Medical Modules (any level)

5. Droid Repair Module

6. All Crafting Station Modules

Yup... all of that contained within just 1 little bitty MSE Mouse Droid. Now you see the problem?

yes, I see the problem.

you'd have one completely worthless droid. That doesn't work. you go ahead and imbed like that, any cluster imbedded within a cluster bugs, and stomps functioing

Then I can only assume that you haven't actually done this. See... I HAVE done it... and trust me, it works just fine. The only thing(s) that don't work are the multiple crafting stations, but that's a separate issue entirely.

Umm... whats the exploit? Lets say we have 1 of every module and 1 crafting station... in an mse droid. You now have an mse droid that can do lots of stuff. How you are you going to charge for it? I see nothing wrong with this because it really isn't game breaking. Not to mention I vaguely remember reading in one post that sometimes med mods, data mods, and storage mods don't always play nice together. I also know you can't put a repair module in a power droid because the repair module doesn't work( sucks eh).

Also remember pathing on floating droids is better so sell DZ70s telling them the pathing is better.

So... the only reason any other droids exists (except for Mouse and Probots) is because they have a different appearance? Seriously, if this situation doesn't bother you, then maybe you don't realize that as things are right now, every other droid out there has no reason to exist except for their appearance.Maybe some of you think that alone is enough reason that they should be a part of the game, but I can't share that sentiment, sorry.

The point is that droids don't have any differences besides appearence and I treat it that way. Customers even tell me the only reason they'd buy a better droid is because it looks cooler. Bringing up what you've found with general module sockets won't change that. All that will happen is allow general module sockets to not be put into each other. Right now what you have said isn't an exploit because it adds no game breaking benefit because most of the stuff doesn't work. Even when it does work the only thing that will be useful is just having multiple modules. That is an easy fix... but still having nearly all modules in a droid isn't game breaking. It just means we charge more. What they can do is have each droid have a special ability(like a power droid) and then limit the number of modules that can be in there and/or take out the stacking of module clusters.

But Ratape, the devs themselves have stressed the desire to remain true to the continuity of the Star Wars mythology. If that is so then I suggest that droids have VERY specific things that they can do, as most droids were really good at one thing, with a few secondary skills. R2's are astomechs who can fly and repair starfighters and transports. R5 units are argomechs with limited utility as astromechs. Treadwell droids were built with certain models being utilized in different repair fields. Protocol droids were utilized in differing situations, some programmed for military, some for civilian.

As a DE, I'd like to see certain droids capable of certain functions, making neccesary to purchase those droids that are specialized in that field.

David, I couldn't agree more. Most my arguments were on the basis of how things are now.

ah, so it worked for you. nice. i've tried it many times. it never worked completely. always bugged. and no, i'm not talking about the crafting stations.

---

Jabetha wrote:

1. Unlimited # of Armor Modules (any level)

2. Unlimited # of Item Storage Modules (any level)

3. Unlimited # of Data Storage Modules (any level)

4. Unlimited # of Medical Modules (any level)

5. Droid Repair Module

6. All Crafting Station Modules

Yup... all of that contained within just 1 little bitty MSE Mouse Droid. Now you see the problem?

---

Although it could be a problem, right now I really don't see a problem:

1. That's the DEFENSIVE module socket slot, notthe GENERAL module socket slot, so it shouldn't take a Cluster. Even if it does, the Advanced Probot, prenerf will show that multiple armor modules make no difference, and in fact can even reduce effectiveness.

2. Item storage is broken. Who knows what this would actually do to capacity if it worked?

3. Data storage is broken. See (2).

4. Doesn't matter, you'd still be limited by the power of the medic actually doing the healing.

5. One repair module does it all in one shot. Ten isn't going to change anything.

6. Multiple crafting stations are broken.

Geeze, I guess that sums up the sorry state of our profession, eh?

Mendel

Very well put Mendel, there you are Sintrosi, I guess the exploit back fired only to show you that once again DE has become the ultimately mentally challenged proffession in game....wow...we are rock guys..

For crying out loud, STOP SPAMMING THIS.

This is at least the third time I've seen it.

First, the modules don't stack (i.e. 10 medic modules don't function any different then one).

Second, multiple crafting stations don't work in the same droid.

Third, most of these are broken anyway.

I would hazzard a guess that this is fixed with the module fixes.

This isn't a SERIOUS exploit.

It's a /bug.

/bug it, e-mail it to the CSR that handles exploits, and move on.

Audio

Well... if you or anyone else doesn't consider that fact that EVERY single droid we can possibly make (except for DZ-70 and Probots) are reduced to nothing more than 'eye candy' as a result of this, then I guess it isn't as serious as I thought. But, I for one find it extremely disappointing that EVERY single droid we can possibly ever make (R5, R4, R3, R2, Surgical, LE Repair, BLL, Protocol, Treadwell, etc.) exist in this game for NO reason whatsoever except for whatever graphic they present to the public.

It truly amazaes me that more actual DE don't seem really bothered by this. Dismissing it as a non-issue merely because the vast majority of our modules are broken is not a real counter-argument btw... if anything it only highlights the true 'pathetic-ness' of this profession.