Urzigurumash wrote: »

It wasn't Soul Shatter was it?

No, as I said I don’t have any passives or other skills unlocked. My Soul Magic level is 1 and I only have Trap because it’s a default skill everybody has. This was the first thing I looked up when it occurred.

Is there a weird interaction where a specific Necromancer skill is considered Soul Magic? Or does Oblivion‘s Foe proc by itself? It’s kinda weird.

maybe you altered somehow the durations, if you refresh Soul Trap on enemy does the dot from the set refreshes too? You cast it once, both get 10 seconds. You recast Soul Trap after 5 seconds, both get to 10 seconds again? or Soul Trap goes to 10 seconds and the set remains at 5 seconds?

or more logical, he used a cleanse and he cleansed your spell and not the set

Ok, it happened again while doing pledges on a boss mob. Soul Trap wasn’t active, but Oblivion‘s Foe was ticking for it‘s full duration. I don’t understand what procs it.

It's proccing at the beginning of your soul trap cast and at the end most likely. This happens with some sets in the game like Relequen because the time you cast a skill and the time it actually hits can be mileseconds apart.

For those who aren't aware, Relequen actually hits twice a second if you're weaving, once if you're not. This is because it will register your light or heavy attack hitting the moment you press the button, but the target doesn't actually take damage until a fraction of a second later. This is illustrated really easily by standing 28m away with a bow, you will notice relequen procs before your arrow hits the target.

For the relequen example:

0s - Light attack cast
0s - Relequen ticks (5s duration left)
0.1s - Light attack damage lands
1.0s - Relequen ticks (4s duration left)
1.1s - Second light attack cast
1.1s - Relequen ticks (5s duration left - refreshed from second light attack)
1.2s - Second light attack damage lands

So by continuing the above pattern, Relequen shows it actually hits twice a second because you refresh the dot a fraction of a second after it last hit. This happens with a lot of dots that have their first tick at 0s, instead of 1-2s into the duration. This is a big reason why dots like poison injection, venomous claw and twin slashes were changed a few years ago to only have the dot tick 2s in instead of at 0s. The adjustment was made because people were able to use these direct damage + dot skills as spammables since the initial dot tick + direct damage allowed it to outperform regular spammables like flurry. In this brief period of time, Stam DK's were able to use venomous claw as their class spammable.

So with that logic, this is my guess for soul trap and oblivions foe given the above example:

0s - Cast Soul trap (Oblivions Foe set checks if target has set dot running, if not, it procs on target for +10s duration)
0.1s - Soul Trap Ticks (Some type of travel time/delay between cast and actually dealing damage)
2.0 Oblivions Foe ticks (8s left)
2.1s - soul trap dot ticks
4.0s - Oblivions Foe ticks (6s left)
4.1s - soul trap dot ticks
6.0s - Oblivions Foe ticks (4s left)
6.1s - soul trap dot ticks
8.0s - Oblivions Foe ticks (2s left)
8.1s - soul trap dot ticks
10s - Oblivions Foe ticks (Expires)
10.1s Soul trap dot ticks. Oblivion's Foe's dot expired at 10s, so this last hit at 10.1s procs the set again.

TLDR: It happens because of travel time/server delay. The set is doing it's check when you cast soul trap, but also when the target takes damage from soul trap. If there is a delay in soul trap doing dot damage, you will get an extra oblivion foe proc out of it.

Seraphayel wrote: »

@MashmalloMan You could be right about this. I thought about a similar effect, but it still is very weird as it doesn’t apply all the time, but ocassionally.

The thing is, you cannot reapply Oblivon‘s Foe (OF) as long as it‘s on the enemy - this basically means OF procs sooner than Soul Trap when first applied. If not, the last tick of Soul Trap couldn’t reapply OF. But again, it doesn’t happen all the time, which makes this occurrence even weirder. I don’t even know if the explanation with the delay is the given reason for this to happen at all.

Ideally, oblivions for should only proc on a target that doesn't already have the proc on them, so likely what happens, is that the last tick of your soul trap happens after the last tick of the setz and hence it reapplies it.
It's within the rule set of the set itself, even if a bit wierd.

Seraphayel wrote: »

Firstmep wrote: »

Seraphayel wrote: »

@MashmalloMan You could be right about this. I thought about a similar effect, but it still is very weird as it doesn’t apply all the time, but ocassionally.

The thing is, you cannot reapply Oblivon‘s Foe (OF) as long as it‘s on the enemy - this basically means OF procs sooner than Soul Trap when first applied. If not, the last tick of Soul Trap couldn’t reapply OF. But again, it doesn’t happen all the time, which makes this occurrence even weirder. I don’t even know if the explanation with the delay is the given reason for this to happen at all.

Ideally, oblivions for should only proc on a target that doesn't already have the proc on them, so likely what happens, is that the last tick of your soul trap happens after the last tick of the setz and hence it reapplies it.
It's within the rule set of the set itself, even if a bit wierd.

I understand this, but based on this logic it has to apply every time I apply Soul Trap to an enemy. The usual rotation then would look like this:

Soul Trap > Oblivion‘s Foe > Oblivion‘s Foe >> Soul Trap > Oblivion‘s Foe > Oblivion‘s Foe

I am not aware that this happens every time I reapply Soul Trap, so that basically one Soul Trap gives you two Oblivion‘s Foe DoTs. I‘ll test it when I’m back in game and give an update.

Yeah not sure, it could be server delay as well, frankly. That would explain the sporadic nature of this event.