Droid Engineer Archive
Thread: Delivery Droids Proposal v1
Javac wrote:
Ogge_the_Lizard wrote:
I'll leave the function discussion to you pro's... I'm just a passionate DE that would like to see it fair.
To be honest on the resource side it would be something more like:
Steel: 20
Iron: 10
Copper(maybe a rare): 15
Inert Gas: 20
Polymer: 25
Electronics GP Units: 2 (non-identical)
Electronics Memory Units: 1 (it has to remember location right?)
Droid Storage Compartment: 1 (doh!)
Maybe even add Control Units or Droid Sensor Packages (could be Micro Sensor Suites instead). Now this would be options for lvl 5-6 modules. Low lvl modules would be much easier to make with probably lower range and less items. Maybe even planetary delivery only for low lvl and interplanetary for higher.
The Survey droids would then be reworked and devided into a droid and a module, this delivery module could then be used in that droid model. It would be like a spendable long range droid, for delivery and surveying (maybe even some more functions for JTL).
Egads! You realize how much more expensive all that crap will make the droids? I'd rather it have no subcomponents, perhaps one MM at most. I took the resource requirements for a Level4 storage module since I can't see a delivery droid holding more than that, and upped it a little bit. Note this isn't a complete droid ... just a module, so you'd have to drop it into a droid (probably MSE).
The reason I thought about it this way is that it would be easier for the devs to code, since you can already drop items into droids with storage. This version would just be a lower cap, and have the 'deliver' functionality.
Yes I do know, but in that case it would have unlimited or a high amount of uses. (if the droid decay is fixed sometime soon).
I'm just trying to be realistic, even though some new modules (read barker, harvester) do not require sub components I feel that with the demand on subcomponents for other droids it would only be fair. And frankly I'm an old timer DE and wouldn't wanna see the droid being a simple use and throw away style droid.
I don't think the required subcomponents are hard to code, the hardest would be the function in it self... since everything that is a certain distance from players (say 1-2km I don't know exactly) don't even exist in the server, they are all loaded as a player approaches. And a droid that dissapears from one place and warps to another (although we already have this
) would probably be harder to code and integrate with the system that some subcomponents in a draft schematic.
Javac wrote:
Gotcha now, two different ways of approaching it then. Personally I don't see them implementing Droid Decay anytime soon which is another reason why I suggested the one-shot deal. It's taking fucntions that are already present in droids for this new task. The only completely new part would be the pickup on the customer end.
I could however go to a middle field(seeing as droid decay seem to be far into the future)... where the droid+module is a bit more expensive to makethan you would like. And where you would to "recharge" the module, with thrusters or gas or something maybe, and thereby creating a consumable.