You guys keep quoting this:
Quote:
Originally Posted by Rogean
[You must be logged in to view images. Log in or Register.]
I'm going to be coding in a mem blur immunity flag, and nilbog or I will go through all the raid mobs, including some epic mobs, to flag them for both mem blur immunity and charm immunity.
|
as evidence that this mechanic is an exploit, but you aren't quoting what it's in reply to:
Quote:
Originally Posted by ElanoraBryght
[You must be logged in to view images. Log in or Register.]
Here's the ones there have been issues with so far. Some of those issues were issues before 1/2, but unresolved petitions regarding raid rules, memblur and FTE make it highly likely they will see the same issues in the near future - and that someone's epic will be affected by it.
|
Which was an extension of the original post:
Quote:
Originally Posted by ElanoraBryght
[You must be logged in to view images. Log in or Register.]
Is it against server rules to charm / mez / memblur epic mobs, and loot epic mobs that you didn't kill / did not have permission to loot?
|
I am in no way Rogean, but I interpret that as in this specific thread, he is saying that because blurring mobs resets encounter logs (and thus enabling another guild to steal a mob they did not have FTE on/spawn themselves if people present are not running logs/fraps to dispute it, which is the topic of discussion in that thread), he will be patching in a fix (not classic) to flag certain raid/epic mobs as mem blur immune. It seems like his post is far more about preventing griefing/raid interference than preventing the mem blur = complete heal mechanic mentioned in this thread.
In no way does that quote by Rogean read like it means mobs should not be complete healing upon being mem blurred, and I haven't seen any other quotes of GM's making a ruling that this mechanic is an exploit, so until we see a ruling it would seem like mem blurring in VP (a zone where raid interference is allowed) to cause mobs to CH themselves is fair and open game.
Anyway, this is a bug report thread, so it should include evidence posts from the relevant time-frame of the server and such that this mechanic is not working appropriately. I'll let you guys get back to it.