If you have found a exploit, use the /bug command, also go to the forums and send a private message to one of the devs to let them know about it. And just to make sure that you covered all bases, and you used the exploit a couple of times just to see how it worked, ccr yourself explaining how the exploit works, so the CSR will know how it is done and what to look for.
And I do believe this needed to be brought to the attention of everyone, and the easiest way was the looking glass. cause not everyone reads through the forums.
LuciousBrujah wrote: And just to make sure that you covered all bases, and you used the exploit a couple of times just to see how it worked, ccr yourself explaining how the exploit works, so the CSR will know how it is done and what to look for.
And just to make sure that you covered all bases, and you used the exploit a couple of times just to see how it worked, ccr yourself explaining how the exploit works, so the CSR will know how it is done and what to look for.
I cannot stress enough that /bug needs to have AT LEAST an auto-reply letting you know that it was received by the system. Right now the submit button may as well be a close window button. Ideally you would have someone whose job it was to read every bug report and categorize them by type and severity and then forward to the appropriate testers/developers. Right now we haven't a clue what happens to /bug reports. Perhaps a blurb explaining the path of a /bug report would be good? Last thought, aren't there some more privileged community members out there who can help fasttrak severe bugs???
