Talk:Ebon Vanguard Assassin Support

Archive

---

• 2007 - 2010

Assassin attacks

I think the assassin's attacks are counted as your own attacks? I just noticed this in Ruins of Surmia HM where whenever the sin attacked something with Shield of Judgement on it I got knocked down. Also, that would explain the fact that the user sees the sin's crit energy gain... Jeree95 14:54, 14 September 2012 (UTC)

Bug

Someone had the same bug as me from the Ebon Vanguard Assassin page with the summon not going away after a long period of time. Put it as bug. --SuperPudz 07:16, 12 February 2015 (UTC)

Soul Reaping

When the assassin disappears, Soul Reaping does not trigger. It does trigger if he is killed, however. I'm not sure how best to fit this into the article. Mist Y (talk) 11:26, 19 September 2018 (UTC)

1 Revert

That anomaly is nonsensical and/or wrong. The assassin does not always attack the target the spell was cast on. This is well known and established. The duration of the summon is dependent on the type of creature the spell is cast on. There is no inconsistent behavior here. That anomaly should be removed. 50.28.145.79 18:14, 16 October 2019 (UTC)

Does the attacking have anything to do with the target not being Charr and Charr being within earshot? Or is it independant of creature types? And even thought it's well known it's still a bug in my book. Steve1 (talk) 18:33, 16 October 2019 (UTC)

The vanguard assassin has no special targeting priority for charr or any other mob type. The fact that it occasionally attacks a different target is a separate topic entirely, and I'd argue that that is more of an anomaly than a bug. It appears to generally attack the closest enemy to the location it is summoned at. Because it isn't summoned exactly at the target's location, sometimes the closest enemy isn't the spell target. You can see that occur here. There are some niche edge cases with things like corpse aggro. Dead assassins and Asuran summons don't leave "corpses", but something lingers for a bit if they are killed because Asuran summons will aggro onto mobs as can be seen here, and vanguard assassins will occasionally behave oddly under similar circumstances.

Regardless of the exact mechanics of the targeting, there is no anomalous behavior with charr that isn't also present elsewhere, and that's why that note should be removed. It conflates separate topics. The duration of the summon is always tied to the creature type of the target the spell is cast upon. 50.28.145.79 19:28, 16 October 2019 (UTC)

Understood. I'm not very knowledgable about the skill's mechanics, so I went with the info which was given. You could've amended the page yourself, by the way. :) Steve1 (talk) 20:50, 16 October 2019 (UTC)

Different IP but me again. I'm going to add an elaboration to the anomaly note specifying that it will chose the closest target. I'd like to include the fact that this behavior isn't 100% consistent, but cannot think of a way to do so in a manner that is both concise and clear. 76.127.242.82 01:32, 17 October 2019 (UTC)

Bug/Anomaly Minion Limit Check

Noticed this while playing around today. Summoning the EVAS checks the players minion control limit, and will destroy any minions over the limit if the players Death Magic attribute has decreased since their last summon.

To make it easier to explain: At 12 Death Magic, you can control 8 minions. If someone casts Wail of Doom on you, your Death Magic is reduced to 0 and you should only be able to control 2 minions. However, the game only checks the minion limit whenever you summon a new creature, not when your death magic decreases, or increases for that matter. So, at 0 Death Magic from Wail of Doom, you can retain control of your 8 minions unless you were to summon a new one while still at 0 Death Magic, at which point the game will check your minion limit (which is now 2) and destroy any minions over that limit.

EVAS is doing exactly that. In game, I went from 14 Death Magic with Masochism active, to 12 Death Magic when Masochism expired (Rt/N so Masochism isn't permanently maintainable) and retained control of my 9 minions. However, using EVAS would immediately destroy one of my minions so long as Masochism wasn't on me. Therefore, EVAS is causing the game to check the minion limit, which is either an anomaly or a bug, probably the latter. Soldier198 (talk) 03:57, 28 November 2020 (UTC)