Droid Engineer Archive

---

Drashk wrote:
GnomeAd, if it wasn't a bug then you should be able to place general modules into cluster module sockets.

---

Nope, sorry. That doesn't quite follow. Just because you can put GDMSCs into other slots has no bearing on why you can't put other modules into GDMSC specific slots. They are different types of modules.

Since the GDMSC is a separate schematic that you get for a specific skill level, the purpose of it just might be that it will let you place more modules in your droids, instead of what we all assumed. It actually makes better sense this way. Why require me to learn this skill box just to be able to make an R2/R3 droid? Don't forget that the non-advanced R2 only takes clusters. While we probably all agree that we don't want it to be this way, that doesn't mean that it wasn't designed this way.

NO, it does NOT make sense that way, GnomeAd.

It's been done to death here, but I'll say it again: An Advanced R4 is the best droid if you're correct, but an advanced R3 is the best droid if I'm correct. That cannot be right.

---

Kollos wrote:

Clear enough for you now? Or shall I do the same comparison with a MSE droid and an R3?

---

Kollos, this argument has been clear to me all along. Please understand that I don't really want the GDMSC to be able to be placed in non-GDMSC slots. I'm not arguing the point of it being a good or a bad thing. I'm arguing the point of is it a bug or a bad design. I don't think any of us think we should be able to do this. However, the devs have shown us over and over again that they have a different idea as to what we should be doing than we do.

Added general module slot to the advanced Binary Load lifter droid, and both basic and advanced protocol droids.

Droid storage compartments are now using droid experimentation rather than artisan.

Droid customization tool now gives droid crafting xp instead of general xp

Droid socket modules can no longer be plugged into one another.

Multi-crafting station module droid capability fixed for some cases where one type would over-ride another type.

Combat-related stats removed from examine windows for non-combat-capable droids

Item Storage Module 2's now really are that, instead of becoming data storage module 2's during the crafting process.

It seems like a whole lot of nothing. They are bug fixes. Im happy for that. Id like some of the move obvious crafting bugs to be fixed. storage modules in surgicals, droid repair tools, experimintation having meaning. I cant say I care what gives droid crafting exp. Ive been maxxed since August.

Good riddance to the socket cluster bug tho! I'll be happy to see that go. Its worth the publish all on its own.

I DO agree with your conclusionsKollos, but the only problem with your R2 vs. R3 argument is that there are LOTS of droids in the tree that have less functionality than droids that are further down in the tree.

Harder to build droids that are higer up in the skill tree, but areless functional than easier to build droids, are more common than the other way around at this point. sadly.

Though I agree with your conclusions, argueing along those lines doesn't demonstrate much since finding a droid higher up in the skill tree that is better than the droids lower in the skill tree is the exception, not the rule. Now I will cry.

Sody, this is on the list of concerns that I gave TH when he posted this snipet. I'm really not expecting any feedback about my concern list any time soon, since there are a ton of other issues that he has to deal with right now.I don't think its so much a matter of TH not knowning the difference, I think its a matter of how the patch items are written before TH gets a hold of them to put together for the general public.

As soon as this code hits TC I'll be logging in and will give everyone an update.It might take a little bit, since the first thing that I plan on building is an Advanced BLL with at least a Storage module, so that I can say that my BLL actually can carry something for once.

---

GnomeAd wrote:

However, the devs have shown us over and over again that they have a different idea as to what we should be doing than we do.

---

Yeah, Kollos used to call people exploiters back before we found out module stacking was perfectly legal. That's unfortunate I think.

Malitevv,

You raise a valid point about some higher-end droids (protocols, for example) having fewer (or no!) module sockets as compared with relatively lower-end droids.

But I believe that by staying within the R* family of astromech droids when making these comparisons, you can avoid that problem, and there is a VERY clear and obvious progression from low-end to high-end in terms of the number of available sockets.

LOL

If De's were the main focus/priority for the next upcoming patch where professions were getting a upgrade, I feel sorry for the rest of the others. I understand some changes cant be done overnight but to have fixes for bugs as only safe thing they can announce and even those fixes are not 100% guaranteed

well i am glad i dont put much weight into being a MDE and play more for other aspects, one could get depressed waiting for DE improvements in this game.

---

Droid_Engineer_Rho wrote:

But I believe that by staying within the R* family of astromech droids when making these comparisons, you can avoid that problem, and there is a VERY clear and obvious progression from low-end to high-end in terms of the number of available sockets.

---

Rho, I agree with this 110.5%, especially since clusters shouldn't go into clusters and the high end droids only have cluster slots.

However, the stated definition on a cluster is also VERY clear so its VERY clear to me that this is ambiguous and in all fairness should be resolved by the devs. Its a very basic tenent of term construction that you don't construe language so as to render parts of what you are interpreting as meaningless.

not that im sad about these mind you, just they take forever to correct bugs from day 1...err i mean day 2. i mean beta...oh nevermind.

Underwhelming.