Carbineer Archive
Thread: A real problem with what they did today
herrrmit wrote:
To NoOnesEnemy:
You're obviously right that it didn't work as intended, but it still does not, and the devs haven't fixed anything else that's broken with the profession. That's why most of us are upset. And again, to set the record straigt, I have been shot by the target at whom I was spamming charge shot; in its pre-nerf status, it did not render a target helpless. All it did was keep the target in one place. It did not actually work like a real kd, and guess what; it still does not. I hope you were equally diligent in /bug reporting all other broken carbineer specials, because the ineffective broken specials are about all we have left.
I think the better subject line would be "A real problem with all the things they did not do today". I'm a master carbineer and the most effective thing I've found are full auto 2 and charge shot 1 even with the correction. That's what, 0.0.0.2 strictly speaking of specials.Give the class something worthwhile, please.
I mastered carbine to augment my master swordsman and masterbrawlerwith counterattack stacking,ranged mitigation and the ability to stun, blind people and to get close enough to them to deliver some pain samurai styleusing charge shot with my 1.2 speed DH17 (powered up). I've never killed anyoneworthy with the carbine alone. Worthy means they're buffed like me, wearing armor like me, and have mastered at least one elite/hybrid combat profession. Killing defenseless or non-combatant people does not count for this discussion.
Regarding today's fix, spamming charge shot just never seemed effective to me to kill mobs or people. Warcry2-charge shot-full auto 2 kills mobs way, way, way faster. As for killing people, after stunning and blindingthem with full auto, I would usechargeshot to get close enough to deliver warcry2 and all the crunchy goodness that soon follows (TK dizzy attack since there isn't one in carbineer, intimidate, head hit, you know the rest). Hopefully they would still be wielding a gun so there would be no melee mitigation to deal with.
Now, I still deliver some painassword/carbineafter this patch andbounty hunter/carbine can deliver some pain too, but what about the carbineerswho are carbineerpurists? Perhaps it's as Thunderheart said of pikeman,"it's ahybrid class meant to beplayed with something else". If that is so, surely there should still be more to offer than 0.0.0.2.
$0.02
You obviously have no idea what /chargeShot1 was, or is.
NoOnesEnemy wrote:
What I was basicly trying to get at was that pretty much everyone on this forum is complaining about the wrong thing, and saying that Carbineer has been "nerfed", which it hasn't. That would imply that one aspect of carbineer that had been working fine, had been taken away or had it's effects reduced.From what I've heard, CS1 was fixed. The people that did the fixing obviously forgot about the rest of the broken profession though, and only fixed part of it.
First, it has never been a "real" KD on par with the other KDs in the game. It pinned you down, it didn't put you on your back unable to do anything.
Now, the Dev(s) put it on the "KD timer", which would imply that they actually changed it to a "real" KD, which of course, they didn't. It is now in limbo between what the Devs think it is, what it was and what it is now. It's got the worst of everything now, it's on a timer, it doesn't stick and it hardly knocks down anything. I just fired 35 times and it worked once.
/chargeShot1 is now completely broken. It was slightly broken before, thus it has been nerfed. I don't think it was nerfed intentionally by the Devs, the problem is they have no clue how our specials actually work in-game because 80% of them don't work as described. So when some part-time coder whips out his outdated design docs and starts "balancing" things, of course he's going to mess up.
They should have just left us the F alone until they had the time to figure out the mess the Dev team left for the Live team.
They obviously thought, "Hey. a KD. That's an easy fix, it just needs a timer, we can do that" and so they put a KD timer on something that never was a real KD to begin with.
They know they screwed up but of course they wont hotfix it, because that would mean that they would have to admit that they, like you, have no idea how our specials work.
So please, before you piss off even more people by claiming that something was fixed, go educate yourself on what /chargeShot1 was ( not what BH dabblers made it look like ) and what it is now.
NoOnesEnemy wrote:
With a fast enough gun you could reapply the KD fast enough to stop them from ever standing up, rendering a target helpless.And I did state that I knew why most people were upset. What I was basicly trying to get at was that pretty much everyone on this forum is complaining about the wrong thing, and saying that Carbineer has been "nerfed", which it hasn't. That would imply that one aspect of carbineer that had been working fine, had been taken away or had it's effects reduced.From what I've heard, CS1 was fixed. The people that did the fixing obviously forgot about the rest of the broken profession though, and only fixed part of it.
/salute NoOnesEnemy
I believe we are talking about the same thing here. For the purposes of this discussion, I won't refer to the "fix" of chargeshot as a nerf. Though, I believe you understand that the effect it has on the profession as a whole is exactly the same as a nerf. I am doubtful that the fix was complete, however. I will take your word that with a fast enough gun (though we'd have to be talking about a krayt gun here...I've got a 2.5 speed laser and a 1.7 speed dh17, and I can't do it with either one), charge shot could be spammed fast enough to render a target helpless, though it would have to be stipulated that no other shots are mixed in with charge shot, like cripple shot, which is a slow special. The point I'm making is that the bh carbine kd (I don't know the name) actually kd's for about five seconds or so, but our charge shot only kd's for about one, or maybe two seconds at most, and this is why I doubt it is, in fact, working as intended.