Droid Engineer Archive

Thread: Droid decay

Jeryld
Fri Sep 17, 2004 9:28 am
#1

I know there are a few threads about this already, but as none of them seem to be recent I thought I'd post this in a new thread.


Regardingthis, I think it would be really cool if instead of "Droid decay" droids suffered from "Component decay" - in other words , each time you pulled your droid out, there was a .05% chance (or whatever, possibly variable per type of component and droid) on each component that it fails. So you pull out your droid for the xth time, and it's motive system fails, so it can't move. To get it fixed, you take it to a DE who has to replace that component to get the droid functional again. Or possibly makes you a part exchange offer that you just can't refuse.....(would be nice to be able to salvage droid partstoo )


I think this would really add to the "feel" of droids and make the DE profession even more fun...I realise the dev's have other priorities atm and will probably be a fair old while before the re-visit DE's again, but we can but hope.....
Jjiaah
Fri Sep 17, 2004 2:28 pm
#2

While an innovative idea, this would end up requiring way too much database space unfortunately. The servers would need to keep track of each and every module in the droid and if it was functioning or not, instead of just the droid as a whole. Those extra entries add up in a hurry.


I like how you think however. I definitly agree that it would be fun, and put some RP back into being a DE.
Kleston
Fri Sep 17, 2004 2:54 pm
#3

Aye, most don't realise this but even though databases can store a lot more information in a lot smaller space, they still do add up when you figure in hundreds of thousands of identical yet varied entries.




  • Kleston - Gorath

  • Kre'Ivo - Scylla

  • Jerard - Bloodfin


If it moves, shoot it. If it shoots back, duck. If you can't duck, pray. If praying doesn't work, you're dead.
Jeryld
Fri Sep 17, 2004 4:55 pm
#4






Jjiaah wrote:

While an innovative idea, this would end up requiring way too much database space unfortunately. The servers would need to keep track of each and every module in the droid and if it was functioning or not, instead of just the droid as a whole. Those extra entries add up in a hurry.


I like how you think however. I definitly agree that it would be fun, and put some RP back into being a DE.





Ihave absolutely no knowledge at all of the structure, limitationsor even the type of database that SWG uses. So it's not really a subject that I canconstructively discusse. I understand your point, but I don't believe it would be necessary to add nearly as many extra fields as you think to each "droid record". I can think of a scenario where only 1 extra field would be required....but it's pretty pointless for me togo intothis, as in reality I know sweet FA about what would be required.


All I do know is that this is something that I would love to see put in place - and if enough people feel the same way, then maybe it's worth my or anyone else's time to write it up as a proposal, so the devs can either dismiss it as too much work, or beyond what is possible, or what ever. Or maybe even agree to it But I guess it all depends on how many people out there think it's a worth while idea....


Cheers

Redskuller
Fri Sep 17, 2004 5:10 pm
#5

my thought on the droid decay: Let there be a hidden limit on how many times you can call out a droid; set the limit to fall between 250-300 callings and let expermintation quality of all the sub-parts make up the number of times the droid can be called out. In addition, make some animations for when a droid "dies" and, if the droid has a storage module installed, let it turn into a container, like the locked/unlocked containers but with a decorated outer shell; limit the holding capacity of the "new" droid container to the limit of the storage module.



Redskull Lobobo, Armorsmithe, Merchant
In game since day 2-- ex-M.DE (pre-CU, CU)
Forum Auction Vendor Located at ( -332. -5580 C-net, Corellia)
Tarquinas
wabicajo
Sun Sep 19, 2004 12:05 am
#6

This is an interesting idea. It certainly makes sense, droids fall apart, they get repaired. I don't think it would be a memory problem, since all the components are kept track of, how else would you know what is in your droid. Clearly things that get more wear, motive systems, manipulator arms, combat modules, would have to be repaired more frequently than say a storage module. Of course, if the droid is totally destroyed, you would be able to get any items and data from the droid. You could even sell the broken parts to the junk dealers. It would make more business for DEs, and help with roleplaying. Also, maybe you could make the option of being able to switch out modules. If you have an R3 with certain functions you don't want, go to a DE to swap in the ones you do. Very handy, and would save the customer money.



Wabicajo Aleranga-Master droid engineer/pilot/Novice armor smith
Eclipse
Your sig is too wide for my screen
Shugard
Sun Sep 19, 2004 12:24 am
#7






wabicajo wrote:
Very handy, and would save the customer money.





Not exactly what i want to do.


Anigma of Bria


Master Droid Engineer

Master Aritisian

Master Merchant



Anigma of Bria
Master Architect
Master Artisian
Master Merchant

Anigma's Harvesters WP 5292 6067, Kaadara Naboo


- I support a rollback and keeping & balancing the old combat system.
...and making SWG a better place to be.
Your voice counts!
Jeryld
Sun Sep 19, 2004 11:09 am
#8


Saving the customer money doesn't = reduced profit for you.In fact, It should give you more custom, and so increase your profit....
wabicajo
Sun Sep 19, 2004 4:41 pm
#9

Besides, saving the customer money would mean that they would come back more frequently and get more things. A person would me more inclined to by components when they want instead of a bunch of droids that may or may not suit them. You would have more people coming in more frequently for things, which is good.



Wabicajo Aleranga-Master droid engineer/pilot/Novice armor smith
Eclipse
Your sig is too wide for my screen
Page 1 of 1
Previous Next