Droid Engineer Archive
Thread: Data droids and a use for them to (Dev)
Ok, first of all this isn't a new suggestion, it's a simple request to implement something that has apparantly been planned from the beginning.
Implement Schematic and Data Object sizes.
Everyone's seen the Schematic Size number on items that they can craft. All that Is really nesescary is to implement this characteristic so that schematics (and to a lesser extent mission data objects) take up more than one space on the datapad. This will give people who frequently use schematics or who do deliver missions a reason to buy data droids, and it'll give us a new market.
DaHumAn wrote:
if we cant store waypoints in them they are only one thing: useless.
Limited use, but not useless. I know a handful of crafters (myself included) that couldn't operate our business nearly as well without the data modules. It makes for a great way to organize factory blueprints for those of us who don't make one shot deals.
DaHumAn wrote:
i make stuff by the thousands so i never use it =).
I generally do as well, but there are times that I don't know if I'll need more of a part or not, or if I get some great experimental values with something (more for my doctor stuff, since experimental value doesn't do much for droids) I'll make a schematic even if I don't have the resources to make quantity at the time, then store them in a droid as I work on finding more of the resources I need.
I usually put item and data storage both in, so that i can store the schematics, and the resources needed to fill that schematic. Makes it handy to have them both in the same place if I need one of the schematics later. Adding the appropriate crafting tool is handy too. And it can be done even in an advanced MSE without using any epxloits, at my skill levels.