Some people think that taking a half hour in a dungeon is intolerable. That's fine for them to follow in their premade groups, but I don't think it's fair to apply that to everyone.
And AFK is in the list of kick reasons.Heck in a dungeon both dps can literally afk the entire thing and it's still possible to clear. It'll just take a while.
I seem to recall having already covered this.Like I stated before, if the tank cannot for the life of them hold agro, for some reason refuse to use tank stance and are doing practically nothing but are still running in and just spamming the 1 key, do you kick him?
Removing someone from a run for making it impossible to clear isn't the same kind of thing I'm anti-jerk about.
Probably not. But you seem to be fine with going through my older posts anyways, so I assumed you'd have come across it.I don't believe I've discussed with you about specific uses of parsers for that kind of scenario with you.
The question really is why open the door when there's an acceptable way around opening it?why would the community need to cater for it and not get a tool for the better end of the spectrum?
Look at threat meter to compare the people who are sharing to those who aren't.What if every DPS is hiding theirs? Or what if two are hiding theirs? Do you kick whoever's not sharing?
If nobody's willing to share at all, vote abandon. If they're not willing to help solve the problem, then being able to default see their numbers won't solve it either.
Embarrassment, fear of harassment.If three out of 4 DPS shares their number, then why would there be a need to hide it if others can conclude you're the dead weight of the party while the other 3 are doing well?
Nothing. With party parsers, what's stopping people from kicking without offering help?What's stopping people from kicking them before asking?
Which confuses me because there wasn't any need to remove the party bonus in that case (if the removal was related to the TP bars, maybe just a coincidence) because the party bonus wouldn't be updated at all throughout a run short of people being kicked/leaving and replaced.I have no idea how Square-Enix codes things, but from what I'm guessing about their logic about the TP bar:
They're sending a lot of data in a single object to each user every set amount of time per second (or once per second? No idea). While the user client can calculate the TP based on the actions players do, it wouldn't make sense for TP to be calculated locally, rather than being retrieved. Or at least, I wouldn't program it myself where you send 99% of related data through one object and send the remaining 1% through another.
If they're not related, then whatever, maybe they just decided that party bonus wasn't really important enough to be seen (true, but besides the point).
If they are related, that suggests actual display/UI real estate issues, rather than necessarily having to do with what data is actually being sent when.
If the latter is the issue, a party-wide visible parse during combat would be a bigger issue than a personal one.
If someone's going to the difficulty to mod their client to lie about a parse, you'd think they'd go through the difficulty to learn to play.Whoever mods (or hacks) their parser to fabricate anything wouldn't cause any problems.