The no-consent option also carries a strong burden, and a strict condition... players must at all times be aware that their IC actions should be expected to draw appropriate IC consequences. If JoeLemming is willing to ICly walk onto a battle scene, and then remain there in the area, s/he should expect and be fully prepared to be possibly subjected to the IC happenings in the area. Being IC carries with it expectations responsibilities, the same set of conditions that are set on other players to ensure your good time. When a player is in an IC area with an IC flag set (and there really are only a few reasons for an ooc player to be in an ic area) s/he is essentially indicating that s/he is making that character available to be acted on by other IC forces, in a reasonable manner. There is simply no excuse for not expecting that.

The no-consent rule does therefore exist not as a way for a player to simply avoid IC things but as a way to prevent players from being treated unfairly by certain extreme, unreasonable IC things, and perhaps harassment as well. This is certainly not an easy convenient backdoor for whiners and cowards. If it is perceived to have been invoked in such a fashion, be prepared for strict repercussions. If you are the least bit in doubt, call a member of RP-staff before invoking no-consent. It's basically a powerful RP-tool granted to the players for their security, and like many other tools, it can be abused.