Carbineer Archive
Thread: chargeShot1 & chargeShot2
Page 1 of 1
EfreaK
Tue Feb 17, 2004 3:19 am
#1
I know that chargeShot1 is wasted now, errr...I mean fixed.
But whats the status on chargeShot2, has it been fixed or "fixed"?
But whats the status on chargeShot2, has it been fixed or "fixed"?
What to dabble next...
Lobam
Tue Feb 17, 2004 6:05 am
#3
What do ya mean? Do you mean that it does not animate the KD repeatedly, or do you mean something else? I haven't got it yet, but i'm only a few k xp away...
EfreaK wrote:
I know that chargeShot1 is wasted now
Aibar
Tue Feb 17, 2004 6:46 am
#4
chargeshot 1 works but it is on a timer now so it can not be spammed anymore, and if you kd your target they get right back up, shouldn't the target at least stay down for a few seconds before getting back up ?
Esquilax1138
Wed Feb 18, 2004 1:11 am
#6
Charge shot 1 works ok,not much of a KD on mobs but I notice a good 5 seconds KD on NPC's, enough time to get in a crippleshot and a FAS2 or scattershot2 usually, can be very effective. Charge shot 2 does absolutly nothing, don't even bother with it.
TAfirehawk
Wed Feb 18, 2004 1:20 am
#7
Yes the 5 second timer on the KD effect is GREAT now. With +85 Carbine Speed I can get in 3 CrippleShots before they get up
Before the patch, with same carbine speed, same weapon, same creatures....barely get ONE CrippleShot.
The % to hit of ChargeShot1 was also changed, a stealth nerf. I found this out fighting Rancors, which I have done for about 4 weeks and now ChargeShot1 is much less effective.
There never was a problem with the 30 second KD timer, the animation was a less than one second posture to prone, NOT KD. Now we have the added damage multiplier and 5 second KD effect timer ![]()
I need to try some other melee classes with no KD defense, but PC's seem to still go down on spam posture to prone, but PvE definitely doesn't show the "false" animation anymore. Although it seems to act like a StoppingShot instead of posture change to prone. My testing has been on Rancors that are much harder to hit and I typically am running the other way to see the exact response 
More testing to follow....
Page 1 of 1