Droid Engineer Archive
Thread: Droid Crafting fix slated for Wednesday
Well, in the most recent update to the Update Issues page, this is what Q had to say about our inability to craft most of our droids:
droid engineers cannot craft some (or all) droids | ? | 15-Oct | researching
Honestly, this doesn't sound too promising, as the bug apparently hasn't even been verified by QA...Wednesday sounds hopefully optimistic, but it definitely would be nice.
On a side note, I had a customer last night who wanted me to make an actual BLL out of a BLL chassis he already had. I told him about the bug, but he still wanted to go through with it. Lo and behold, it actually ended up working. And, after he called out the droid, I customized it and had him store/call it, and the customization actually remained on the droid. So at least this is one case where the internal server error won't occur.
Yeah, a few people have pointed out that the list of droids with the "internal server error" and the list of droids to which color does not stick were identical.
Frankly, Wednesday is disappointing to me. I'm not angry ('cause I've been angry for two days, and it's wore me out so I don't have the energy to be angry anymore), just disappointed. I understand they have to investigate the problem, but we've been out of commission for so long now... All I've been able to do for the last few days is run missions to make money (since I can't sell droids) and place harvesters. I now have enough Vatee iron to make a fleet of MSE droids so astounding they would require their own planet.
I'm being patient, I really am. But there's a limit to that patience, and I fear it's drawing near.
Biranno Runningstar
0-0-0-0 Droid Engineer (and bugged to stay that way)
I'm sure it's nothing and probably means even less, but did anyone notice that in that second column (the one labeled "Verified by ourQA?") that the two issues pertaining to DE had question marks (?) in them, whereas everything else was a Yes, No, or left blank when not applicable.
I find that ironic yet somehow brutally honest on the part of SOE. It's as if they are saying "Yes we confirmed this is an issue, no we haven't been able to confirm that as an issue, but where DEs are concerned, we don't even know what we don't even know. We just know that there's a lot of complaining going on over there." Sad yet pathetic.
Then again, I'm probably reading too much into it. It's still pathetic though.
Marc_Deltram wrote:
I'm sure it's nothing and probably means even less, but did anyone notice that in that second column (the one labeled "Verified by ourQA?") that the two issues pertaining to DE had question marks (?) in them, whereas everything else was a Yes, No, or left blank when not applicable.
I find that ironic yet somehow brutally honest on the part of SOE. It's as if they are saying "Yes we confirmed this is an issue, no we haven't been able to confirm that as an issue, but where DEs are concerned, we don't even know what we don't even know. We just know that there's a lot of complaining going on over there." Sad yet pathetic.
Then again, I'm probably reading too much into it. It's still pathetic though.
I think they just use the "?" until such time as they:
1) "Trap" the bug in-house via the debugging machines.
...or...
2) Find the code line(s) that actually contain the bug.
Once they verify it as a 187% undeniable bug, on their end, they will likely update this to say "Yes".
/bow
Respectfully,