Gl_max_size 1
coris
Join Date: 2003-07-08 Member: 18034Members, Constellation
<div class="IPBDescription">..</div> Maybe CAL should update their rules with some unallowed cvars, because there are quite some that give you an unfair advantage.
(s_show 1 if that hasn't been removed etc).
gl_max_size 1 pretty much gives you white walls (but a ****edup crpsshair)
(s_show 1 if that hasn't been removed etc).
gl_max_size 1 pretty much gives you white walls (but a ****edup crpsshair)
Comments
<a href="http://www.lol.com/co_core_gl_max_size_1.png" target="_blank">Example</a>
But thats cumbersome, and I agree that this along with the AMX mod to lock minimum rate and cl_cmdrate are really, really necessary for CAL.
But thats cumbersome, and I agree that this along with the AMX mod to lock minimum rate and cl_cmdrate are really, really necessary for CAL.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
In regards to setting monitoring from serverside: As far as I know there is no way of monitoring these commands as they are not sent to the server. Only a select few are actually sent (approx. 10 from what I can recall) So to enforce settings/rates the only way to do it would be to force one certain number.
I had attempted to do this with cl_cmdrate a while ago but those with poor connections had lagg issues.
But thats cumbersome, and I agree that this along with the AMX mod to lock minimum rate and cl_cmdrate are really, really necessary for CAL. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
You dont even have to restart half-life, all you need to do is reconnect to use the command retry. The changed settings will also apply after a level change. And yes this can be abused, but let them do it.
If people feel like using green alien models, haxed gamme and no sprites/textures let them do so. It only takes away the atmosphere.
If we can create an exact list of all exploitive commands and how they are used to exploit in this game, Id like to submit a nice long formated thread to the NS Bug forum.
If we can create an exact list of all exploitive commands and how they are used to exploit in this game, Id like to submit a nice long formated thread to the NS Bug forum. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
There are no exploitative commands in natural-selection.
But it's all about perspective isn't it?
Very, very sad.
Very, very sad. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
You can compare this to cl_cmdrate if you like, both have valid purposes when being adjusted,however both can be put to values which are "exploitative" where does one draw the line?
Attempting to rationalize textures/models/graphics procedures like what is shown in this thread makes me cry IRL.
gl_max_size 8 is pretty much the same though. I wouldn't mind a block for any value lower than 128.
<!--QuoteBegin-DragonMech+--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (DragonMech)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> Just lock gl_max_size to a value of 128 (low end machines), 256 (average machines), or 512 (high end machines). If it's set to a value other than one of those, just adjust it to the nearest value.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
sounds good to me.
Totally and completely <b>AWESOME!!!</b>
You guys outdo yourselves just being yourselves.
I so want to abuse this.
And XTC...I'm telling everyone! lol <!--emo&:p--><img src='http://www.unknownworlds.com/forums/html/emoticons/tounge.gif' border='0' style='vertical-align:middle' alt='tounge.gif' /><!--endemo-->
If we can create an exact list of all exploitive commands and how they are used to exploit in this game, Id like to submit a nice long formated thread to the NS Bug forum. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
I agree, but lets please not do so on NS general compeditive discussion forum, as until things are fixed this just means a whole bunch of annoying as hell hacker wannabe kiddies playing with thier configs to screw over the game for everyone else, simply because we are posting exploits in a publicly accessable place.
seriously, why hasn't this topic been moved to a private section in the bug reports forum yet? that is common protical for exploitive things like this.
<!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Screenshots are pretty much useless unless you require people to have net_graph activated since you COULD record a demo that you view after the game with normal cvars / models.
<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Maybe because most people play the game for atmosphere or fun and not cause they are addictet to seeing white walls.
A small question:
Player "I pwn you all u dumb n00bs" uses an extremely tweaked config, with every exploit imagineable used to its full extent, but still he does not score as high, as the average "skilled" player.
Would you notice, that he is using exploits?
Would you care?
Does it reduce the fun, you are having while playing?
<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Maybe because most people play the game for atmosphere or fun and not cause they are addictet to seeing white walls.
A small question:
Player "I pwn you all u dumb n00bs" uses an extremely tweaked config, with every exploit imagineable used to its full extent, but still he does not score as high, as the average "skilled" player.
Would you notice, that he is using exploits?
Would you care?
Does it reduce the fun, you are having while playing? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Does it still make it right?
After certian events that were uncovered in one of the comunities I regular in (you know what I am talking about if you were there, I'm not going into it further) I am quite aware that varionions of this exact thing are more common then most people would imagine. The thing is, most players simply don't want to play against hackers/exploiters.
If I am getting owned, I don't want the person I am getting owned by to be hacking/exploiting. It is not fun to lose, and if someone is not using unaided skill in order to beat you, then they are fooling themself about thier ability to win, and I am playing unfun games against someone who is worse then me just because they figured it would be fun to exploit the game in unethical ways that I am not.
If I am owning, I don't want to be playing against hackers/exploiters. People who hack and exploit don't tell you they are doing it before you start a match with them. If I can get a 40:15 killscore against a hacker, that would be pretty good, but against a normal nub it would be much less satisfying since I know from experiance I am capable of getting 40:5. If I know the player I am playing against is hacking before they start the round I am more aware of what to expect when I am playing against them, and I am more prepared to counter it. If I don't then they have taken the heads up on me simply because I am ignorant of what they are capable of, yet me, not being a hacker, they are more then able to predict the actions of.
This being a majorly exploitable bug should not be publicily available information, If I am going to cloak in game I want to know/belive that the function is working properly against the people I am playing against. If not, I want to know that too, so I just don't do it. If another player is hacking or using an exploit such as this, they take away my ability to know, and thus they should not be allowed to continue doing it, and the information about how it is done should not be publicly scattered/availible.