Oh I missed the whole Caan/Nae argument.

Caan I was the raid leader. I raid lead most of the time in HE when I'm online. Nae helped ease the burden, especially when this computer went down and I couldn't raid, and he was remarkably more controlled in doing so than I expected, and I thank him for that. As far as the hope we get rolled back thing, we were told no we aren't, and why should we? We get no extra loot. We got loot like one week early. As Nae said, and I'm not defending his tone, to call this "tarnishing our guild name" for the fact the event respawns on its own, in addition to the lockout working, is not BS in my opinion. Was it a mistake? Of course it was, but this isn't anywhere near the comparison of hacking, not AT ALL. It's just apples and oranges. There is no comparison. The event does this on its own, and was left in this state long enough for the rumors about the event lockout extending being the norm to spread. Think about that. The event is over a year old. This has been going on for more than a year. I'm not going to claim in hindsight it was a smart thing to do, but the fact is we got no free loot.

I was raid leader, but I'm not leader. I don't remember how it went all down but I expressed my concerns but in the end it was my mistake to think three was no big deal, and in the end I thought it was mere lockout management. A mistake to be sure, but a taint on the guild? No, and I'm not sorry to say that, because we got no free loot. We defeated the event and the only difference is it was one day instead of two weeks. Again, I'm not saying it was smart to do it, but it's nowhere NEAR on the level of more severe exploits or hacking. Heck, in my opinion beam kiting and the formerly exploitable ranger headshot thing, and yes even bard AE kiting as dangerous as it was way back when were significantly worse than this. Would I sit back and see it happen again? Of course not. The only reason I did is because we got no free loot. That's not an excuse, that's the reason. I didn't suggest doing it, but I didn't refuse to lead the raid either, so that is my bad, but a shame that taints the guild? Something that merits a rollback? For a lockout that functions properly over the period the event would normally be farmed anyway, for three spawns? No, I'm sorry but I disagree that that in any way shape or form resembles hacking raid bosses (which was the rumor Nae was talking about, not that I support the drama over it).

Nae may lack tact, especially when angry, but he is correct that this does not correspond to the hacking allegations way back when. It's night and day. This was not smart. Ghost killing is outright cheating.

Now, to end this on a positive note, Caan left a VERY good first impression on me. A long time ago, IL was having trouble. Rumors were floating around that it was going to fold. Caan was going to app to us, but our monks were close, if I recall. Our monks opened up a few weeks later and he was told, if I recall right. Even though he apped to a guild that looked like it may die, he stayed with IL. He said he wanted to stay the course, that it would be wrong to jump ship all because things look bad. I have a TON of respect for that. He stayed, and the guild is still around, and I give my kudos to any IL member that stayed then. I don't look at jumping ship when guilds have issues in a positive light. Guilds have ups and downs, and the fact Caan stayed even as an app speaks volumes for his character. As many people know, when a guild has issues there are some that jump ship for greener pastures and there are people that stay to keep things going and to rebuild. I'm going to defend Caan because that one incident really impressed me, and I've never had an unpleasant conversation with him, aside from one awkward misunderstanding a long time ago that was resolved in minutes (I asked him which targets IL was doing in ToB so HE could avoid them to avoid any open zone confusion and it was misinterpreted to mean I was stating what targets HE was doing or something like that).

Sooooo we made a mistake, but I won't sit there and see it compared to hacking. As I said, it's night and day. The event itself functions this way and has probably since release, long enough for some people to consider it the norm, people we unfortunately chose to take advice from.

Caan, had we spawned it a ton of times, perhaps I'd agree, but I don't call three times chain spawning in the least. Again, was it okay? Based on the logic we were following we thought so, but obviously it wasn't, but that's what a mistake is. Mistake? Yes? Grievous wrong doing? Heck no. As I've said several times, we got nothing extra out of it. If we had, I'm sure there would have been a rollback, which there wasn't, nor was anyone banned. It just wasn't a smart thing to do.