Droid Engineer Archive

My wife, a Master Scout and Ranger-in-training brought this to my attention. Seems the harvest droid I made for her malfunctions once in a while. When told to harvest a corpse, the little guy will not do it. Sometimes he'll go part way to the corpse and return, other times he sits there like a paperweight. Whn this happens it takes a couple of harvest commands to get him to do his job. On the other hand, he always obeys the attack command and others.

To verify this, I became a novice Scout and made myself a harvest droid. Exact same scenario!

Since we bothe are using the same cable internet connection, my first thought was that it is caused by some sort of lag monster or something. I've made and sold many harvester droids and have never received even one complaint about this kind of activity from the droids.

Has anyone else noted this happening, and is there a known cause, or could this just be a game "bug"?

Thanks in advance!

Yabu Miekag
Elder Droid Engineer
Home base at Mos Syn on Tatooine, Flurry Server

When ever you command the droid to harvest something, you must make sure that the droid starts to move before you change targets. After you give your droid the command to harvest something, wait 2 seconds before changing targets. Once the Droid starts moving along its merry way, you are free to chose your next target. Also make sure that you are not canceling all targets, by clicking 'open air'. This will cause the same result.

Making SWG more Star Warsy. One droid at a time.

Thanks for the quick response! Yes - in fact since I was testing what my wife had reported, I remained on target until the droid actually finished the harvest. Since I'm Master Arty, Master DE, and Master Merchy, I have only very basic Scout skills, and am only working with creatures from Kaadu on down, but the results are the same. Doesn't seem to be related to wounds on the droid or the power level, but when it does happen, it is generally after a harvest or two.

If the droid refused to act on other commands, such as attack or store, I'd be inclined to believe it was a connection issue at our end. But since harvest is the only one it seems to "forget", I'm at somewhat of a loss.

The only related issue I can attach to this is that once in a while one of my "bodyguard" droids will forget the "guard" command, and display a "?" when I issue the command. But the harvest droid shows no such message.

Yabu Miekag
Elder Droid Engineer
Home base at Mos Syn on Tatooine, Flurry Server

Previous reports (and my own experience with this) have led me to conclude it has more to do with latency in the server/planet/zone you are hunting than any flaw in the droid. Its just something thats gonna happen from time to time. I'm guessing that after a failed harvest from the droid, you can longer harvest it yourself.

My guess is, that any "fix" implemented would involve increasing the "acquisition" timer in the Harvesting code (to overcome a lag delay) since this would increase time per harvest even more, its an issue of the devil you know over the devil you don't. I prefer knowing ahead of time that sometimes my droid just won't work, as opposed to knowing he will always take longer than I prefer to harvest.

Gilack Mehoipou [Bloodfin]

Quintuple Master- Marksman/Squad Leader/Rifleman/Vortex Pilot/Politician

Made it before all hell broke loose.

As long as we're on the harvister droid subject.. Do scouts get any xp if they use the harvest droid instead of harvesting a corpse themselves?

My lady friend and I just starting using harvest droids today and we love them. We did not experience any problems with them harvesting every corpse we pointed them at. We were hunting outside of coronet too, so there was quite the server load in the area.

Once, andonly once, I did have to tell my droid twice to harvest a corpse. The first time it just sat there and the second time it hopped right to it. Other than that the droid never failed to get the resources that I wanted promptly.

These things are great. I really wish that I had bought one sooner.