Droid Engineer Archive

---

TheRealTK421 wrote:

I need to take the temperature of the DEs a bit to see where the larger / smaller issues are currently.

---

1. Naming Humoid Droids

2. Deeds need to show Crafting stations

3. Surgical Droid Item Storage

4. Some kind of bonus for Master DE, ie more droids in datapad, another callable droid

5. We either need to be less reliable to Master Artisan Parts or more professions need to rely on us to build their products

§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
X Machine'Zed X
Obsidian Dagger Squadron

1. Battle Droids (Sodan's Proposal)

2. /examine details need to reflect ALL stats and modules as well as the deed prior to generation

3. Storage in Med Droids

4. 2 droids for MDEs, only one combat at a time tho.

5. The components for the repair kits require resources that are too specific (on my server ATM i can not make one of the components due to a slow spawn)

1.) un-nerf droid armor

2.) list all modules in the droid deed examine window

3.) more droid chasis

4.) allow BLL's to hold multiple stacking storage modules. Ths would give them a max of 30.

5.) fix remaining bugs

1. Feature change: We want the ability to have a droid out at the same time as a creature/faction pet. If it is impossible to allow this for combat droids for balance purposes, then do it for non-combat droids. Please implement a system that exempts droids which lack combat abilities from the "1 pet per player" rules. And please, if this is done, do it right and make is so that combat-capable droids that have no combat modules installed are classified as non-combat droids.


2. Bug: The conversational interface for talking droids is broken. This includes the fact that some of the more basic commands cannot even be trained (e.g., store and group), and the fact that these droids cannot be named.


3. Feature change: All abilities/stats of each droid component need to be displayed in the examine window. This includes droid deeds, cluster modules, etc.


4. Bug: Experimentation is useless on all of our components except for "all the new stuff", the level based modules, and the final deeds. Please bring it in line with other professions and make it so that experimentation really matters across the board in some consistent fashion. It is nice that it works properly on the new stuff (the repair kits, etc.) but in truth, this fact will make the profession even more inconsistent and confusing for newbies to the profession, if the old stuff isn't brought in line.


5. Feature change: We need one additional component that can fit into the armor module sockets. As it stands, because only one component type goes into these sockets, and all the best droids have two sockets, the high level armor modules are actually only needed for the low leveldroids (because on any high level droid two level 4's gives you max armor). Which is pretty darn silly if you think about it. If we had one more armor socket insertable component (a HAM augmentation component for example), then there would be meaningful tradeoffs to make when putting armor in our droids. As it stands, high level armor modules are pretty useless because of this issue, because very few customers care about the armor levels on the droids that take only one armor socket.

1. Feature change: We want the ability to have a droid out at the same time as a creature/faction pet. If it is impossible to allow this for combat droids for balance purposes, then do it for non-combat droids. Please implement a system that exempts droids which lack combat abilities from the "1 pet per player" rules. And please, if this is done, do it right and make is so that combat-capable droids that have no combat modules installed are classified as non-combat droids.


2. Bug: The conversational interface for talking droids is broken. This includes the fact that some of the more basic commands cannot even be trained (e.g., store and group), and the fact that these droids cannot be named.


3. Feature change: All abilities/stats of each droid component need to be displayed in the examine window. This includes droid deeds, cluster modules, etc.


4. Bug: Experimentation is useless on all of our components except for "all the new stuff", the level based modules, and the final deeds. Please bring it in line with other professions and make it so that experimentation really matters across the board in some consistent fashion. It is nice that it works properly on the new stuff (the repair kits, etc.) but in truth, this fact will make the profession even more inconsistent and confusing for newbies to the profession, if the old stuff isn't brought in line.


5. Feature change: We need one additional component that can fit into the armor module sockets. As it stands, because only one component type goes into these sockets, and all the best droids have two sockets, the high level armor modules are actually only needed for the low leveldroids (because on any high level droid two level 4's gives you max armor). Which is pretty darn silly if you think about it. If we had one more armor socket insertable component (a HAM augmentation component for example), then there would be meaningful tradeoffs to make when putting armor in our droids. As it stands, high level armor modules are pretty useless because of this issue, because very few customers care about the armor levels on the droids that take only one armor socket.

Bah - don't we have a bunch of SOE employees that are supposed to be keeping track of such things?

1) Answer: What is the purpose of the DE profession in the eyes of the SWG development team?

2) Answer: which 8 of the 10 top questions should be addressed by the release of Publish 7 and Publish 8?

3) BLL and 3PO droids == useless.

4) Power Droids need batteries. Come ON. I can run a house off a Power Core darn it!

5) DE is the only crafting class that makes such an optional product. Every other crafting class has checkers, they gave us some old broken dominoes instead.

1. Bug: Item storage doesn't work in surgical droids.

2. Bug: The droidsmith tool kit is virtually impossible to craft.

3. Bug: General Module socket clusterscan't fit in combat module socket cluster slots like they did pre-patch.

4. Feature change/add: All information about a droid needs to be shown when examining a deed.

5. Feature change/add: reduce complexity of droid combat modules

Edit: changed issue #5 since I knew it wasn't going to happen

Message Edited by JavelinCatcher on 04-02-2004 01:28 PM