Droid Engineer Archive
Thread: Droid Report: Droid Reconstruction Kits unusable by non-DEs (info from Devs)
Slothrop27 wrote:
This just seems like another paradox for the droid engineer. So instead of using a droid wound pack you either
need to come to a DE to repair your droid for you, or find someone who has a Repair Droid with a working repair
module, considering it's impossible to have 2 droids out at one time.
How can a sentence like this: "These kits were put in to address the problem of Droid Engineers not being able to repair their own droids because they could have only one droid out at a time," actually be used to explain anything!!??
This sounds like a major pain for all non-DE's. I wish the DEVs would realize that their explaination
makes no sense at all.
Again this begs the question, is there anyone out there in DEV-land that A. has a droid in-game, or B. has walked
one day in a DE's shoes....
Well it makes perfect sense to me. In the past the public could have droids repaired by a DE with a repair droid, or by anyone else who owned a repair droid. In that respect nothing has changed for the public.
The DE issue was: we, the engineers, had no way to repair our own droids, which since we made them in the first place made no sense. In respose to this we asked could an MDE have 2 droids out at once please, only 1 combat but also 1 utility (repair) so that we can repair our own droids. Devs did not want to allow that, so they created these Kits for a DE to use themselves.
It makes sense, and it also means repair modules in a droidwill sell to customers. I really dont see whats wrong with this as a compromise.
Slothrop27 wrote:
The trouble I have is this, why would repair modules in droids now sell to customers? For them to heal other people's
droids? I think people want to heal their own droids, not the droids of other people. If no one in the game can call
two droids at once then this means no one in the game can use their repair droid for any other purpose than to heal
droids that are not their own.
I'm warming up to the idea of people coming to me in order to have their droid's wounds healed. But it still sounds
like a major pain for any non-DE's, as well as rendering commerically useless all droid wound packs, and by and large,
repair droids in general.
Maybe I'm wrong, but I just don't see customers buying repair driods for the sole purpose of healing others. Who knows
tho, maybe the gaming community will like that idea. I'd like your thoughs on this....
Pallida wrote:
ONLY in gaming do I see a tendency for peeps to want to become John Rambo... and by doing so, defy ALL known and accepted military strategies.
Hehehe...exactly.
I can just see it...."What about me and my uber R3 up against 5 Stormtroopers?!? I win!!"
Not.
Nothing has changed for regular players, as far as how they heal/repair wounds on droid HAM. Nothing.
/bow
Respectfully,
Slothrop27 wrote:
The trouble I have is this, why would repair modules in droids now sell to customers? For them to heal other people's
droids? I think people want to heal their own droids, not the droids of other people. If no one in the game can call
two droids at once then this means no one in the game can use their repair droid for any other purpose than to heal
droids that are not their own.
I'm warming up to the idea of people coming to me in order to have their droid's wounds healed. But it still sounds
like a major pain for any non-DE's, as well as rendering commerically useless all droid wound packs, and by and large,
repair droids in general.
Maybe I'm wrong, but I just don't see customers buying repair driods for the sole purpose of healing others. Who knows
tho, maybe the gaming community will like that idea. I'd like your thoughs on this....
Jenden wrote:
Slothrop27 wrote:
The trouble I have is this, why would repair modules in droids now sell to customers? For them to heal other people's
droids? I think people want to heal their own droids, not the droids of other people. If no one in the game can call
two droids at once then this means no one in the game can use their repair droid for any other purpose than to heal
droids that are not their own.
I'm warming up to the idea of people coming to me in order to have their droid's wounds healed. But it still sounds
like a major pain for any non-DE's, as well as rendering commerically useless all droid wound packs, and by and large,
repair droids in general.
Maybe I'm wrong, but I just don't see customers buying repair driods for the sole purpose of healing others. Who knows
tho, maybe the gaming community will like that idea. I'd like your thoughs on this....
A I've had a lot of people get droids with repair modules, generally either so they can repair friend's droids on hunts or they can transfer the repair droid to someone else whenever they need their droid healed.
Ya know, that info is on the tooltip window.
I have to get a friend's droid wounded and try it out, curious to see if the camp/city location usage restriction can be overridden by use of a medical droid.
about the practicality of the repair droids and the frequency by which they are used by people to heal
the droids of others, but from what you're saying I'm encouraged that these repair droids are put to
good use.
Does anyone have any info on how much wound damage a repair droid with a good repair module can heal?
Maybe they could just add Droid "Hosptials", or Droid "Repair Garages". Oh wouldn't that be a rocking idea.
Ho....
This shouldn't matter. Droid Repair modules should heal all droid black wounds in one repair command (regardless of the amount).
Slothrop27 wrote:
Does anyone have any info on how much wound damage a repair droid with a good repair module can heal?
/bow
Respectfully,
Fair is that we don't write the code or make the final decisions, TK.
It's not the player's fault that the idea SOE had recently for placing higher-level player combat droids into the game wasn't a workable one. Sounded to me like it got shot down from inside SOE as much as by the DE community and players in general.
The decision might have been based on our input but we did not make the decision. Hell, if they don't want ideas shot down they shouldn't send them out in board daylight in an unarmored glider, heh.
We've never heard about:
1) What the original plan was to add such high-level combat droids (suspect certs were involved).
2) What the 'Mission Statement' is for the DE profession. NO In Concept thread for us.
So I'm being perfectly fair and logical as far as I can see.
If it doesn't look very good then I think that's SOE's fault not mine, eh?
/bow
Kilarny wrote:
Fair is that we don't write the code or make the final decisions, TK.
Man, I have to say, I think this would be a really bad idea (but I think I know what you meant). The last people that really should be "developing" software are the people that actually code it and the end-users themselves. There usually has to be a middle-man that can work as a go-between.
That's my personal experience, anyway.
It's not the player's fault that the idea SOE had recently for placing higher-level player combat droids into the game wasn't a workable one.
Actually, it was workable. For balance, using a new profession to 'get there' was (as they have said) the best option in theireyes. We said no. They pulled the plug on it. That's what went down, Kilarny.
Sounded to me like it got shot down from inside SOE as much as by the DE community and players in general.
Then, on this point you'd be partially incorrect (we shot the down, the Devs just sort of agreed that a metallic CH wasn't really what they had envisioned as the "best" solution either). If we'd have welcomed DH with open arms, we'd likely be playing it now or soon. That's the reality, as I can see it now...
The decision might have been based on our input but we did not make the decision. Hell, if they don't want ideas shot down they shouldn't send them out in board daylight in an unarmored glider, heh.
We've never heard about:
1) What the original plan was to add such high-level combat droids (suspect certs were involved).
2) What the 'Mission Statement' is for the DE profession. NO In Concept thread for us.
So I'm being perfectly fair and logical as far as I can see.
If it doesn't look very good then I think that's SOE's fault not mine, eh?
Okay..we are totally off-topic on this now...and I don't think it's going to do any good to beat this set of horse's bones.
Can we just agree to look forward?
Respectfully,
That makes sense, but its pretty lame actually.
We complain that the repair module isn't usable because you can't use it to repair your own droids and they respond be giving us a new kit that does the same thing as the repair module. I'm glad I can repair my droids, but that "solution" completely misses the point of the problem it is suppossedly adressing.
The repair module is still useless.
TheRealTK421 wrote:
/bow
Kilarny wrote:
Fair is that we don't write the code or make the final decisions, TK.
Man, I have to say, I think this would be a really bad idea (but I think I know what you meant). The last people that really should be "developing" software are the people that actually code it and the end-users themselves. There usually has to be a middle-man that can work as a go-between.
That's my personal experience, anyway.
Yes, they are called game designers. Don't have to be able to write the code, but you do have to know how it works. The 'middle-man' should know everything about the game system. It is the combination of the GM (gamemaster) and an Industrial Engineer.
I'm not sure there IS one for SWG, somebody whose sole focus is gameplay.
It's not the player's fault that the idea SOE had recently for placing higher-level player combat droids into the game wasn't a workable one.
Actually, it was workable. For balance, using a new profession to 'get there' was (as they have said) the best option in theireyes. We said no. They pulled the plug on it. That's what went down, Kilarny.
Sounded to me like it got shot down from inside SOE as much as by the DE community and players in general.
Then, on this point you'd be partially incorrect (we shot the down, the Devs just sort of agreed that a metallic CH wasn't really what they had envisioned as the "best" solution either). If we'd have welcomed DH with open arms, we'd likely be playing it now or soon. That's the reality, as I can see it now...
If it wasn't the "best" solution, and there WASN'T a "best" solution, then that's a game design problem. If everything SOE has communicated on the DH issue has been correct, then they never should have considered the DH profession at all. See Runesabre's reasons for not doing DH.
The decision might have been based on our input but we did not make the decision. Hell, if they don't want ideas shot down they shouldn't send them out in board daylight in an unarmored glider, heh.
We've never heard about:
1) What the original plan was to add such high-level combat droids (suspect certs were involved).
2) What the 'Mission Statement' is for the DE profession. NO In Concept thread for us.
So I'm being perfectly fair and logical as far as I can see.
If it doesn't look very good then I think that's SOE's fault not mine, eh?
Okay..we are totally off-topic on this now...and I don't think it's going to do any good to beat this set of horse's bones.
The horse is not dead - it's just wounded. I think if we whip it some more it will get back up. In plain English, the answers we needed yesterday are the same ones we need today. No dead horses are involved.
Can we just agree to look forward?
NO! The thread is MINE!
We are trying to look forward but haveonce again no information on Publish 8. I would be happy to look forward if I had something to look AT.
Respectfully,
/bow
I know you are trying to do a good job here, but we're still getting the mushroom treatment.