Droid Engineer Archive
Thread: YES to DH
Page 1 of 1
abe333
Sat Jan 24, 2004 6:16 pm
#1
I would like to point out that while most non-holo DEs currently seem to dislike the idea of DHs, it should be remembered that they picked the profession knowing that it was craft only at that time. DEs have been so broken for so long that most would never consider putting in the time to master the profession. SO, I am not sure that the number of potential DEs-to-be compared to the whiny current DEs are being considered by most. I think the DEVs are right on the money in considering a DH class...and I hope it goes hand in hand with the current DE tree. I suspect we would see a huge influx of DEs. As long as the combat droid use skills are at the top of the trees I think it will be a HUGE improvement over a DE craft only class.
Let the flaming commence....
LordKalibah
Sat Jan 24, 2004 6:19 pm
#2
the fact that DE cant personally use the droids isnt hte point. the point is for 1 .... that means a lot less people to sell the droids too... as only people with this extra skill set will be able to use the,...
Nelus
Sat Jan 24, 2004 6:23 pm
#3
i say yes to dh
all droids will be useable by everyone just the highlvcombatdroids which cant be given to players without skillpointcosts will be sold to DH, all other droids will be sold to everyone!
AudioOrgana
Sat Jan 24, 2004 6:23 pm
#4
Please post your opinion in the appropriate thread "In Development".
Coming here to announce this is nothing more than trolling.
Audio
abe333
Sat Jan 24, 2004 6:32 pm
#5
Sorry, meant to post this in the Droid Engineer forum....
wait, huh?.....
AudioOrgana
Sat Jan 24, 2004 6:46 pm
#6
abe333 wrote:
Sorry, meant to post this in the Droid Engineer forum....
wait, huh?.....
Yes, this is the DE forum.
Your posting is regarding a "DH" profession, not to mention insults this entire forum by calling current droid engineers "whiny".
This would be like them announcing a new "meat hook" combat profession and discussing it in the weaponsmith forums.
Finally, since you finish your posting with, "Let the flaming commence", you show that you knew full well what you were doing, and instead of directing your input at the appropriate thread you came here to create a reaction - this is the very definition of "troll".
So again, I ask you, to voice your opinion in the appropriate place. Right now, that is :
http://forums.station.sony.com/swg/board/message?board.id=Developers&message.id=21175
Audio
Sodan-droiddreamer
Sat Jan 24, 2004 6:52 pm
#7
Bullcrap. No.
Just 'causethe profession was broke to bgin with don't mean it has to stay that way. How come CHs can use pets AND tame them?
Nelus
Sat Jan 24, 2004 6:56 pm
#8
again, this was planned, than DEs screamed they dont want combat abilitys and thats why they go to a new profession.
Droid_Engineer_Rho
Sat Jan 24, 2004 7:01 pm
#9
Whiny?!? I can't imagine what there is to whine about...
2. Bugs still in evidence
A. Droids are not giving any UXP.
B. Droid names use the standard name filter. Droids should use a modified name filter that allows for numbers in the name.
C. Droids with no attack capabilities none the less have attack speeds and damage values in the datapad.
D. Droids often stop following without reason. This is a generic pet problem as it happens to all pets, not just droids. Pets seem to get stuck on invisible zone boundries. Walking up to about 10-20m from the pet and re-issuing a 'follow' command fixes it (most of the time).
E. Item Storage Module 2s come out as Data Module 2s during the assembly stage. What you seem to get at the end is a Data Module 2. This is only a NAME/ICON problem. The module is said to function as it should - as an Item Storage Module 2.
F. EXPLOIT: Cluster modules not only fit into cluster module sockets, they fit into service module sockets. This allows cluster modules to fit into cluster modules ad infinitum. Clusters should only fit in cluster sockets. Otherwise you're further exploiting the idea that the droid frame used is irrelevant.
G. Droid Customization skill only goes to +64 at Master.
H. Repair modules do not function at all when placed in the Power droid or any of the humanoid droids.
I. Medical modules affect the effectiveness of stimpacks. Reports say that a stimpack is more effective when a medical module-equipped droid is nowhere to be seen (unless it contains a level 6 module).
J. Some experimental values for droids and droid components are always 0% regardless of the resources used. If they're going to be always 0%, don't show them.
K. Droid deeds need to show ALL the modules installed and any important properties associated with those modules.
L. EXPLOIT: By telling a droid to stay, running 800m (need to cross a server zone?) or so away and calling another droid, you can effectively call all your droids at once.
M. Droid Storage Compartments use Artisan Experimentation instead of Droid Experimentation. It's a DE craft, it should use DE skills, not Artisan skills.
N. Item storage modules do not work with Surgical Droids (basic and advanced). The option to use item storage is not available in the radial menu.
O. Droid customization is borked. No xp is gained from colouring droids, the colours don't always hold (use the first white box to reproduce). R# units have random colours when they are first tamed and randomly change until the droid is customized. The number of colours available with the customization tool are different than the colours available during crafting. New droids are reported to not be customizable (certain frames perhaps?)
P. Droid customization tools give General Crafting xp instead of Droid Crafting xp when crafted.
Q. Droids suck batteries like there's no tomorrow ever since they no longer recharge on store. Please find a happy medium.
R. After calling or storing a droid, the datapad radial menu doesn't immediately update to reflect the status of the droid, causing the store item to appear after storing the droid. This seems to be a general radial menu problem with 'optional' items in the menu.
S. Armor resists sometimes degrade.The armor resist changes to a vulnerability and it isn't just visual.
T. Crates of droid batteries don't tell us how many charges the batteries in the crates have until you remove them from the crate. Buyer beware until this is fixed.
U. Converse style droids cannot be named.
V. Binary Load Lifters are useless beyond being walking signs or furniture.
W. Protocol droids (basic) are useless beyond being walking signs or furniture.
X. Enough with the 'tame' thing... let us 'activate' or simply 'use' the deeds to first create our droids.
Y. Experimentation on subcomponents has no effect on the final droid (see Drashk's experiment). Experimentation on modules also seems erratic at times. Mechanical ratings of modules have an effect on the mechanical rating of a cluster (as do brains with repair modules), but the effect seems unusual.
Z. EXPLOIT: BH droids can be exploited as to not use their final charge.
AA. Experimentation values for Effectiveness listed in the schematics for droid chassis' are wrong. They list SR/UT, but should be OQ.
AB. Complexity tapes no longer have any effect on the droid's complexity.
AC. Only the most recently deployed set of "crafting stations" works.
3. Uncertainties
A. Patrol point list is not saved between store and call, is this by design?
B. Power droids are the only droid with a non-modular function (ignoring combat capable droids here). Why not make it modular or give other droids inherrent functions?
C. Some of the advanced droids are using 'Converse' instead of 'Program' for programming. Nobody seems to know how to name these droids. Can it be done?
D. Droids cannot be called while inside a city building. I see no reason to prevent us from calling droids in a city. Shouldn't matter if we're in a building or not. If this is intended, then why?
E. Seeing several reports of 'broken' Medical modules. The modules break and remain broken even after recharging the droid.
4. Wishlist
A. Give us information on droid power levels in the examine window and/or in the datapad. Also, since droid batteries repair mind, how about using mind as the droid's power level indicator? The action pool would also work.
B. Examining droid should give the same data as in the datapad (for the owner).
C. We really want certain droids to only be able to take certain types of modules. There have been a number of really good posts on this topic, and due to space constraints, I'll leave it at that.
D. Consider droids that can survey and report back on a particular resource. Perhaps even a high-end version with the ability to go to other planets to determine which resources are available.
Ea. Consider droids that can help maintain installations. Send a droid out to pay mantenance. Send a droid out to collect resources. Send a droid out to deliver power. There are many ways to implement this as a viable system.
Eb. Another viable idea for this is to add droid chassis' as optional components in the harvester schematics. One optional slot for mediums and two for heavy harvesters. Allow for a power droid chassis to remove the power requirement at the cost of maintenance and extraction rate. A BLL might increase the extraction rate at the cost of power and maintenance. A repair droid might remove the maintenance requirement at the cost of power and extraction rate.
F. Consider droids that can act as standalone vendors in cities, and/or droids that can act as Barkers. Perhaps even let droids deliver goods to a customer in another city or on another planet.
G. Droids to remember if they were stored or called over a logout. Running around in the middle of nowhere and logging out causes your droid to hide back in the datapad. This means having to go back to town or putting down a camp in order to recall your droid. This is undesireable.
H. A DE equivalent to vitality packs would be nice.
I. Create a slicing module to boost smugglers' slicing ability.
J. Allow us to drop batteries into the droid's inventory and have it recharge itself as needed until the batteries run out.
K. Create an entertainment module akin to the existing medical module to allow entertainers to work ouside of camps, cantinas and hotels. This module would be also level 1-6 with each level giving a little extra boost to the entertainer's skill.
L. Saw a request for a training droid as seen in the movies that 'harasses' its target, pulling aggro. This idea is intended to give a little variety to the Novice DE's life. Could also be used as a consumable for training the combat classes.
M. Let us name our droids through the datapad controller. Droids shouldn't need to be 'taught' a name like pets do. The name is programmed into the droid separate from the other commands.
N. Add the creator to the droid view information, not just the owner. When you look at a pistol, you see who made it. When you look at a droid deed, you see who made it. When you look at a droid, you SHOULD see who made it.
O. Allow droids to be re-deeded for ease of transfer. Since we can only have 5 droids in the datapad, it makes it really tough for DE's to take old droids as trade-ins for upgrades (like a car). We either have to immediately re-sell the droid or delete it. Would make more sense to re-deed the droid so that it could be sold to another customer as a 'used droid'.
P. Droid "macros" came up. Let us create macro-like droid programs to have a droid execute a series of commands. Not sure how this would be implemented, but it is an idea.
Q. Make the droid deeds show pictures of the droid itself rather than a silly deed icon.
R. Make BLL Droids useful in 'city planning'. Let us use them to move buildings around without re-deeding. Great for once the player city expansion is released.
S. Please review the customization lifespan. 20 is too short. I have people complaining to me personally that they have to get their customization updated almost daily since they're always calling and storing their droid. I'm sorry, but if my car needed a new paint job because I took it out on the road 20 times, I'd be most displeased.
T. Weapon and armor components have modifiers to various properties of the final product. Do the same for droid components... like have the motive system affect the droid's speed.
U. Customization changes are only visible to the DE until set. Would be nice if everyone could see the changes so that the droid owner can decide if they like a particular colour before it is finalized.
V. Power droids should not require batteries. They're equipped with their own power core.
W. More colours for the protocol droid please... gold and gold is very limiting.
2. Bugs still in evidence
A. Droids are not giving any UXP.
B. Droid names use the standard name filter. Droids should use a modified name filter that allows for numbers in the name.
C. Droids with no attack capabilities none the less have attack speeds and damage values in the datapad.
D. Droids often stop following without reason. This is a generic pet problem as it happens to all pets, not just droids. Pets seem to get stuck on invisible zone boundries. Walking up to about 10-20m from the pet and re-issuing a 'follow' command fixes it (most of the time).
E. Item Storage Module 2s come out as Data Module 2s during the assembly stage. What you seem to get at the end is a Data Module 2. This is only a NAME/ICON problem. The module is said to function as it should - as an Item Storage Module 2.
F. EXPLOIT: Cluster modules not only fit into cluster module sockets, they fit into service module sockets. This allows cluster modules to fit into cluster modules ad infinitum. Clusters should only fit in cluster sockets. Otherwise you're further exploiting the idea that the droid frame used is irrelevant.
G. Droid Customization skill only goes to +64 at Master.
H. Repair modules do not function at all when placed in the Power droid or any of the humanoid droids.
I. Medical modules affect the effectiveness of stimpacks. Reports say that a stimpack is more effective when a medical module-equipped droid is nowhere to be seen (unless it contains a level 6 module).
J. Some experimental values for droids and droid components are always 0% regardless of the resources used. If they're going to be always 0%, don't show them.
K. Droid deeds need to show ALL the modules installed and any important properties associated with those modules.
L. EXPLOIT: By telling a droid to stay, running 800m (need to cross a server zone?) or so away and calling another droid, you can effectively call all your droids at once.
M. Droid Storage Compartments use Artisan Experimentation instead of Droid Experimentation. It's a DE craft, it should use DE skills, not Artisan skills.
N. Item storage modules do not work with Surgical Droids (basic and advanced). The option to use item storage is not available in the radial menu.
O. Droid customization is borked. No xp is gained from colouring droids, the colours don't always hold (use the first white box to reproduce). R# units have random colours when they are first tamed and randomly change until the droid is customized. The number of colours available with the customization tool are different than the colours available during crafting. New droids are reported to not be customizable (certain frames perhaps?)
P. Droid customization tools give General Crafting xp instead of Droid Crafting xp when crafted.
Q. Droids suck batteries like there's no tomorrow ever since they no longer recharge on store. Please find a happy medium.
R. After calling or storing a droid, the datapad radial menu doesn't immediately update to reflect the status of the droid, causing the store item to appear after storing the droid. This seems to be a general radial menu problem with 'optional' items in the menu.
S. Armor resists sometimes degrade.The armor resist changes to a vulnerability and it isn't just visual.
T. Crates of droid batteries don't tell us how many charges the batteries in the crates have until you remove them from the crate. Buyer beware until this is fixed.
U. Converse style droids cannot be named.
V. Binary Load Lifters are useless beyond being walking signs or furniture.
W. Protocol droids (basic) are useless beyond being walking signs or furniture.
X. Enough with the 'tame' thing... let us 'activate' or simply 'use' the deeds to first create our droids.
Y. Experimentation on subcomponents has no effect on the final droid (see Drashk's experiment). Experimentation on modules also seems erratic at times. Mechanical ratings of modules have an effect on the mechanical rating of a cluster (as do brains with repair modules), but the effect seems unusual.
Z. EXPLOIT: BH droids can be exploited as to not use their final charge.
AA. Experimentation values for Effectiveness listed in the schematics for droid chassis' are wrong. They list SR/UT, but should be OQ.
AB. Complexity tapes no longer have any effect on the droid's complexity.
AC. Only the most recently deployed set of "crafting stations" works.
3. Uncertainties
A. Patrol point list is not saved between store and call, is this by design?
B. Power droids are the only droid with a non-modular function (ignoring combat capable droids here). Why not make it modular or give other droids inherrent functions?
C. Some of the advanced droids are using 'Converse' instead of 'Program' for programming. Nobody seems to know how to name these droids. Can it be done?
D. Droids cannot be called while inside a city building. I see no reason to prevent us from calling droids in a city. Shouldn't matter if we're in a building or not. If this is intended, then why?
E. Seeing several reports of 'broken' Medical modules. The modules break and remain broken even after recharging the droid.
4. Wishlist
A. Give us information on droid power levels in the examine window and/or in the datapad. Also, since droid batteries repair mind, how about using mind as the droid's power level indicator? The action pool would also work.
B. Examining droid should give the same data as in the datapad (for the owner).
C. We really want certain droids to only be able to take certain types of modules. There have been a number of really good posts on this topic, and due to space constraints, I'll leave it at that.
D. Consider droids that can survey and report back on a particular resource. Perhaps even a high-end version with the ability to go to other planets to determine which resources are available.
Ea. Consider droids that can help maintain installations. Send a droid out to pay mantenance. Send a droid out to collect resources. Send a droid out to deliver power. There are many ways to implement this as a viable system.
Eb. Another viable idea for this is to add droid chassis' as optional components in the harvester schematics. One optional slot for mediums and two for heavy harvesters. Allow for a power droid chassis to remove the power requirement at the cost of maintenance and extraction rate. A BLL might increase the extraction rate at the cost of power and maintenance. A repair droid might remove the maintenance requirement at the cost of power and extraction rate.
F. Consider droids that can act as standalone vendors in cities, and/or droids that can act as Barkers. Perhaps even let droids deliver goods to a customer in another city or on another planet.
G. Droids to remember if they were stored or called over a logout. Running around in the middle of nowhere and logging out causes your droid to hide back in the datapad. This means having to go back to town or putting down a camp in order to recall your droid. This is undesireable.
H. A DE equivalent to vitality packs would be nice.
I. Create a slicing module to boost smugglers' slicing ability.
J. Allow us to drop batteries into the droid's inventory and have it recharge itself as needed until the batteries run out.
K. Create an entertainment module akin to the existing medical module to allow entertainers to work ouside of camps, cantinas and hotels. This module would be also level 1-6 with each level giving a little extra boost to the entertainer's skill.
L. Saw a request for a training droid as seen in the movies that 'harasses' its target, pulling aggro. This idea is intended to give a little variety to the Novice DE's life. Could also be used as a consumable for training the combat classes.
M. Let us name our droids through the datapad controller. Droids shouldn't need to be 'taught' a name like pets do. The name is programmed into the droid separate from the other commands.
N. Add the creator to the droid view information, not just the owner. When you look at a pistol, you see who made it. When you look at a droid deed, you see who made it. When you look at a droid, you SHOULD see who made it.
O. Allow droids to be re-deeded for ease of transfer. Since we can only have 5 droids in the datapad, it makes it really tough for DE's to take old droids as trade-ins for upgrades (like a car). We either have to immediately re-sell the droid or delete it. Would make more sense to re-deed the droid so that it could be sold to another customer as a 'used droid'.
P. Droid "macros" came up. Let us create macro-like droid programs to have a droid execute a series of commands. Not sure how this would be implemented, but it is an idea.
Q. Make the droid deeds show pictures of the droid itself rather than a silly deed icon.
R. Make BLL Droids useful in 'city planning'. Let us use them to move buildings around without re-deeding. Great for once the player city expansion is released.
S. Please review the customization lifespan. 20 is too short. I have people complaining to me personally that they have to get their customization updated almost daily since they're always calling and storing their droid. I'm sorry, but if my car needed a new paint job because I took it out on the road 20 times, I'd be most displeased.
T. Weapon and armor components have modifiers to various properties of the final product. Do the same for droid components... like have the motive system affect the droid's speed.
U. Customization changes are only visible to the DE until set. Would be nice if everyone could see the changes so that the droid owner can decide if they like a particular colour before it is finalized.
V. Power droids should not require batteries. They're equipped with their own power core.
W. More colours for the protocol droid please... gold and gold is very limiting.
Page 1 of 1