That moment when...

[Adrian74]

If I'd post the most absurd reasons I have got kicked about.... Geez...

But here comes two of the recent pealrs:

Kicked in a dungeon because saying "Foe Requiem exists" to the bard.
Kicked in a dungeon for using a macro I have that salutes party and says I'm the crazy relic user, and my progress with the relics.

In both kicks, I got kicked...IN THE LAST BOSS, before entering, they used me for speeding up their dungeon like f-ing cowards and then just kicked me before ending. At least they could have done it prior to first boss... x'3

[LineageRazor]

Kicked in a dungeon because saying "Foe Requiem exists" to the bard.
Kicked in a dungeon for using a macro I have that salutes party and says I'm the crazy relic user, and my progress with the relics.

While I wouldn't personally kick you for doing these, it's not hard for me to see why they would annoy people.

In the first case, "Foe Requiem exists" implies that the Bard doesn't know Foe Requiem exists. You're telling the bard that he doesn't know his job. It's not hard to see why the bard would be annoyed by this, and if the others in the party were the bard's friends, it's not hard to see why they'd agree to kick you. A better way to go about it would have been to say, "May I have Foe Requiem, please?" There's still folks out there sensitive enough to be offended even by that, but they'd have less justification, and you'd have a better story to tell the forum.

In the second case, it comes across as bragging. Additionally, if you spam it a lot, then folks would get tired of it fast - in fact, ANY frequently-used macro that also has chat text is going to get very tiresome, very fast. I'm guessing, though, that you only use it once per dungeon - in which case, the question would be WHY? Why is this information important for other players to know? Perhaps you ARE bragging?

[Adrian74]

While I wouldn't personally kick you for doing these, it's not hard for me to see why they would annoy people.

In the first case, "Foe Requiem exists" implies that the Bard doesn't know Foe Requiem exists. You're telling the bard that he doesn't know his job. It's not hard to see why the bard would be annoyed by this, and if the others in the party were the bard's friends, it's not hard to see why they'd agree to kick you. A better way to go about it would have been to say, "May I have Foe Requiem, please?" There's still folks out there sensitive enough to be offended even by that, but they'd have less justification, and you'd have a better story to tell the forum.

In the second case, it comes across as bragging. Additionally, if you spam it a lot, then folks would get tired of it fast - in fact, ANY frequently-used macro that also has chat text is going to get very tiresome, very fast. I'm guessing, though, that you only use it once per dungeon - in which case, the question would be WHY? Why is this information important for other players to know? Perhaps you ARE bragging?

Well... In the first case, while laughing a little with the raid people, I joked with "Maybe I should have said 'Hi dear Bard, I don't want to be unrespectful but, do you perhaps know that Foe Requiem is a skill that reduces the magic vulnerability of our enemies by 10%? And it doesn't reduce you 20% damage like the other songs... so... could you use it?"

But... for language economy, and, already tired at that moment, I just decided to "Foe Requiem exists"... That they indeed took bad... Heh...

About the second case... Well, the spam is only once in a dungeon, and sometimes... People likes to brag about many things, their coil stuff, their Final Witness tittle, etc... Everyone have their tastes, my obsession are the relic weapons and so, I like to have a macro showing my progress with it (It was at the first time for having track of my own relics, sometimes used to forget which step was which... Too many of them, after it, evolved to make it my salute macro)
Of course I could also just use The Final Witness tittle and that stuff, but, hey, my tastes. (I personally would not kick someone for such a thing, but I already know that macro has 'AGGRO MAX')