[Pan]

Arum, don't presume to speak for Omni.

We were the first to try the ringwar on this server (with our allies and other people who showed up to help). It was buggy as hell.

We're very interested in trying it again when the third wave can be checked and held with melee aggro - as it should be. (Assuming that the giants/corpses/summoned under the world are either fixed or accounted for by an on-site GM).

We are not interested in picking of a Dain that shouldn't be spawning. And that's the genesis and nexus of my posts in the raid forum.

All tuning mechanics aside, that Dain puts the raid guilds on the server in an untenable situation. Specifically:

They have asked us not to exploit bugs.
They have called the failed-war Dain a bug. (Which, by definition, would make killing him an exploit.)
Upon spawning, this buggy Dain precludes a legitimate Dain from spawning.
Some raid guilds have chosen to kill the buggy Dain (leaving out all arguments or intent-to-spawn here intentionally).

The upshot of this is that those guilds who choose to kill the buggy Dain are at risk of sanction by the staff. And historically on this server, in my opinion, the rules are enforced fairly inconsistently. That, to me, means that it's not implausible for someone on the staff to wake up, realize that something that they've called a bug is being exploited (for whatever reasons - justifyable or not), and then issue bans/suspensions/dissoulutions/whatever the caprice of the moment dictates. It's entirely possible that could happen. And a defensible argument could be made for it.

The situation is both untenable and needless. A simple word...or serial DTs and resets...from the staff is all it would take to put this matter to rest. As it stands, those who choose not to compete for that Dain are losing opportunities - while those who do are assuming a rather hefty but absolutely unknown risk. And there's no reason for it.