I believe there is a problem with the glitching rule as it is for the moment. Have a look:

14. Cheating is not allowed, which is why it is called cheating. Glitching is also a form of cheating.

And the rule goes on by describing what glitching is and that is not the problem. The problem is that the rule sais nothing about cheating after this, and I do not mean that it does not mention it, rather that a lack of definition troubles me. Therefore we have a rule that quite effectivly gives a clan the oppotunity to get replays of every match and "scan" for a hint of glitch. And this hint is by the rules defined as a cheat, and the cb is lost or tied. But what if the glitch was in no way intended? What if it had no effect on the battle? What if a person is not inwolwed in the fighting, and perhaps far away from the match? And how long does it take to make it a glitch(there is actually a few of us who still can't hit the damn right button )?Oh we can argue all night long, but I don't intend to. I have a suggestion for a definition, and it is up to the admins if they want to include it or not, but I think it would be helpful for the admins as a tool to decide.(and if this definition goes into use, you might just be able to do what you are suposed to do, instead of looking at replays all the time. So....here goes:

The definition of cheating should be: Cheating, when it comes to glitching, should be wiewed as a intentional or unintentional abuse of the glitching problem in ghost recon(as described in the rule 14 in the damn bl rules) to gain an unfair advantage for you and/or your clan that has an influence on the actual events of the game.

This is only a draft and feel free to polish it. But there is one more thing.
   
- don't prone in craters. Although not the complete craters are a glitch you shouldn't prone in craters to prevent misunderstandings.(taken from rule 14.)
 
This line should be rewritten...is this a rule or advice? It is very unclear.
All this is my personal oppinion, so use it or not.....I just wanted to say it out loud...but I hope you will consider it.

I agree.  The rule should be as vivid and explicit on this already vague topic to avoid further misunderstandings.  

Yeah, I always assumed that a glitch was the issue where someone couldnt be shot but was shooting.  I mean I am not sure that laying in a ditch if you are not shooting is a glitch because that is why the ditches were there.  It's when you take advantage of the ditch by glitching trying to shoot back at the attacker.  that is when the issue applies.  So when you say that there are different opinions there I fully agree Civic.  There is.  I mean what if you had to suddenly step away from the console but you didnt want your guy to get shot, so you go prone in a ditch while you are afk.  I do this all the time to stuff my face for instance while in Multiplayer games.  Is that considered glitching, cause I stepped from the Keyboard and went afk to stuff my face with food?  See that is not glitching, but someone could construe that as a glitch.

A glitch should be defined as the idea of wanting to get an unfair advantage while knowing u are in a glitchy situation.  By that definition it should be considered illigal and cheating.  So the only time that should be an issue with reviewing a round is the determination if the glitch was intended or not.  It should be gone thru in this order:

1.  When was the glitch reported?  Was it reported at the appropriate time?
2.  Was it a glitch?
3.  Would the glitch have affected the game outcome?
4.  Was the glitch intended?
5.  How serious was the glitching that was done?
6.  Does the offender admit to the glitch?
7.  What punishment, if any, should be given?

If this order is followed it should be easy to determine how to deal with a possible glitch.  Although no idea is fullproof when it comes to the infamous glitch.  But this is just a simple plan on how to determine guilt in a "POSSIBLE GLITCH SCENARIO."

I whole-heartidly agree with Brutha on the fact that something should be done with the specifications on either how a glitch should be handled, or the clear specifications on what exactly is considered a glitch.  

:MoD:Saberian

Lone.. This issue has been brought up due to a prob that the admins just dealt with. Brutha has some good points that he wants clarified. Brutha just wants to make it more clear so that other clans dont try to use this as a cop out to get wins if it is not an actual rule (just advice). Us admins will talk to mauti and see how he wants to word it to make it more clear.

Well...what we can establsih now is that there are rules to prevent clans from abusing the replays by demanding a reason for getting the replays...Sure it is a good idea, but what is keeping the clans from saying that they believe they observed a glitch and then say "sorry we were wrong" when the admins are finished with looking at the replay? The thing is that perhaps it is time to perhaps give warning points for that kind of behaviour as well. Perhaps then the admins will be able to do what they are suposed to do with their time, instead of looking at replays every day. And the players will not go around and wonder if their cb will confirmed, or if they have to play it again. I hope(and believe) that you guys want to spend some time in your real life as well(I know I do)......you cant live on forums, chips and coke alone you know Again..this is my opinion, and I have to admit...I am an idealistic naiv little fool(although those of you who have seen me might say nooo...little?)

yeah...well and good on us....but there are those bastards out there who can really ruin the fun in a game by doing this. For them this is life and death....and not only in game. So trike down while you can and rid the battle league of this problem.