Quote Originally Posted by kikix12 View Post
Of course it was an exploit. Not because of turning off the game or anything, but because it used an in-game flaw to achieve something that the developers did not intend. You submitted the same score multiple times through the flaw of the IN-GAME code, the flaw of it saving the scores that are not submitted properly...but also stacking them. The exploit begun before you even turned the game off.

That and this are two different things. Complain all you want, but "semantics" are extremely important in any kind of clash of interests. Semantics are what can make or break a court case. You cannot dismiss them just cause you think that "If they do something that I don't want them to do, it must be an exploit". I never said that what they are doing is "good". But I did say that technically speaking it is not an exploit, therefore they cannot be banned for what they did up till now. It will become an exploit if the developers will find a way to deal with the problem (like counting the run-down of the cutscene even when someone is disconnected) and players will somehow manage to dodge that, because at that point they should not have normally access to the system they are using now.
1. It is a flaw in the ingame code, it just happens to be the code that runs after a disconnect.

2. It's not 'them doing something I don't want them to do', it's them doing something the devs don't want them to do.

3. Exploits don't only become considered exploits once they've been addressed by the devs.

4. Exploits don't need to be fixed prior to devs being able to punish for their use.

5. Even if not considered an exploit, they could still be pegged under disrupting other player's experience by forcing newbies to not get to experience the dungeon as the devs intend.