Droid Engineer Archive
Thread: Droid Condition Decay Necessary for DE Economic Health
On Vitality/decay rates and such...
Arcid wrote:
Daker-Naritus wrote:
Hey, just a thought...
It sounds like droid armor now wears out in the next patch... If droid armor wears out, that means that your droid becomes much less effective and will need to be replaced, right?
Actually I think it's that Droid armour is technically supposed to wear out currently, and so we're getting new, lighter armour that doesn't wear out next publish
Correct. That is 'the deal' with the new droid armor exactly.
I tend to agree that there needs to be a way to turnover droids based on use. How many times have we all seen a droid a player is using have 100% condition when it's doing its thing. That's like 99% of the droids I see. My poor R2 DoughBot's Repair module rarely gets used...
I'm kind of thinking that decay should be possibly linked to battery use (i.e. use of X batteries decays the Vitality by X amount). This means that all droids would have the same decay baseline. However, it might well be possible that the quality of the batteries would be linked to the decay rate.
The main issue at hand, however, is that we need to ensure that there isn't a 'buy once' market..
This is one of those things that I think we should keep an eye on as a higher priority for down the road but I don't know if it can be added now. Things are progressing in a pretty set way on both P7 and, from what I know so far, P8 as well.
More to come....the massive reading continues...
/bow
Respectfully,
Kollos wrote:
Good point, Malitevv.
But it could "decay" to the point that customization wouldn't stick, it could barely move, and Droid Batteries no longer worked.
true. but they would have to fix the fact that things like crafting stations don't require batteries. you can use the crafting stations in your *low power* droid for ever last I tried.
This is a good idea, although there is a hole in this as things currently are. A droid will eat batteries all day if you keep giving it batteries. If they implemented a check, where a droid would refuse a charge if it were "full", this is a good idea.
TheRealTK421 wrote:
I'm kind of thinking that decay should be possibly linked to battery use (i.e. use of X batteries decays the Vitality by X amount). This means that all droids would have the same decay baseline. However, it might well be possible that the quality of the batteries would be linked to the decay rate.
ArdenStarmariner wrote:
Lot of people feel that crafting failure rates go up alot when the droid is on low power.
Malitevv wrote:
A lot of people feel that way but there is no way any of them could tell the difference between a coincidence and a real connection unless they've done hundreds of controlled tests. and nobody, to my knowledge, has successfully dont that.
Thats a test I wouldn't be willing to touch with a ten meter pole. 
My suggestion ofon aCondition Decay system would be for it be linked to calling out the Droid. I wouldn't suggestion something as drastic as in the case of Customization, rather I would suggest that it be tied in with Vitality loss. For ever 10 times a Droid is called from the Datapad, it loses 1 point of Vitality. For every 20 points of Vitality loss, one random function is lost in the Droid. (IE Storage, Personality Chip, Armor, Crafting Station.) The Vitality can be healed as per normal, but once the Droid drops below 60% there is a chance that the Droid will be damaged beyond repairand become functionless, much like Armor or a Weapon that is rendered functionless if the repair roll fails. A system like this would allow for the most amount of turn over, yet at the same time would give the Droid owner some control over how fast their Droid wears out.
I like tieing it to battery use instead of calls for one reason: battery use is a better reflection of howmuch the droid has actually been used.
new droid owner are very likely to take their droid out and put it back away a few dozen times just to test how the system works. wouldn't it suck for them if that test caused it to decay? there is also the fact that bugs can cause the player to need to store and recall the droid because it got stuck on a graphical artifact or simply got lost because of a following error. but bugs won't cause it to accidentally eat a battery. :-)
Correct...that's why I prefer this.
Malitevv wrote:
I like tieing it to battery use instead of calls for one reason: battery use is a better reflection of howmuch the droid has actually been used.
Note: I've also brought up to the PTBs about those certain droid features that seem to work endless (No batteries required).
/bow
Respectfully,