Idiot typing misspelled wallhack commands

[Zeppelin]

Were you wiggy?

wiggy is master-jiau

heheh

[|iR|Focalor]

gl_ztrick is not a wallhack command.

Yes, it is. Why the fuck do you think I posted this? This ain't my first rodeo.

[fdrjk]

In itself, it is not a wallhack cmd. People can use it for toggling some wallhacks, though.

[|iR|Focalor]

So you're more inclined to think that someone using that command on a Quake2 server is NOT attempting to use a wallhack?  It's a shame you weren't made an admin when you asked for it.

[fdrjk]

In fact, I am. Setting your gl_ztrick to "1" will not do anything, and, in itself, will NOT make you see through walls.

In fact, to test this, I played a whole game on vanilla with my gl_ztrick set to "1", and I couldn't see anything different if I had set it to 0, let alone seeing through walls.

It's a completely useless cmd that's supposed to fix an already fixed bug; and in some exceptions, people use this useless cmd for toggling wallhacks on and off. In that case, yes, it would TOGGLE the wallhack, not be the ACTUAL wallhack. But like I said before, that's implying people have it set up like that. In any other cases, it's just a useless command.

If anyone's trying to use it, they're most likely unsure of what it does. However, since the accused is located in Poland (Wallhack capital), I could see how he would be trying to toggle a wallhack.



 

[Zeppelin]

In fact, I am. Setting your gl_ztrick to "1" will not do anything, and, in itself, will NOT make you see through walls.

I have it set to 1.
I think its set to 1 by default on r1q2.

 

what foc is saying, is probably you need that cmd to toggle the wallhack, maybe?
first time i see that cmd, so i dk

[fdrjk]

See? You're not exactly sure of what it does.

My default for the command is "0", but like I said, it doesn't make any difference.

[console]

gl_ztrick is a clever but obsolete hack to avoid clearing the z-buffer between frames. 

It used to provide a potential performance boost on early GL cards.

Unless your video card is something more than a decade old, there's no benefit to enabling gl_ztrick, and indeed enabling it is more likely to decrease performance on modern cards if anything.

Once gl_ztrick became obsolete, some wallhack developer decided to use it instead as a flag to toggle the wallhack.

So yes, in the present era I'd view any random player trying to fool with gl_ztrick with extreme suspicion.  (And  )


Regards,

[Zeppelin]

Unless your video card is something more than a decade old, there's no benefit to enabling gl_ztrick, and indeed enabling it is more likely to decrease performance on modern cards if anything.

should i turn it to 0?
since its 1 by default i allways had it enabled

[fdrjk]

It used to provide a potential performance boost on early GL cards.

Unless your video card is something more than a decade old, there's no benefit to enabling gl_ztrick, and indeed enabling it is more likely to decrease performance on modern cards if anything.

Once gl_ztrick became obsolete, some wallhack developer decided to use it instead as a flag to toggle the wallhack.

 

[console]

should i turn it to 0?
since its 1 by default i allways had it enabled

It's zero by default. 

Line 1008 of reg_gl/gl_rmain.c:  gl_ztrick = ri.Cvar_Get ("gl_ztrick", "0", 0);


Regards,

quadz

[Zeppelin]

nvm!
i found it on my config:

gl_ztrick "1"

 

[|iR|Focalor]

I played with the stock exe for quite a while. I've never seen ANY line by default in the stock config that dealt with gl_ztrick. It's not explained in any part of the readme files or manual that comes with the game CD. Perhaps other clients besides the stock exe have it by default in a config. This guy was not using another client though. Let's not be gullible here. Anyone actively using that command in the middle of playing on a public server is obviously up to no good. Argue it all you want.

[QwazyWabbit]

The gl_ztrick variable existed in the original Q2 OpenGL code. It is in exactly the same file on the exact same line number in the original Q2 code and the r1q2 code. The default was and still is zero.
The function that evaluates it, R_Clear() in gl_rmain.c is different between Q2 original and r1q2. It was designed to manipulate the z-buffer depth, affecting the color depth and the pagination of the Z-frames of the OpenGL. It had nothing to do with walling as far as I know.

I would not be inclined to convict anyone on the basis of a mis-typed command, especially not this one unless there is stronger evidence: Demo.

[console]

It had nothing to do with walling as far as I know.

A Google search turned up what are said to be the instructions supplied with the wallhack in question.

Reading the following, it appears gl_ztrick may not have been used as a toggle, but rather that the wallhack worked best with ztrick disabled:

OpenGL WallHack by ^Franck_ (wh.dll)


Last Edition: January 21, 2000

To load wh.dll place it in q2 dir and write in console:
gl_ztrick 0
gl_driver wh
vid_restart

To switch WallHack modes press simultaneously 'P' and 'O' buttons.
4 WallHack modes:
1º: Entities Hack
2º: Super Entities Hack
3º: Transparent WallHack
4º: Wireframe Hack

Hmm... anyway...