^ This. I mean, like, my original post even bolded the point of what I was talking about... and its like only 3 lines long...

So people who cap doors only attempt to cap the door once every 12 seconds? *gets handed cue card* Oh, this just in, breaking news, people cap more than once every 12 seconds! Well, there goes your idea.

Although its quite a tangent at this point, many things in the combat log, especailly in operations, are not elegantly shown; some mechanics cause the player to damage themselves from a bosses' mechanic, a boss damaging itself, etc.

I stopped playing my jugg right before 1.2 hit when huttball stopped popping 90% of the time, so I honestly can't remember if taunt stops caps, I know the cry doesn't (the aoe slow). Though taunt doesn't ever do damage, on a delay or not, so I think that's truly up for debate, and one could really argue in taunt's favor, not to mention we might see DPS actually use it more although as an aside, interrupts which do no damage interrupt, but perhaps thats a special case since capping is a channeled cast and its an interrupt mechanic. Maybe its not elegant, but it would be to the player if it were hidden in the logs/floating text and one would think if their ability design is easily modifiable an extra 1 damage up front wouldn't be a big deal to change.

I've checked the logs, and yes it is kinetic damage. For sorcs with only ~18.85% damage reduction in light armor (assuming mostly rakata, little over 2000 armor) it ticks for 4999-5003. So assume 5000, every second, for five seconds. So I would think number #2 would be helpful.

Strictly speaking, creeping terror would be 20 force against FL's 28, if you only get the initial tick off, it becomes 22 force from the 6 back from 1 tick of damage. If you get 2 ticks off (you're slow clicking/tabbing the second target) then you would be more force efficient, bringing FL's cost to 16. If an assassin for example is the one capping the door, with shroud up you wont get any force back, as its a resist, and does no damage so no force would be returned. Edit: those numbers assume you have 600 force via talents, not the base 500. Another non-force factor is the vulnerability of being LoS channeling FL, as opposed to hitting the dot to prevent the cast completion and then hiding again. On the topic of melee, in most cases even attempting to run into melee range would be more risky then spamming your key hoping for force to return just-in-time. (Alternatively, the time it would take to run into melee range would be enough time for the force to return, as well - at least to stop one target.)

I like your humor in your post, but let me give you a realistic situation, one that I personally find myself in quite often in void star: I'm the last person alive on a door defending it (LoS Kiting around the pillars to use force lightning/shock/death field/force storm to stop the ~2 people from capping and avoiding damage from their ranged dealers to "hold off" the offense while my team respawns. Now, if theres two people capping, normally I would use death field to stop them both, then force lightning 1, wait for gcd, and force lightning the other. This is horribly force-inefficient, also odds are if I do this skillfully, I'll run out of force trying to prevent the two from capping. So this goes on, I'm now out of force. Now I can't interrupt them, unless I want to run into melee range, which I would for sure never make it, and realistically a sage/sorc meleeing is just not viable.

Consumption is a valid use, except when you can't afford the GCD to do it to prevent the cap. Dotting the target is a hostile action, any hostile actions otherwise prevent the capturing channel/cast. The initial application should count. 1.Yes every class has ways of doing it. Except sorcs when they're running empty on force (and don't die because of 2-3 healers keeping them up), which is also the same class most negatively impacted by the lack of the mechanic I'm questioning. 2a.I gave an incredibly simple, elegant solution. Even programatically - the initial application does 1 damage, followed by healing the target for 1 damage. 2b. Its a major-issue for sorcs that are dry on force. Its similar to the way hunters were in arena in Burning Crusade. If sorcs had a ranged auto attack that cost 0 force, this would not be a problem.

Of the 4 choices, they depend upon force, something that sage/sorc run out of (as dps, unless hybrid - which almost nobody runs anymore) become options that are not possible. And the fifth choice, melee? Thats just silly, but it does work. However in voidstar if a sorc/sage is ever sitting on top of a door without the express intent to disarm/arm, they are crazy and are not utilizing their range.

Its very ironic indeed!

Or, just make it do 1 up front damage and then heal the 1 damage that it deals up front. Same solution, it wont look elegantly in the combat log, but same deal.

Just because it was an issue (and it was a horribly unbalanced mechanic, interrupting on ever tick) doesn't mean it shouldn't be interrupted by the initial tick/application. This is especially painful to Sage/Sorc players as they have no ranged auto-attack or any way to instantly regenerate a lot of force (like vent heat).

Serious question. Applying a dot doesn't stop a cap. We all know the huge change where DoT damage doesn't interrupt channels, but why doesn't the INITIAL APPLICATION of a DoT interrupt the cast or alternatively, the first (and ONLY the first) tick of the DoT?

So essentially nobody can do this encounter without sniper bubble, unless you have zero sage/sorc (weak armor/health pools) Great.

I meant in 16, but its nice to know someone has. The problem there, is that you have zero Sorc/Sages. The lowest armor/health pool class in the game, without a real defensive cooldown.

All of the legacy abilities use Tech as their damage type. Isn't this unfair to classes that don't have + tech power?

Has anyone successfully done this portion of the encounter WITHOUT a sniper?

Since apparently my thread is still on the front page, it takes me 30 minutes, Madness Sorc with Talos. I have 600 prescence with the +84 buff. Its really easy, cc + kite + dot = win

We've had this problem 3-4 times. 16 man - hard.

Just to let everyone know

They're excellent at mid control, but they're also shut down easily. That's also their really only good role in huttball.

Tier list for huttball S-tier: Assassin (tank) A-tier: Sorc (either), Jugg (tank), Mara (with obliterate), Merc (Arsenal), Jugg (non-tank, with obliterate), Powertech (pyro), B-tier:Pyrotech (Tank) Assassin (non-tank), Operative (heal), Merc (any but Arsenal), Mara (without obliterate), C-tier: Operative (dps) D-tier: Sniper

Then give one of the kiting classes an actual defensive cooldown (Sage/Sorc) then kiting will be perfectly fine.

Well I did say vanish abilities. They both do it.

The only people who will be in full WH are on the heavily populated servers that don't have to wait on que times, and that play a LOT every day. To the second point, whats the issue with that?