dUDAK_mURAK wrote:Thanks for clarifying what was going on with the database though and next time you guys test an exploit try to be more discrete, imagine how awkward it is if it's not an easy fix or has no immediate solution, other people might find it ;(
Usually good to test 1 or 2 times, not 10-15 (;
And you are not dumb man we love ya defragger
Under most circumstances, we are discrete enough. We have found and reported bugs regarding the mdd servers discretely before. This time it was partially not our fault that we weren't discreet. Nor was it partially our fault that it logged a hella lotta times. Most of the tries were due to the initially seeming random factor of the bug, and another significant chunk of it was us trying to eliminate the randomness to be able to consistently reproduce the bug. Of course, I am not going to deny that some of us had a bit of fun with the bug that day. However, it was mostly good natured fun though.. If you noticed we mostly used fake map(s), and fake modes that will not disrupt the official rankings. Then there was palmslane... (what can we do? OptionalBob was just too godly)
Anyways, even before you guys started to bring the issues (mostly non-intrusive ones -- excluding palmslane) we caused to light, we had messaged hk regarding the problem, how to revert our foolish attempts, and possible reasons and ways to fix the problem. In my opinion, the way we acted was quite responsible. This is more than I can say for some people who were faced with similar situations.
If you guys want our accounts banned, sure go ahead and tell the admins to do so. We very well knew that this may be a consequence. But, please make sure not to delete backwhen's account cause that poor soul had nothing to do with this apart from having bad luck