Droid Engineer Archive

Falacy you are my hero.

Your are an icon of myopia.

I rent lots from other player to harvest more resources because I like to make lots of different things, It isn't hard to fill up a datapad with waypoints to rented harvester lots, your city and your home, PC armor, PC weapon, PC tailor, stim shops, resource shop vendors, 5 droids, 2 non-ch pets or god forbid if you ARE a CH. I personally rent about 30 harvester lots I rarely put all 10 from one guy on one resource. That is the best way to get enough of one resource to really make good use of a factory. I do intend to make runs of 10000 armor modules for my droids once I get a schematic that suits my purposes.

Not everyone wants to make liberal use of the delete key, and continually have to fiddle with getting a new waypoint to your favorite vendor's shop on one planet or another.
Not everyone wants to play the exact same way.

I suppose is might be worth qualifying what my 67% consists off....

First off the planet in question is Tatooine. I have The Pod Race start, Torche Station, Sarlacc, Anthrout(sp?), Jabbas Palace, Fort Tusken, Jawa Fortress, Lars Moisture Farm, Krayt graveyard and a couple of other 'famous places' bookmarked

I have my house, my generator and my extractor (I only own 3 pieces of real estate)

I have my Bantha and my Probot and usually a medical droid (since I'm a Droid Merchant my droid entries can fluctuate though as I have been known to do trade-ins and I will often sell my personal droids under the right circumstances)

The rest of them are player shops (usually ones without Advertising III so they are not on the map - but since the map resets when the servers reboot I find the bookmarks better anyway) that I go to either to buy stock or to buy so my own use.

Now its likely that the other planets wont have so many 'tourist attraction' waypoints as Tatooine but I hope this shows how easy it is to fill your datapad up :-)

You're still my hero.... ah, and look at that, I'm someone's here too!

See, we DEs can be special! Would ya look at that....

---

HRESULTStoreDataInDroid(CData*& data)

{

if (CData->IsType() != Schematic) {

return E_FAIL;

}

else {

m_Data.push_back(data);

return S_Ok;

}

}

---

LMAO!

Your assuming the devs were smart enough to prototypethe data objectand use pointers. Its sad but we could stick in one or two more varibles and just LIMIT the number of pets in a droid, instead of what they did.

Wait a second guys: I got a hold of the source code for DE's datapad, and I think I figured out the problem:

HRESULTStoreDataInDroid(CData*& data)

{

if (CData->IsType() != Schematic) {

return E_FAIL;

}

else {

m_Data.push_back(data);

return S_Ok;

}

}

It's 2:42 am what can I say?

Data modules should be able to store waypoints. There's no reason why they shouldn't be able to do it. I can't think of a single reason why. No exploits or anything.

It's been a long time since I last posted. I'm a touch less cynical now. However, there still isn't a point/need for the data module in a droid. It's been so for over a year now.

The trouble with storing waypoints is simply that it opens up the possibility that people could 'crack' a droid module and be able to store mission waypoints. From a roleplaying point of view, this might actually be a cool feature to give to smugglers. However, by the same token it would also be exploited. So, the Devs would need to find some kind of balance or some kind of secure way to diferentiate a plain "waypoint" from a "mission waypoint". This is likely the major concern and the easiest solution is the current one: do not allow droids to store waypoints.

The infinite droid nesting issue precludes the ability to store droids in droids. Can't put that option in, due to the ease of exploitation (and possible server crashes!).

So that leaves us with draft schematics. Which brings me back to my first post a year ago, who freakin' cares? You make a scematic, you walk over to your factory, you use the scematic, done. Really, unless you're some kind of pack-rat, there's no need to keep draft scematics at all.

In the end, Data Modules were an unfortunate waste of development time.

---

ASHRID wrote:
I suspect that they _should_ hold waypoints and it wouldnt suprise me if they accidentally broke this in their hurry to remove the fact that it could hold missions at one point (which are technically waypoints thus my theory)

I'd imagine when a dev finally gets around to it (or works out how to do it, or hell even works out that its broken) we will see waypoints able to be stored in them

---

They made it so WPs couldn't be used because people were taking MANY missions and storing mission WPs in the droids.

---

Geevo wrote:

---

ASHRID wrote:
I suspect that they _should_ hold waypoints and it wouldnt suprise me if they accidentally broke this in their hurry to remove the fact that it could hold missions at one point (which are technically waypoints thus my theory)

I'd imagine when a dev finally gets around to it (or works out how to do it, or hell even works out that its broken) we will see waypoints able to be stored in them

---

They made it so WPs couldn't be used because people were taking MANY missions and storing mission WPs in the droids.

---

This is the correct answer. Groups were storing mission waypoints, thus speeding up the xp gain beyond what the Devs believed was reasonable. Remember this was done in the days before mounts and speeders so there was a deliberate time-sink having to run back to get more missions. Droids storing missions bypassed that time-sink, and as such the practice was defined as an exploit. Hence it was nerfed.

Simple as that, and not likely to change anytime soon

---

falacy wrote:
br>So that leaves us with draft schematics. Which brings me back to my first post a year ago, who freakin' cares? You make a scematic, you walk over to your factory, you use the scematic, done. Really, unless you're some kind of pack-rat, there's no need to keep draft scematics at all.

In the end, Data Modules were an unfortunate waste of development time.

---

Well then you don't do mass manufactoring. I make on average 30-40 schems that I want to keep for PuPs when I sit down and make them. That way I don't ahve to sit there and try and make a schem for the type of PuP I want to make. I also do this with my parts for making droids. I make a schem for lets say Adv Brains. I then run the fact long enough to get 2 then make all the other pieces I need t to make an R3 Adv Chassis. Once I ahve all the schems made I need then I start the factories going in earnest making all the parts that are needed. I use most if not all 100 data storage in my crafting droid when I'm making schems. Why? Because I don't want to waste time in the future! I'm not always in a crafting mood when a factory is ready for a new run either. I can keep 4 factories going at once. 3 with parts and 1 with the chassis. I hand craft the fianl droid and the clusters to match what customers want with the exception of my medicals and the R3 Adv Bombs I make.

Ingred' Silverfire, Bria
Master DE

Yalton, that's totally cool, but I'd have to say that you're likely one of the vast minority of truly organised individuals. Good on you for actually making a use of this module!

Of course, the data module isn't entirely useless. However, at the same time, it's just not abundantly useful either - save for the few people like Yalton who are maticulously organised. For crafters, it serves its purpose. As for having it do more, it's like we've said before in this thread:

The Devs couldn't stop people from storing Mission way points, so they had to can all waypoints. Also, people were making so many nested droids (droids inside droids inside droids...), they caused server problems when travelling across zones. As such, and considering the low priority of the matter, we are left with the current amount of functionality. Which, as Yalton pointed out, isn't all together useless.