System to curb Ready Check abuse?

[Kluya15]

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.

2.3 is around 4 months from now. It really takes that long to limit how often someone can do a ready check?

[KogaDrake]

I'd rather simply not have ready check if its not done right. ready check is to see if everyone is here and ready to start. not use in battle, not be spammed, all click yes, no up for a min or longer, someone not there, wait 15sec before try to ask again, you know who was away so you have party chat or voice to see when they return...

[Namasu]

If the dev can't fix this by 2.25 then might as well remove the feature until 2.3. We can deal with manually typing "are we ready?" and wait for everyone to reply but dealing with trolls who spam ready check is just not acceptable for another 3~4months.

[Mcshiggs]

If the dev can't fix this by 2.25 then might as well remove the feature until 2.3. We can deal with manually typing "are we ready?" and wait for everyone to reply but dealing with trolls who spam ready check is just not acceptable for another 3~4months.

I like this, if they didn't think ahead that this would be abused in the way it is, they aren't doing their jobs as developers, you have to design content with the intention that players will abuse it any way they can, otherwise they have no excuse for leaving out things like parsers, because you know players will abuse them to make it difficult on others. They need to start thinking out their content, finish it, run a test server if you have to, before they release it half done, then instead of working full time on new content having to devote so many people to fixing the things they didn't plan for, I know there will be some things that can't be foreseen, and minor bugs, but so much they have released seems rushed and unfinished with casual forum responses about how they will get to it later.

[Ed_N_Ants]

I love the ready check... That"s how I check for AFKer's during fate parties... I don't mind helping people out, but i'm not about to give them free food... Had 3 of them just last night, they join the party stash their character and then go AFK...

[Lucke]

snippy snippy

What makes matters worse is this isn't their first rodeo. They have experience with MMOs: they developed XI. They're also a AAA company. A lot of things they do and decisions they make seem VERY amateurish. Leaving out STANDARD functions of the genre until later in the game's life just perplexes me. SE shouldn't be releasing half done stuff. They're better than that.

By the way, when I tank, I only use the ready check before a boss. I agree with a limit, maybe there can only be like 3 ready checks available, or each person can initiate a ready check once per dungeon.

[Ninix]

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.

Four months to add what amounts to "if (!inCombat) InitiateReadyCheck()". Seriously?

Obviously I know it's not as simple as that, but there is no way you can convince me that something like this will take so many engineering and QA man-hours that it will take 4 months to ship.

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

Shhh, they have priorities. I really don't know what I would do if I couldn't earn the trust of another NPC in the MSQ. I would like faint.

Their priorities suck. People can use it to harass their group, and the worst part is you don't even know who is doing it so you can votekick or report them. It can seriously diminish the enjoyment of the game if you get some random idiot in your group who wants to spam it. That should be very important to them.

Good priorities would be to have this in as a hotfix before 2.2.

[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