Droid Engineer Archive

Dismissal - Please address the lack of confirmation - accidental dismissal is costly and aggrivating

From the initial description of what droids were intended for from the very beginning - Droids could be used as Vendors...

Additionally - if my "voiced opinion" matters at all, I would rather NOT see "BluePrints" sepparated out as mentioned in a previous post of arrangement by "Combat", "Component", "Experimentation", ect - I don't feel this would be a positive direction for the profession.

Thanks

Sintrosi, this is not a personal attack so please do not take it as one, perhaps my points where not clear as I am frustrated by the changes and I really want to play a Droid Engineer but am finding that it is not fun or rewarding in its current form. Many of the idea's I have seen are good idea's but I have seen poor implementation of fixing this class. Once again addressing the bigger picture (and by the way for the rest of you Surgical Droid is also available at skilllvl III and therefore of little use to people stuck crafting endless numbers of MSE's that no one will buy with a lvl 1 medical module in an MSE that does nothing for medic).

I did see how they addressed the XP issue thats my point they made a change and slammed us once again increasing the grind needed. If you think it is particularly fun and rewarding to make 1000's of droids for nothing by all means don't address the skill trees or XP needed for each and keep each skill tree on the same path. I have also sold crates of droid compartments to crafters that needed them for repair kits and private crating stations and the UXP did not move my Droid XP at all.

My point is that you covered it but did not do anything meaningful to correct the problem you only replaced one bad idea with another.

1. Different XP line for Refinement skill tree

2. Lower XP for advancement in Droid Production, Construction, and Refinement. (as it stands now DE grind to level IV Blueprints first and do little experimentation with other components as a result).

3. Increase the stats for DZ70 droids so that lower level DE's have something to sell. (45 point HAM Bars are insane considering what has to been done to get your first new blueprints, 150 HAM would at least be resonable and not overpowering for this droid).

4. Allow droids to be destroyed, C3-PO did not hold up all to well to a direct blast from a Stormtrooper in cloud city and R2 D2 took a direct hit and ddi not look all to well. We should be able to actually repair them and only DE repairs these droids. If the melee and combat types risk there droids then they need to seek out DE for repairs or carry addtional backup droids. All other classes have a Niche, the Entertainers heal mind and battle fatique, the medics heal wounds and stats, why then can anyone store a droid and as if by magic it is healed???

Point 4 has been discussed I know but I felt it need to be addressed again.

Thank You

Yadar

Not sure if this is a bug or intentional but I haven't seen it posted yet.

I've made a number of med-bots since they're really the only useful bot at the novice level. I can call the droid anywhere in the city and use my medical abilities to heal myself. However, the second I take myself and the droid inside a cantina, I loose this ability and receive the message that "this can only be done in a campsite, medical center, or near a surgical droid" This is mainly refering to /tendwounds as stims and other medipaks work just fine in the cantina's. If this ability is going to be limited this way then why not restrict the cantina's to only mindwound and bf healing. As it stands now a whole host of entertainers can dance and play all day / all night with just a couple novice medics healing their action points over and over but I have to go outside to tend my own wounds.

Sthizve, I think this is as intended. If people could heal both med woundsand mind wounds in the cantina no one would ever go to the hospital.

On World persistence of droids, I'd vote for a somewhat less than permanent persistence. Maybe the droid is there as long as the character is logged in.

If they are truly like harvesters, there will be issues with droids all over town who's ownershave logged,or people simply not able to log out in a convienient place and time because they have their droids out.

What happens when there is now one else to teach....

I already know alot of people that are paying to be able to teach someone for the apprentence points.

I can see that I am going to have a problem since my universe is already full of Master Engineers and I am just now getting to Master Artisan BTW only 300 app points for Master artisan, for more than a week now......

6k for an advanced probe heheh good lord in the time it takes to get the resources and construct one I could make 10k doing destroy missions. The day droids sell for that on my server is the day I stop bothering to sell them. Given how much cash there is in the system selling one for 6k is basically saying your product has no value. Heck basic pistols sell for minimum 8k and require far less resources and messing around than an advanced probe.

Kaid

I'd love to see MstrArtsn's MTBF (mean time before failure) idea implemented for droid parts.

Once the MTBF "hit points" fall below 0 that part fails and the droid needs to be brought to a Droid Engineer for proper repair. Maybe you need a Binary Load Lifter to go out and pick it up? Or take your Repair Droid into the field where the droid broke down?

Add some smoke animation to failed droids...

I am going to buy a binary load lifter. I think those are awsome.

The probots...Why does everyone cry? The DEVs will fix it, eventually. Just have patience, such as how we all waited for this game for how long, 3-4 years, if I am correct.

I think the lack of Dev response should be on the list.

Sintrosi,

Thanks for the all the hard work you've done so far with the DE Correspondent role.

You appear to be well on top of things and I have every confidence that your input and attention will help us all to build better useless droids.

Now....I've read all the official 'top issues' lists and I've not seen this little gem put up yet.

So, here's my first official entry into the fray:


Implement/fix the ability to call droid within "outposts" on Adv. Planets (Endor, etc.)

Currently, this particular aspect of droid use does not appear to function. CH's can call their pets while within an outpost's 'city limits', to the best of my knowledge. However, I am unable to currently call any existing droids while in an outpost. I believe that outposts should qualify as 'cities', for the purposes of calling forth a droid. As it stands right now, a DE and/or droid owner would only be able to call a droid on Endor, for example, while in a camp.

Thanks again for the hard work...

I'm for World persistent droids. Droids are free functioning intelligent beings in the Starwars Realm, and they should not need us to hold their hand. The only problem with this, is there is alot of potential for people to clog the world with droids everywhere.

Power level indicator just makes sense, and should have been originally implemented, and I can't believe it wasn't.

The fact that droids don't have a spot on the bazaar is ridiculous, we sell something very unique and hopefully will be something very useful.

I'm a droid engineer, and I barely know how my droids work. Documentation is a must.

Droid names, its pretty minor, but, I would definately rather see an MSE droid named M2 instead of something like "Puddles."

I also agree with the idea of better descriptions, because again, I'm at Droid Engineer and I barely know what my droids are capable of.

I haven't had a droid out long enough to have it lose power, so the length issue I can't comment on. But, the whole "let the droid recharge itself" is a little iffy...I mean, if they were in a house with a recharing station or something, that would make sense, R2 could roll up there and plug in. If you are hiking along though...the droid can't magically pull out a battery and recharge itself...I think this issue stems from laziness more than anything, but correct me if I'm wrong.

Dismiss confirmation makes sense, add some kind of better documentation on what droids do, and this will help eliminate the problem as well.

I saw someone mention Droid Powerups. That would definately be a reason for Droid Engineers to stay in business, and I"m all for that.

The previous problems that have been reported are much more important too me of course.

I have seen or heard problems that relate to all the bugs, and think all of them should be addressed.

Just my thoughts.