System to curb Ready Check abuse?

[Ninix]

There is a lot of code you are asking them to modify and test to make sure it works properly. Personally, I'd rather this b part of 2.2x or 2.3 instead of having them delay 2.2 for this, which would be the other option.

There is no way this involves "a lot of code" unless they're talking about adding some overly complex way of blocking abuse with a cooldown on it or something, which is unnecessary. Later on, if they want to work on it some more and restrict it to the party leader only, or display who initiated the ready check in the popup, or add a cooldown, that's great. But all they'd have to do right now to make CT more bearable is to stop it from being used in combat.

In the event handler for the Yes button on the "Commence ready check?" popup, check if the player is in combat (using the same method the Vote Dismiss function uses to accomplish literally the exact same thing) and if they are, don't commence the ready check and display a red error message. Hell, they don't even have to translate the error message! Just use the generic "You can't do that yet." string.

I'm not expecting them to write the code, test it, merge it into the production branch, compile a patch, get it certified with Sony, bring down the servers, and deploy the fix tomorrow, just do it sooner than 4 months from now.

[Jeraldi]

2.2 is at the point where it is almost ready to ship and is a major content patch I would rather have them get that patch out then in a week or 2 add the ready check fix in with the fixes for the new content. Otherwise we will have a lot more extra maintenance time to deal with plus a less polished 2.2.

[Cigaran]

Hey everyone,

We've confirmed that the team is looking into limiting the use of ready check to outside of battle around patch 2.3.

Then please either:

1. Remove the functionality from the game until 2.3.
2. Make the use of this feature during combat a bannable offense.

The fact that this was allowed past QA or Localization as a possible griefing tool was bad enough. Taking three or more months to address the issue is a complete joke.

[Warku]

Its really frustrating and it seems like square-enix is the only company that waits 4 months to implement simple fixes to serious problems.

[ColorOfSakura]

This needs to be addressed well before 2.3 comes out. There's no reason for it to take 4 months for this to be implemented. If it's going to take that long to fix, then please remove the feature until it can work without people griefing the other players.

[Ry0uSh1n]

Hey everyone,

We've confirmed that the team is looking into limiting the use of ready check to outside of battle around patch 2.3.

I'm Sorry ... LMFAO .. SE @ it's best .. Look forward to it ...

[therpgfanatic]

Hey everyone,

We've confirmed that the team is looking into limiting the use of ready check to outside of battle around patch 2.3.

This could be hotfixed. It's literally just making it so people can't access the feature in combat. Just grab that part of the mount code that says "if character is in combat = cannot access, show system error message".

I've had to deal with trolls in nearly every Crystal Tower I've ran, who spam the ready and vote abandon feature as often as they can.

[Chiapet]

I find the feature annoying as heck.. who asked for it? gahhh i wanna just call them everyday at 2am and say "ready check!"

[Luso]

I find the feature annoying as heck.. who asked for it? gahhh i wanna just call them everyday at 2am and say "ready check!"

The feature is very annoying. I'd like to completely disable it from my end. I don't want pop-ups even out of combat.

[ajx]

Half the posts are talking about
Showing the name of the initiator (patch 2.2)
Making it unusable in combat ( upcoming - no ETA given)

Whereas the post was only about making a cooldown of some sort out of combat .

Jus sayin in case no one has noticed