Droid Engineer Archive
Thread: R3 ADV. with no RANGED command? What happened?
Page 1 of 2
SenDerlo
Sat Aug 28, 2004 9:03 pm
#1
A friend of mine made me an R3 Adv. for use in combat. However, it does not seem to have the RANGED command. The one R3 ADV. that he has that does have the RANGED command no longer can have that command programmed. He is not sure why this happened.
Only thing we can think of is did they take out the RANGED command for R3 ADV. at some point?
Only thing we can think of is did they take out the RANGED command for R3 ADV. at some point?
Message Edited by SenDerlo on 08-28-2004 09:32 PM
Ranar
Sat Aug 28, 2004 10:43 pm
#2
Well, since CSR gave me the hearty 'we cannot help you, try the forums' rather than an answer, and my search turned up nothing, I'll try here.
Built an R3 Adv about a month back. 2 combat-capable clusters, six droid combat modules. Uploaded it to my datapad. Set all the commands, including the Ranged Attack: command. Fast-forward to tonight. Build another R3 Adv, same layout. Sell it to someone...they do not have a Ranged Attack: under the programs list. I pull out my older R3 and look. I still have a PREVIOUSLY PROGRAMMED Ranged Attack: command (zap ranged), but I NO LONGER HAVE the option to set theRanged Attack:under programs.
It looks as if they either broke something within the last month or purposely nerfed the command. Zap can still fight ranged, but I now cannot change his name as I can no longer change the Ranged Attack command. This is also confusing to customers. When did this happen?
Ordlander
Sun Aug 29, 2004 6:19 am
#3
This is a good question. I have been stumped about this as well. I been going on using it with old one and then new ones told "thought you said could set ranged attack, what gives" I look at mine and nope no more comand but it does seem to work. Build a new one, deed it and nope, it not there 
That leaves two choices and SOE will not say one way or another!
1)They entended to remove the option and umm forgot to mention it.
2)They goofed and no clue that it is missing and we will say this for mouths then all a suden they will wake up and say hey look what we found and all a suden the command will back it like nothing ever happened.
So yes, in the mean time our R3 units can not be set to ranged or mellee. They will do what they think is best. So this was when it decides to go ranged and it has auto-repair mods in it, and your partners also decides same thing and go a different direction. They will not get the joint heal power. Now also in closed in places where the last thing you want is it to go wheeling down the hall in corvette to get ranged in, guess what it will do 
(does not wait holding breath for a DEV response on whats up with ranged command removed)
Buzz1096
Sun Aug 29, 2004 7:51 am
#4
Yeah I noticed it too. The program command for ranged attack toggle no longer comes up on the R3. My toggle command on my droid still works, but no new R3s can be programmed for it.
We need some help from TK on this one.
I'll also put in a /bug report in game. You guys do the same if you can.
NitewolfX
Sun Aug 29, 2004 8:16 am
#5
*sigh* I never knew there was an option. Now I don't have the chance to see it in action.
Ranar
Sun Aug 29, 2004 8:20 am
#6
Yes, I bugged it last night.Also updated my CSR Ticket telling them that (at the time) there were no posts on this on the boards. If they give me the 'check the boards' line again, I am pointing them to this to show I am not the only one. WHY can't they just say 'known issue'? I mean, I'd write it off as a lost cause like the Structure Maintenance droids or the 2-3 things I've had disappear from my inventory in the last 2 days. *shrug*
Ackdel
Sun Aug 29, 2004 8:23 am
#7
http://forums.station.sony.com/swg/board/message?board.id=droid_engineer&message.id=94405&jump=true
That thread contains the last word from our correspondant about this issue. (that I know of) Might be good to bump him again. 
Drashk
Sun Aug 29, 2004 10:49 am
#8
I've talked to the QA that is responsible for all things Droid, on Test Center, about this issue. They are aware of this issue and it is on 'the list'. I'll see if I can bug a few of the QAs that I know, to see if I can get an answer on this issue, however I think that the DEVs have their hands full right now, with trying to finish Publish 10 up for next weeks release.
BTW, the ability to call a droid from the toolbar, which is supposed to make it out with Publish 10, is still MIA.
BTW, the ability to call a droid from the toolbar, which is supposed to make it out with Publish 10, is still MIA.
TheRealTK421
Sun Aug 29, 2004 3:01 pm
#9
Yup...everyone needs to /bug this.
Buzz1096 wrote:
We need some help from TK on this one.
I'll also put in a /bug report in game. You guys do the same if you can.
It is real. We have passed it on to QA already.
ETA on info/fix = unknown (but you'll know about 1 min. after I do).
/bow
Respectfully,
Ordlander
Mon Aug 30, 2004 5:14 pm
#10
Bugged it.
We know that they have hands full with pub 10. --- SO WHAT! --- Then guess what, JTL and fixing the bugs from pub 10. I do not have any hopes of this getting fixed this year though maybe we get lucky for a change. Getting old things that where working then not with them having a could care less mindset.
Malitevv
Mon Aug 30, 2004 5:22 pm
#11
i knew there was a reason I stopped making combat capable R3's. It seems I predicted this was going to happen without even knowing it.
just kidding.
seriously though. this sucks. I was getting ready to re-add combat R3's to my standard stock of droids. guess I won't bother. /bummer.
TheRealTK421
Mon Aug 30, 2004 6:53 pm
#12
To reiterate...
The Devs / QA are aware of this issue but no ETA on a fix.
/bow
Respectfully,
The Devs / QA are aware of this issue but no ETA on a fix.
/bow
Respectfully,
Stegoid
Wed Sep 01, 2004 4:56 am
#13
TheRealTK421 wrote:
To reiterate...
The Devs / QA are aware of this issue but no ETA on a fix.
/bow
Respectfully,
Just so we know what to expect...
When was the last known issue with a droid fixed?
Page 1 of 2