Droid Engineer Archive

Anyway, what you were saying about crafting packages made a lot of sense to me, and seems like a good reason to package crafting, item and data storage in one droid.

Now let's take it one step further: You use the droid to make five schematics, hook it up to an equipment factory, and say 'go'. It extends it's computer interface arm, and gets to work.

Two days later, without further intervention on your part, your factory output hopper is filled with 500 GP modules, 500 Memory modules, 250 Control units, 100 Droid Brains, and a partirdge in a pear tree.

Would you mindif I addedthis to the new thread?

http://forums.station.sony.com/swg/board/message?board.id=droid_engineer&message.id=37192

I like this idea quite a bit. One slight hitch though, in regards to droids storing on server rest, but if that was restored this would be a great addition to the usefulness of the R series droid.

By all means, put it where folks'll see it. :-)

It just struck me as a really solid and realistic aspect of automation, when I saw what you had said. It's really your idea, just extended.

Thanks Rho.

I just updated to Version 1.1 to include a few changes that should make for a better 'DEV Proposal', but I need input from the rest of the DE community. It would probably be read more if it wasn't so freakin long, but it takes a lot to cover so many issues. Please feel free to post ideas like this on that thread as well. It will only help me compile a much better concept idea page. Unfortunatly it will also add to the length of that monstrosity