Quote Originally Posted by Brine_Gildchaff View Post
I'm gonna be frank here. If you pull this kind of thing with a huge-damage mob like Marraco or a petrifier like Zanig'oh, you're not gonna get thanked, you're gonna get reported, because resetting on a mob like that screws over whoever got killed/petrified for longer than the mob's average lifetime. I speak from personal experience here, I -found- Maahes once and the SMN with me didn't have a lot of time, so we shouted and then pulled after ~30 seconds. The horde proceeded to reset it TWICE, and as the party's tank I was petrified BOTH times, destroying any chance I might have had to build up enmity and get anything besides "you poked it once" credit.
This has been discussed to death on other threads, and we even had Enkatreia weigh in on it: resetting a mob can be considered harassment and can leave you subject to punishment.
Quote Originally Posted by Ashkendor View Post
Yup. Seen this happen with Maahes and Alectryon. All the cries of "omg resetting doesn't hurt anyone" make me shake my head because many of these mobs can kill/disable players and leave them getting no credit after it's reset.
Yeah, but that point only stands for two or three exceptions.
Plus, I was talking about a very low number of people; my group plus the number of people around would have made 10 at most.

So, even if a few people would have been caught petrified or dead, the number or players actually getting in the fight were at least ten times more.

The point of my post was to show that, in this situation, canceling an early pull was more beneficial for a lot of people rather that selfishness and "deal with it, I'm pulling when I want".
It was also an opportunity for me to remind people of the nature of this game: a PvE game with very little competition.
Denying people to get some Seals has absolutly no purpose and/or benefits.