Droid Engineer Archive

---

JFreeman wrote:

Yes, the top 5 issues (er... "top 3 issues" now?) reports are seen and read and discussed and occassionally even addressed.

This excercise is a little bit different than that: Taking inventory of the state of SWG features overall, with kind of a high level "This is broken, this is not broken, and that's broken but it can be fixed pretty easily"-eye on things.

I can appreciate the difficulty in separating what we consider critical vs. what you'd consider critical, but that's why I'm turning to the correspondents and community here: I more interested in what YOU think is critical now.

If it's wildly different than what we think is critical, then I'll pop in here and talk to you about it, so we can figure out why we're not on the same page.

---

i am just a simple evil dark jedi but common sense would tell me that what your paying customers think is critical would probably be a good clue in keeping us happy...

i am not talking about total proffession revamps but hitting 5 things we see as critical in each patch that have been around for more than 6 months as an issue should probably be addressed. and if some things are for a future patch or will be covered by a major rework of a profession it would be nice to know in a general sort of way. no one is asking for details just an acknowledgement that a given thing IS a known issue and is being gone over for a future patch.

basically we report stuff and report stuff and report stuff and it is all met with stone dead silence. you guys have said you want to communicate better but we arent really seeing it.

Yea, the list I presented was in no particular order, and I did go into more detail in my official post about each issue.

---

Drashk wrote:

---

Jenden wrote:
Right now the posted one I've got contains:
armor
droid deed stat display
creature harvesting
trap throwing
experimentation
structure maintenance

---

If it was my choice, here is the order in which I would list, the list.

1. Droid Deed Display - Without the droid customer knowing what they are buying, nothing else matters. Every Droid Deed should give an exact listing of what the droid has installed, in a way that is easily understood by the droid user. Armor, Food, Clothing, Weapons, and Bio Engineered products all clearly list the stats of their goods, in a way that anyone can understand. This same design should also be applied to Droid usage. All Droid deeds should list the following, if applicable.
• Combat Damage - The Combat Rating is great for a DE to know, but is next to useless for the droid owner.
• Armor - The Armor Effectiveness needs to be listed on the Deed, for the customer to see.
• Item Storage - The number of items that can be stored in the droid needs to be shown, instead of a rating that only DEs understand.
• Detonation Rating - This number needs to be replaced with a Minimum / Maximum Damage output listing. This way, the customer can look at the deed and know 'exactly' how much damage the droid will produce.
• Structure Maintenance - This module should have information listed such as the number of structures it can service, and whether or not it can be used off world.
• I believe that all of the other modules are listing their functions correctly.
2. Droid Armor - The Armor resetting after the second call is a major issue. The difference between a Droid with 1217 Armor, which seems to be the default for all CL30 Droids, and 9000, which can be achieved with in a 'maxed out' combat droid.
3. Experimentation - The Droid Experimentation system has become extremely gimped. Damage and Health are solely based on the CL of the droid. This has created an issue where every droid can easily have the max stats, regardless of the actual droid type.
4. Anything / Everything else....

I feel that these 3 issues are the top DE issues, that need to be addressed before anything else can happen.

Just an FYI, I am in the process of completely revamping the Centralized Droid Issues thread. When completed, it should be the most comprehensive list of all Droid and Droid Engineer related issues.

---

Armor bug is still definitely #1 for me. See, the deed display thing can easily be worked around. Just make a good description of the product before putting it on your vendor. It's not a critical thing to fix in my eyes.

I'll try to get you guys some more data on it. Not that it matters much to me anymore as I plan to cancel this account next week, but I would like to see it nailed down and fixed.

Unfortunately, for me, the "workaround" is to buy crafting stations and put those in my houses and just not use droids. But that's not the kind of "workaround" a DE should find acceptable

For the love of god can we get seeker droids on the list, I don't even want to know how many sales I lost from this.

Greetings JFreeman, a pleasure it is indeed to see you here. Welcome!

---

JFreeman wrote:

Yes, the top 5 issues (er... "top 3 issues" now?) reports are seen and read and discussed and occassionally even addressed.

This excercise is a little bit different than that: Taking inventory of the state of SWG features overall, with kind of a high level "This is broken, this is not broken, and that's broken but it can be fixed pretty easily"-eye on things.

I can appreciate the difficulty in separating what we consider critical vs. what you'd consider critical, but that's why I'm turning to the correspondents and community here: I more interested in what YOU think is critical now.

If it's wildly different than what we think is critical, then I'll pop in here and talk to you about it, so we can figure out why we're not on the same page.

---

Drashk wrote:

If it was my choice, here is the order in which I would list, the list.

1. Droid Deed Display - Without the droid customer knowing what they are buying, nothing else matters. Every Droid Deed should give an exact listing of what the droid has installed, in a way that is easily understood by the droid user. Armor, Food, Clothing, Weapons, and Bio Engineered products all clearly list the stats of their goods, in a way that anyone can understand. This same design should also be applied to Droid usage. All Droid deeds should list the following, if applicable.
   
   
   
   • Combat Damage - The Combat Rating is great for a DE to know, but is next to useless for the droid owner.
     
   • Armor - The Armor Effectiveness needs to be listed on the Deed, for the customer to see.
     
   • Item Storage - The number of items that can be stored in the droid needs to be shown, instead of a rating that only DEs understand.
     
   • Detonation Rating - This number needs to be replaced with a Minimum / Maximum Damage output listing. This way, the customer can look at the deed and know 'exactly' how much damage the droid will produce.
     
   • Structure Maintenance - This module should have information listed such as the number of structures it can service, and whether or not it can be used off world.
     
   • I believe that all of the other modules are listing their functions correctly.
   
   
2. Droid Armor - The Armor resetting after the second call is a major issue. The difference between a Droid with 1217 Armor, which seems to be the default for all CL30 Droids, and 9000, which can be achieved with in a 'maxed out' combat droid.
   
3. Experimentation - The Droid Experimentation system has become extremely gimped. Damage and Health are solely based on the CL of the droid. This has created an issue where every droid can easily have the max stats, regardless of the actual droid type.
   
4. Anything / Everything else....

I feel that these 3 issues are the top DE issues, that need to be addressed before anything else can happen.

Just an FYI, I am in the process of completely revamping the Centralized Droid Issues thread. When completed, it should be the most comprehensive list of all Droid and Droid Engineer related issues.

--------------------------------------------------------------------------------------------------------------------------------------------

So, I think I can agree with Drashk on this list, though to be honest the experimentation issue is so crucial I would probably place it first.....nomatter....3 is 3 in whatever order.

---

Jenden wrote:
Yea, the list I presented was in no particular order, and I did go into more detail in my official post about each issue.

---

Jenden, when you talked about experimentation, did you talk about it at the combat module level as well? That's a serious issue for me.

---

Gooners wrote:

ok the jedi heal bug. when we are in combat and we try and heal ourselfs we end up healing someone else or it comes up with you are not permitted to help that target, and this ends up with us being killed in pvp and in pve

---

What makes this post extra funny is that Gooners somehow got to Knight without knowing how to usea simple command like/forceheal self.

---

Drashk wrote:

---

Jenden wrote:
Right now the posted one I've got contains:
armor
droid deed stat display
creature harvesting
trap throwing
experimentation
structure maintenance

---

If it was my choice, here is the order in which I would list, the list.

1. Droid Deed Display - Without the droid customer knowing what they are buying, nothing else matters. Every Droid Deed should give an exact listing of what the droid has installed, in a way that is easily understood by the droid user. Armor, Food, Clothing, Weapons, and Bio Engineered products all clearly list the stats of their goods, in a way that anyone can understand. This same design should also be applied to Droid usage. All Droid deeds should list the following, if applicable.




• Combat Damage - The Combat Rating is great for a DE to know, but is next to useless for the droid owner.


• Armor - The Armor Effectiveness needs to be listed on the Deed, for the customer to see.


• Item Storage - The number of items that can be stored in the droid needs to be shown, instead of a rating that only DEs understand.


• Detonation Rating - This number needs to be replaced with a Minimum / Maximum Damage output listing. This way, the customer can look at the deed and know 'exactly' how much damage the droid will produce.


• Structure Maintenance - This module should have information listed such as the number of structures it can service, and whether or not it can be used off world.


• I believe that all of the other modules are listing their functions correctly.


2. Droid Armor - The Armor resetting after the second call is a major issue. The difference between a Droid with 1217 Armor, which seems to be the default for all CL30 Droids, and 9000, which can be achieved with in a 'maxed out' combat droid.


3. Experimentation - The Droid Experimentation system has become extremely gimped. Damage and Health are solely based on the CL of the droid. This has created an issue where every droid can easily have the max stats, regardless of the actual droid type.


4. Anything / Everything else....

I feel that these 3 issues are the top DE issues, that need to be addressed before anything else can happen.

Just an FYI, I am in the process of completely revamping the Centralized Droid Issues thread. When completed, it should be the most comprehensive list of all Droid and Droid Engineer related issues.

---

Excellant Lists gentlemen, both of them. I would suggest two minor changes, Jenden, I would suggest you replace Structure Maintenance Modules, with borked/redundant modules, that way you also cover things like Stimpack dispensers. And Drashk, I would suggest that deeds need to display skills need to use a droid, I hate spending 20 minutes on a dancing Jawa unit only to find out the new owner is neither a dancer, nor a musician. But it makes people hesitant to buy a droid, simply because they are unsure if they can use it.

---

Qlint wrote:
I would suggest that deeds need to display skills need to use a droid

---

Excellent point. Just like weapons and armor, droid functions should also list who can and who can not use the function of the droid. The only module that may be a 'problem' would be the Stimpack Dispensor module, since it currently requires xx4x Medic to fill.

---

Straker_Atrella wrote:

---

Jenden wrote:
Yea, the list I presented was in no particular order, and I did go into more detail in my official post about each issue.

---

Jenden, when you talked about experimentation, did you talk about it at the combat module level as well? That's a serious issue for me.

---

I did experimentation in general, and did mention combat in specific (though that was mainly listed as an inbetween case, where its got an "on or off" type experimentation system).

Since the publish that screwed up droid crafting, I think i've loggeed in 4 times, mostly to just re-list stuff on my venders that didn't sell in a month. In that time I only made like two droids. I just don't have the heart to make any more that could be rendered useless by a new patch.