To be fair, I do this to every game more or less. If it can be broken, try to break it so that someone notices and it gets fixed. It's an exercise in testing.
Sorry, but are you about to call exploiting "unexpected testing"? If something has an obscure way of being done and seems out-of-place, chances are the developer doesn't want you or anyone to perform that action. Unless the game in question is built around obscure methods.
And by "breaking it until someone notices" results in someone noticing. That someone being, trolls. Since you're pretty much expanding the wound sufficiently enough to be noticed, you allow people of malicious intent to pour all the salt they can into the wound.
Most developers are humans. And most humans are not omnipresent, nor are they Big Brother. And lest not we forget that the person who notices the exploit is usually not someone with the ability to fix it.
Instead of exposing the hole to everyone, which is conceived as an open invitation for exploit to most people, try talking about it directly to the owner or someone from the admin team. Not saying anything leads to your testing, good intentioned or not, be used for bad intentions and getting punished by the administration if spotted, since you never said anything about it so that they wouldn't notice.
