Commando Archive

I went PvP for a bit before the servers crashed in Coronet City. What I saw was a bit strange. After I used flame single and flame cone on targets they burned as normal before the incap. Now it has been my experience that when they come out of incap they are still burning and immediately incap and take a large amount of wounds. This was not happening last night,after they came out of incap, eventhough they still had the "on fire" icon in their status bars they were not taking the DOT. They would get up, and without a heal, run around for I'd say a good 2-3 minutes before they even bothered jumping into some water. I got burned as well, and I was able to run 750m (stupid me took the long way)to the nearest water source.

Anyone else notice that the DOT didn't keep ticking off after an incap last night? Is this another stealth nerf? Or was it just the crappy connectivity to the servers last night?

After an incap all dots should start ticking again after about 4 minutes, it's to give the other person a chance to heal and remove said dot.

Back in beta they ticked immediately which meant people would rapidly get incapped 3 times in a row thus causing death, or if the 3 incap = death event didn't occur they were be incapped until it wore off, so they started a 4 minute timer on it to give people a chance.

Ahhh, so now it is working as intended. Well that is good to know that they are fixing stuff. But it makes me wonder why they would let it hit immediately, and the flame was the only one that did this from my experience. I'd get poisoned and bled and all that fun stuff and after an incap it would take a while to start ticking again, but with the flame it would start ticking right away.