Quote Originally Posted by KyroeFelix View Post
Question: Is it rude to tell someone they are playing an aspect of their job incorrectly in front of other people? Example: I see DRGs who use Power Surge and DragonFire Dive all the time, not realizing Power Surge doesn't affect DFD at all. I would like to say something to them, but since you can't send a /tell in instances, I usually don't. I don't want to be offensive and call them out in front of the party.
Usually I'd say to send them a tell, but as you mentioned, you can't do that here. I don't think it's rude -if- it's worded correctly. The OP's example was someone being rude. In that example, I likely would have went something like "I was just wondering if you knew that you could be a Warrior starting at 30, and it'd unlock a tanking skill called Defiance?"... or... since they mentioned they were new, "In case you didn't know, you can unlock your job at level 30, and get job quests from there. It has some useful skills for tanking.".. and then elaborate from there.

I've ran across people that didn't realize you get job skills every 5 levels. They just knew sometimes there was a quest there but not how often, or tried to go back to the class place and saw nothing available so thought it ended. So a portion of that often depends on level, or if they announce they're new to the game. If it's an endgame dungeon and it's something like that Paladin doesn't have shield oath up, I'll straight up just say "FYI, shield oath isn't active". That's something a lot of people forget to do. I know both tanks in our guild have forgot it during raids.. it's immediately noticeable when we have (I'm one of them), but mistakes happen, we're all human.

Some people may still get offended (I've never personally ran into someone who does, but have heard stories) as some folks just take any type of helpful comments as insulting. Overall though, I think you'll find people widely welcome advice when you're nice about it.