One problem with the March 10 update to ready check

Quote:

---

Players can no longer use the ready check feature if they have generated any enmity on a monster. If a party member who has yet to generate any enmity initiates a ready check, the ready check confirmation answer for players that have generated enmity against a monster will automatically be submitted as “No.”

---

So let's say in CT everyone gathers at first fight.

I'll say I do this for simplicity, but could be whoever. I look around, everyone seems ready, I pull.

Someone else who hasn't generated enmity yet initiates a ready check.

So then it defaults to saying I'm not ready cause I have enmity on one of the mobs we're checking to see if we're ready for?!?

Makes absolutely no sense at all.

Maybe they were thinking if someone was off fighting something else? *shrugs*

I think in the example you provided it would be plainly obvious that you are in fact not "Not Ready"

If the person who initiated (or anyone else for that matter) is waiting at that point for the ready check to have everyone confirmed, then I would say it would be the least of your worries.

It should default that you are ready, if you have Enmity on a target. Because you would have taken action against said target.

Ready check is annoying... don't do it during dungeons.

Only reason I see for ready check is when it took awhile to gather people through party finder, you want to make sure everyone is there and switching back to the correct jobs.

I wouldn't miss ready check at all if they just removed it from dungeons.

Quote:

---

Originally Posted by LordSaviour

It should default that you are ready, if you have Enmity on a target. Because you would have taken action against said target.

---

But ready check doesn't check what target you are fighting, for all the rest of the group knows you aren't fighting what you are supposed to (Ready check is for more than CT)

I like the improvement on it. Doesn't flash across the screen with who is a check or an X like it used to. Additionally, it says who started it.

CT is a bad example for a reason to change this. Except, if someone is using it to harass or be troublesome, now you know who is doing it.

I believe it's for situations outside of dungeons. It will autoselect "No' for you if you're doing a FATE or Hunting Logs etc. to kill time until the party fills so the leader doesn't queue the dungeon.

Quote:

---

Originally Posted by Alistaire

So let's say in CT everyone gathers at first fight.

Makes absolutely no sense at all.

---

Ready check can be for anything and not just in CT. For example, what if the party leader is asking if everyone's ready to queue into DF or Coil, and someone's busy fighting a mob? The game tells you he's not ready. It makes sense to design it this way. If you can clearly SEE him fighting the mob, logically you know he's ready. Hence the reason for them to default it to "not ready" is for situations where you cannot see your party member. It may be useful in future CT / Coil bits where the raid gets split up. Maybe there's a bit of a maze section, maybe someone's about to initiate a mechanic like unlocking some floodgate unleashing the hordes of hell and it'd be nice to know if someone's off in some corner somewhere getting his butt whooped.