I can actually explain most of the bugs created by the "Revived Enemy". It's because it doesn't actually do what it says it does. The spell describes it as the Shadow "Mimicing" the enemy, in other words, becoming a copy of it. The game even tries to copy it (Hence the model in T pose when you hit them with the Spirit Mark spell too late), but instead all of its A.I. goes into the original monster (The copy is deleted), so as a result, it still keeps all of its Flags/Labels/Markers/Identifiers. So if you need to clear the room to continue, if it had actually made a successful copy, it wouldn't be flagged as a "bad guy" at all, but because the A.I. "scripts" are placed into the original bad guy, all of the labels remain. They need to be placed into the New Model, not the bad guy that is originally afflicted with the Spirit Mark spell/curse.
Here is a list of the things affected by this bug: Unkillable A.I., Glitched A.I. Mechanics (Running into a corner, not attacking anything, random roaming in combat), Affected by AoE spells (Especially Walking Bomb). EDIT: Broken textures for the minion as well. (The Minion is supposed to be purple, transparent, and glowing, but sometimes it retains its original textures).
I mean, you finally have some form (though be it light) of Necromancy in the game, which is awesome... but Necromancers have minions, and our 1 minion in the game is broken. There goes a half of our specialization damage (3 spells only, 2 of them deal damage, one being the enemy post-mortum in the form of the minion... which is inconsistent).
And by the way, this is also the same way in which the "Simulacrum" passive is bugged. We're still in our original bodies, MOST of the time we don't even retexture (So we do not know we're dead). And for the love of common sense, Make using PHYSICAL ITEMS (POTIONS) IMPOSSIBLE. I keep Wasting potions thinking I saved myself right in the nick of time, only to die 10 seconds later.
Message to EA/Bioware: Fire your Q&A, because I've only taken 2 beginner programming classes and I can easily identify this problem... which I've solved. All you need to do is pass this message to your programmers, bada-bing, bada-boom.
