<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance. It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1.
<!--QuoteBegin-Iron Maiden+Jul 28 2005, 09:51 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Iron Maiden @ Jul 28 2005, 09:51 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> 1) Is there anyway to prevent the animations from the attack? 2) Is it legal? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> 1) Yes. 2) No.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance. It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> If it's locked at 1, why does CAL see it as an exploit?
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance. It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> If it's locked at 1, why does CAL see it as an exploit? <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> Because it is one. Isn't that like asking "If the bank vault is sealed why is it illegal to rob?!?!!"?.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance. It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> If it's locked at 1, why does CAL see it as an exploit? <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> Because it is one. Isn't that like asking "If the bank vault is sealed why is it illegal to rob?!?!!"?. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> I think you misunderstood: if you can't change it to 0, then why is it a rule for CAL to have it at 1 if it's locked? Hey, let's make up a rule where you can't change something thats locked. Pointless.
Perhaps CAL say that to offer an explanation to why it is locked? Besides, their rules tend to preceed the locking of settings. (In fact they tend to directly preceed them.)
Therefore it is likely that CAL created the rule, NS devs locked the variable, and CAL saw no reason to remove the rule. That's the best explanation I can offer.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance. It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> If it's locked at 1, why does CAL see it as an exploit? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> There is a way around consistency. That would be reason enough to keep the rule.
Comments
No. Just no.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance.
It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1.
2) Is it legal? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
1) Yes.
2) No.
End of discussion.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance.
It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
If it's locked at 1, why does CAL see it as an exploit?
And if you get used to it, it's gives little or no problem.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance.
It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
If it's locked at 1, why does CAL see it as an exploit? <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Because it is one. Isn't that like asking "If the bank vault is sealed why is it illegal to rob?!?!!"?.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance.
It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
If it's locked at 1, why does CAL see it as an exploit? <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Because it is one. Isn't that like asking "If the bank vault is sealed why is it illegal to rob?!?!!"?. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
I think you misunderstood: if you can't change it to 0, then why is it a rule for CAL to have it at 1 if it's locked? Hey, let's make up a rule where you can't change something thats locked. Pointless.
Therefore it is likely that CAL created the rule, NS devs locked the variable, and CAL saw no reason to remove the rule. That's the best explanation I can offer.
<i>r_drawviewmodel 0</i> does this I think, but it's illegal in CAL. If you don't play in CAL, however, then go crazy with it. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
It's been locked as 1 for ages; the skulk teeth view obstruction is part of balance.
It's possible to disable them, but I'm not going to be the one to give details. Besides, it's impossible if sv_consistency is 1. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
If it's locked at 1, why does CAL see it as an exploit? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
There is a way around consistency. That would be reason enough to keep the rule.