That's nothing. I was running WoD once and got a really bad group. We very nearly wiped during the Ahriman fight, and the only reason we didn't is because I had to spend most of the fight reviving our healers and tanks, (across the entire alliance), rather than DPSing. We managed to make it through the fight in the end though without wiping, (somehow). And less than a second after, I got kicked. Why? (As I found out from a friend of mine I had went in with who didn't get kicked, thank you Linkshells.) Because I didn't get all of the hourglasses killed at one point when there were only about 5 DPS up across the entire Alliance. No one got killed by the hourglasses, and I managed to swiftcast revive one of the healers in my party right before the countdown on the hourglasses ran out. This was the only time I've legitimately rage quit a game, as I logged out for a few hours after I had been told why I was kicked.......
EDIT: Not really on topic that much, I know. I just felt like venting a bit......
EDIT2: On topic, the only text macros I use are for Resurrection, (mine is literally just "Reviving <t>"), and Convalescence. And I only ever use Convalescence if I'm below half health, and the macro on it is basically just saying that if anyone is free to heal me, any heals on me are boosted temporarily. I'm thinking about shortening my Convalescence one though, as sometimes I have to hit the button twice due to it not activating the skill properly sometimes, yet still displaying the text. I really wish there was a check in place, (in the form of a simple "did previous action activate" Yes/No with a different path for each), that would keep text from activating unless the skill itself activates first. It would cut down on a lot of accidental macro spam. I've seen more than a few people who accidentally press a button and even though the skill doesn't activate, the text pops up. It's pretty common with revive macros in particular it seems......



Reply With Quote

