System to curb Ready Check abuse?

[Johnist]

While I don't have this trouble so far (may because luckily I'm on JP server), but around 2.3 (which means 3 month later) for such an anti-abuse feature? Seriously?

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.

[Giantbane]

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.

God I hope you're being sarcastic.

If either:
checking for combat before initiating the ready check
or
displaying the person's name who initiates the ready check

amounts to a lot of code, then their programmers are worthless and should be fired immediately

[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.

[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.