Changelog 24/11/2014 (The Blighted Isle and Chrace)

[Sulorie]

Searing Touch is the way it is because of the Archmage's ill thought out mechanic. With max Tranquility you can either fire an instant RL or get a 25% damage bonus to all 3 ticks of ST. ST'S first tick is also instant as you noticed. I checked the combat log, cast bar and WSCT when finding the number of ticks.

3 ticks is still wrong and you can watch the video proof. It has an initial tick which is instant and 3 ticks every 2 sec.
The awful mechanic itself has nothing to do with those skills.

http://youtu.be/hwznDVq647w?t=4m10s

First hit RL crit, then 4 ticks ST. This is totally clear. The dmg text in HUD isn't always in sync and appears slightly later but the number of ticks stay the same. The mob loses his hitpoints in 4 steps after RL was cast. I think this should end the discussion about the number of ST ticks.

[Azarael]

I've noticed that there are discrepancies in both sources - yours and mine. In yours:

https://www.youtube.com/watch?feature=p ... 647w#t=802

Disrupt, 242, 242 for 3 hits.

In mine:

https://www.youtube.com/watch?v=PrBiKtz ... page#t=229
https://www.youtube.com/watch?v=PrBiKtz ... page#t=294

Both show 4 ticks in contrast to the earlier instance of 3 ticks. In all sources where there's another tick, it comes after the spell should have ended according to the castbar. Note that the first tick appears as soon as the castbar does, so client latency can be eliminated as a cause of this fourth hit after the spell should have finished time-wise.

Edit: Looking at the Youtube timing, it takes 6 seconds, in contrast to the castbar which finishes early. I'm inclined to agree with 4 ticks now, at 0s, 2s, 4s and 6s.

[Telen]

I'm definitely wrong. Cannot remember that last tick being after the channel ends just that there were 3 ticks during the channel. Think I've been playing swtor too long. Everythings dumbed down and instant.

Just watched a few vids to try to remember. Many of the videos do seem to show it having 3 ticks. Thats when either the target dies just after the channel ends or the next cast kills them. Think thats where the confusion comes from. That final tick isn't during the channel. Its a long time after it ends. You can even get a full cast of RL in before the final tick actually hits. The travel time of ST must be 3s Id guess. The first tick being instant and the other ticks with a 3s travel time beginning right after the first. Meaning the last one hits 3s after the channel ends.

Interesting. Wish I could go back and test this. When you clipped it at 3s did you still get the 3rd tick?

I dont think its a bug or shitty code. I think it is intentionally how the spell works with having a 3s travel time for each subsequent tick.

[Azarael]

Yeah. I gave the later instances a thorough look and the issue is with the client - the bar moves too fast. It takes 6 seconds for those 4 hits to be delivered, and so I agree with Sulorie. Making a note.

[Sulorie]

EDIT: Great that we came to an agreement.



Well, my main was a DPS AM as well and Telen said he is not 100% sure.
When you notice the castbar dropping rapidly between second 6 and 4, then you have to moment where one tick gets lost short after the disrupt. This is the bug, if you want to call it out.

The damage per tick/hit of ST and RL is the same. Both have the same base damage as well. This is not going to happen, when one of them only hits every 3 seconds, while the other has a cast time of 2 seconds.

Furthermore your own testing is wrong, because the target gets killed with the 4 second tick, but the damage numbers are just delayed. This happens even in my posted video proof, when the target dies before the channel is complete.
Here an example of your own video but with a target which survives the channel cast. 4 ticks, both visible and in combat log.

http://youtu.be/PrBiKtzMaWg?t=3m49s

The only "bug" which happens here are delays after being disrupted and non-finished casts which miss the final tick.

[Telen]

Had a look at it a few more times and I'm wondering if the current ticks might be correct just without the first instant tick and a travel time.

As you can see from this http://youtu.be/ptdvYtJzcfs?t=9m55s

The player can get a full RL cast in before the final tick of ST hits.

So the channel does end 2s before the final tick lands.

This could be the confusion with the old private server code being was it 0.5 3 5.5. Those maybe the tick times ignoring the instant first tick and the travel time of the ticks.

[Azarael]

The problem with a lot of these videos is that the original uploaders were not kind enough to play with the combat log on. The interface (especially the original Warhammer interface, as Sulorie's pointed out) is very laggy, but the combat log updates instantly. By timing the two instances of Searing Touch applied at the end of the Sewers video using the combat log, it can be seen that there is an instant first tick and there is also a tick at 6 seconds afterwards in Youtube time, with two ticks in between.

[wiscel]

Did something change to the NPC at the BO's? Last night I could'nt kill even one of them.

[Azarael]

They're higher level and mobs hit harder.

[Sulorie]

The problem with a lot of these videos is that the original uploaders were not kind enough to play with the combat log on. The interface (especially the original Warhammer interface, as Sulorie's pointed out) is very laggy, but the combat log updates instantly. By timing the two instances of Searing Touch applied at the end of the Sewers video using the combat log, it can be seen that there is an instant first tick and there is also a tick at 6 seconds afterwards in Youtube time, with two ticks in between.

Yes, and often when they have the combat log on, they have disabled the time stamps. ^^