Droid Engineer Archive

---

Mightion wrote:
The R2 I made after the 10th was built with a chassis I'd made in my factory before the patch. After I colored him the first time (R2-B1 lives again!), his colors have stayed. The chassis was colored white with red trim, though...

---

This is really good news, because this is the type of droid I built for a customer yesterday, who then could not program him. After numerous attempts, I could not color the frame, and had to give up. Whenever he pulled the droid from his pad, the frame had a different random color.

---

Gimps wrote:

I've used pre patch R2's 3's and 4 chassis to create new droids yesterday and today,so there's no problem there.

---

Well I made a new droid for my customer and exhanged it for the droid I made yesterday, and I couldn't find a problem with the droid. I was able to color it the first time, using the 'second' white box, instead of the first -- as was suggested here on this board.

So, perhaps the only serious problem we may still have is related to the medical modules. It looks like we're still getting complaints about those, from what I'm reading here.

I've been selling a lot of medical R2s today and the 'Recharge your Droid Trick' has worked almost each and every time.A fewproblems that I did run into today werepeople trying to use their batteries while stiil in a crate, or from their backpack. In order for a Battery to recharge the Droid, the person must have the battery in their inventory.

The only time that this didn't, I simply asked the person to store their droid and call it again. Not surprising to me, this worked like a charm. It would seem that about 1 in 100 - 1000 times, a droid loses some of its function when called. Simply storing the droid and making sure that it is charged up after you call it back out again has been the remedy that has worked more than 99.9% of the tiem. That .1% that it didn't work was because I built the droid while falling asleep and forgot to install the medical package