Quote Originally Posted by BillyKaplan View Post
1. A single occurrence is not enough to report someone and no player will have the necessary information. All this'll do is likely make more work for SE.
2. You are once again targeting the innocents who legitimately have bad connections. Whether or not they should be playing a game like this to begin with is a question in and of itself, but it's not like we're discussing Savage here, just ARR MSQ.
...
I retort saying, that we have to report this now.
Because the exploit was found and the information has been made publicly available.

The means to exploit it was even linked in this very thread!


The people who have made this exploit public knowledge are to blame for any extra work the GM's have now because of this.
As this exploit blatantly goes against what the devs intend for these dungeons.


Quote Originally Posted by kikix12 View Post
When logging sometimes, I repeatedly get disconnected after each few minutes. And it usually happens right after a pull starts (you know, more data sent/received). And it's not my problem. It's the connection between me and server, or servers. I can play perfectly fine usually (as far as the connection goes, anyway) and the game never says that my connection is any worse than "Good", often being "Excellent".

Square would need to invest in both their own infrastructure (frequent DDoS attacks, countless bottlenecks, servers over capacity etc.) as well as location to one that have better connection worldwide (California is in such a place, that its connection to other countries is crippling any game located there for players from other continents). Neither of these will happen, so you can be certain that players will be banned for no fault of their own.
The people exploiting this will be doing it at specific points in the dungeon, when the longest cutscenes are beginning, not on a pull, and not multiple times in rapid sucession.

The pattern will be if a specific player keeps having it happen at these specific points over multiple runs.

And the only way SE will be able to so anything about is if we let them know.
Sure, they may have more reports to go through, but as I said...
That extra workload is the fault of the people spreading this exploit.

The linked instructions even show what points are 'most efficient' for using this exploit.