I don't know of anyone on Stromm that was banned for anything in the recent past, and certainly not a large portion of my guild.

I can say there was no monkey business. We did not hack/exploit/cheat or anything like that. There is an event that repops, basically on its own. It has done this since it went live, and there are guilds that had several month lockouts on it. My guild had no lockouts NEARLY that long, but it did repop on us and we figured we did nothing wrong. Why? Because we got lockouts as you would expect. We did not go out of our way to make the event repop, unless you consider the trigger automatically repopping on its own going out of your way, and we did not think it would be an issue because the lockout mechanism properly worked, meaning in reality we got no extra loot. After I learned the GMs did not like that, I informed Caan and intended to let Sefta know (acquaintances from the other two guilds on Stromm in Crystallos) to let them know to back their raids to the sides of where the boss pops and be ready to blur it if it repops. I actually haven't talked to Sefta yet but I suspect someone else has. In any case I'll make sure FH knows.

Some from my guild defended their friends in Evo when that drama happened. The whole of HE did not jump up to criticize Evo. I know I didn't. I don't know what people in Evo got in trouble for, and I will not try to claim they were bad players at all, but having an event repop by itself on you and getting a slap on the wrist for it is hardly being Great Offenders. As I said, no one was banned, nor were there any rollbacks or anything like that. Had we known it was wrong we wouldn't have done it, because as I said it yielded no extra loot over time and as such I figured it did not fit as an exploit.

I bug reported it the first time it happened to us, and the word around was this was common knowledge, that many guilds would do the event a few times to keep it locked out for awhile, and that the GMs didn't care and the devs didn't fix it because the lockout functioned.

I am happy my guild has a pretty good reputation and I uphold that being honest is the best way to do that. Did I personally think an event repopping on top of the raid and yielding a lockout extension was all that terrible? No, again because of the lockout. I will see that this is fixed, will warn people not to kill it if it pops on top of them. There are guilds that have done FAR worse with this event, as I said. Do I want to see them punished and rolled back? Absolutely not, because as far as I know it's commonly thought this is acceptable for the event. As I said, I don't know exactly why the event repops, but I do know that every time we've done it its triggers have repopped on us. I hesitate to say which event exactly it was, so I'll leave it at "if an event repops on you don't kill it."

Now, on the topic of "karma." I've found that when people have disputes, both sides feel they are right and the other side is bad in some way. I'm sure Nae felt wronged by people in your guild. Did that excuse his comments when some of your friends got into trouble and he pounced and made a thread? Well no, but that's just how people work. Sorry Nae if you don't like me talking like that about you, and I know I'll have to say I'm sorry for saying sorry since you say I apologize too much. :P

In any case, long story short: No one was banned, but there is an event that was bugged since it first came out that repops on its own somehow, extending the lockout if killed again, and it's best not to kill it if it does.