Droid Engineer Archive
Thread: Publish 7 (Droid Invasion): Please report any/all bugs or 'strangeness' here ONLY!! (03/16/04)
I've already put this in front of the Devs. However, it's not really a "bug" per se. It's the way the new Combat vs. GSM clusters are intended to function. If/when this will change, I can't say...but I have it in front of the Devs.
JJLDJ wrote:
TK or Gorantoth:
Could we please add to the droid issues thread the fact that astromechs don't accept non-combat clusters?
Thanks,
/bow
Respectfully,
Only the R3 Adv has 6 possible Combat Modules slots (via 2 Combat clusters).
caurannus wrote:
Everyone keeps talking about a 600 max cap combat rating for adv p bots, derived from 2 combat cluster modules. Anyone else getting this?
The Probot Adv. only has 5.
/bow
Respectfully,
Is anyone else having problems naming their newly-built droids?
quarda wrote:
...but I could not change the name of my Advanced Probot.
If so, please let me know here so I can get this into the queue.
/bow
Respectfully,
caurannus wrote:
Also i have been having some goofy experimentation results, ie amazing successes resulting in lower combat ratings, etc. It's almost like the craft nerf is still being applied to droids. Using materials over 950, i can't get above 77 combat rating, or above about 80% on experimentation, although all bars on quality are yellow and maxed out across the window, ie no room for experimentation if better minerals were used.
/bow
Shian_Tavkin wrote:
TK
No problems naming Probots from me
Okay, good. I've been seeing this about and just want to make sure. I'm guessing it might be newer DEs or droid owners that just aren't hip on how to name droids.
Don't forget to point people to the SWG KB, everyone...lots of GREAT droid info there (and more, as we add to it).
A strange thing is happening to my LE in combat though. Given the attack command he will shuffle into range and generally keeps going till incapped, however on several seperate occasions he has carried out 3 attack rounds and then stopped trying to fight. He just stands there
This is definitely not a battery issue, and its not on a server line unless Bestine has several server lines running through it, which I doubt. Odd say I
See what you can do to get me more hard data on this. I don't know if it's a high enough priority to elevate but we can keep an eye on it. If anyone else can confirm, that'd be the bee's knees.
One other thing, the healable range on the stims seems to be mighty short to me, especially with Probot moving so fast and so far during combat....can we get any details on range? and it there a difference in range from A to D (I dont think there is).
I've only made Bs, so far and not even a chance to really use them. If anyone can get hard data on this, it would help.
On the talkie droids, how come there is no STORE / DISMISScommand we can teach them to hear, or am I just blind? Do we have to use the radial Dismiss?
Okay..do NOT use Dismiss. This will basically destroy the droid. I'll find out about getting "Store" set on the radial instead of Dismiss. And..check to see if they actually changed it such that Dismiss actually means Store.
Thats all..the others have already listed my other issues discovered to date
Respectfully,
Add to bug list:
1. R2 droid set to Ranged combat uses the 'buzzsaw' animation graphics while making the lightning-gun sound.
2. A 'Failure' on a combat module decreased the mechanism quantity while increasing the Combat Rating.
3. The 15-second timer ceases to function after the first droid call. This one is already reported but I confirmed it last night in the wilds of Dantooine...First call took 15 seconds. Stored, call that droid back no delay. Stored it and called a different one which arrived with no delay.
Ibelieve I recallGenerate Vehicle did not have a delayeither.
I cannot confirm that the droid call worked with no delay after being in combat, I did not try that.
The obvious conclusion on #3 is that the delay code is having whatever flag triggers it set to OFF and it is never put back ON.
Kilarny wrote:
Add to bug list:
1. R2 droid set to Ranged combat uses the 'buzzsaw' animation graphics while making the lightning-gun sound.
2. A 'Failure' on a combat module decreased the mechanism quantity while increasing the Combat Rating.
3. The 15-second timer ceases to function after the first droid call. This one is already reported but I confirmed it last night in the wilds of Dantooine...First call took 15 seconds. Stored, call that droid back no delay. Stored it and called a different one which arrived with no delay.
Ibelieve I recallGenerate Vehicle did not have a delayeither.
I cannot confirm that the droid call worked with no delay after being in combat, I did not try that.
The obvious conclusion on #3 is that the delay code is having whatever flag triggers it set to OFF and it is never put back ON.
Kilarny,
Are these all (in your estimation) "confirmed" / verified?
If so, I can add them to the list...
/bow
Respectfully,
TheRealTK421 wrote:
On the talkie droids, how come there is no STORE / DISMISScommand we can teach them to hear, or am I just blind? Do we have to use the radial Dismiss?
Okay..do NOT use Dismiss. This will basically destroy the droid. I'll find out about getting "Store" set on the radial instead of Dismiss. And..check to see if they actually changed it such that Dismiss actually means Store.
I'm sure the radial option 'you are dismissed' is a store command, no doubt about it.
What I'm asking though is can we get it so we can teach it to respond to spacial 'store' rather than use the radial, its the only command (I think) that works like that
TheRealTK421 wrote:
Kilarny wrote:
Add to bug list:
1. R2 droid set to Ranged combat uses the 'buzzsaw' animation graphics while making the lightning-gun sound.
Have not attempted to reproduce this error, so it would not count as a reliable report yet.
2. A 'Failure' on a combat module decreased the mechanism quantity while increasing the Combat Rating.
Confirmed. Saw this 3 times last night, twice on Failures and once on a Moderate Success (?!).
3. The 15-second timer ceases to function after the first droid call. This one is already reported but I confirmed it last night in the wilds of Dantooine...First call took 15 seconds. Stored, call that droid back no delay. Stored it and called a different one which arrived with no delay.
Ibelieve I recallGenerate Vehicle did not have a delayeither.
I cannot confirm that the droid call worked with no delay after being in combat, I did not try that.
Confirmed.
The obvious conclusion on #3 is that the delay code is having whatever flag triggers it set to OFF and it is never put back ON.
Kilarny,
Are these all (in your estimation) "confirmed" / verified?
If so, I can add them to the list...
/bow
Respectfully,
Caix,
CaixCatab wrote:
Something's up with droid naming, but it doesn't happen all the time. I couldn't name my probot nor my R3on patch day, but I just named my R3 two minutes ago (to Bob, since I was expecting it not to work again
), but my probot still won't eat it's name. There's an issue, it just doesn't happen constantly.
See if you can get some hard data/evidence on this nailed down. I've been seeing naming strangeness but we need to try to confirm/verify the 'where/when/how' of this problem.
/bow
Respectfully,
Shian_Tavkin wrote:
TheRealTK421 wrote:
On the talkie droids, how come there is no STORE / DISMISScommand we can teach them to hear, or am I just blind? Do we have to use the radial Dismiss?
Okay..do NOT use Dismiss. This will basically destroy the droid. I'll find out about getting "Store" set on the radial instead of Dismiss. And..check to see if they actually changed it such that Dismiss actually means Store.
I'm sure the radial option 'you are dismissed' is a store command, no doubt about it.
What I'm asking though is can we get it so we can teach it to respond to spacial 'store' rather than use the radial, its the only command (I think) that works like that
Shian_Tavkin wrote:
TK
One other thing, the healable range on the stims seems to be mighty short to me, especially with Probot moving so fast and so far during combat....can we get any details on range? and it there a difference in range from A to D (I dont think there is).