Darth Kaan Posted October 6, 2002 Share Posted October 6, 2002 ...what each of these settings affect and/or do in game? seta g_saberboxtracesize seta g_saberdmgvelocityscale seta g_saberdmgdelay_idle seta g_saberdmgdelay_wound seta g_saberghoul2collision seta g_sabertracesaberfirst seta _saberalwaysboxtrace Thanks in advance for any input. Link to comment Share on other sites More sharing options...
Darth Kaan Posted October 6, 2002 Author Share Posted October 6, 2002 LOL! I guess no one knows. Nice coding forum! Link to comment Share on other sites More sharing options...
Khier Posted October 7, 2002 Share Posted October 7, 2002 i think sabertracesaber is when it is set to one it enables blocking a saber even if you are attacking and ghoul2collision im not exactly sure about, but i believe if it is set to one or two or whatever it increases the ability to hit someone, u might have heard of collision detection Link to comment Share on other sites More sharing options...
ASk Posted October 7, 2002 Share Posted October 7, 2002 Specially for you, coming from the depths of the K0D3: g_saberBoxTraceSize: defines a box size for tracing saber hits box size is controlled using these other variables: - g_saberghoul2collision makes the trace box bigger by 3 times g_saberghoul2collision enables Ghoul2 engine usage while calculating collisions, making the model bounding box very close to the model outline, instead of being just a BOX And it also makes blocks harder to execute. g_saberdmgvelocityscale: controls the knockback you experience when hit by saber g_saberdmgdelay_idle: once in how many milliseconds (or rather the units which level.time is calculated in) damage the other player if the saber is touching him g_saberdmgdelay_wound: defines the delay for dealing damage after the saber hit the player. g_sabertracesaberfirst: from a peek that I saw, it disables the tracing of saber against another saber hit. The behavior of the saber is then the same as in duels. g_saberalwaysboxtrace: forces the trace to be always as if the player is using the fast (blue) stance of the saber I'm sorry if some of these are stupid and/or incorrect, but I only took a brief glance at the code, and I have no real intention to dig deeper into these parts of the code. Hope this helped Link to comment Share on other sites More sharing options...
Darth Kaan Posted October 7, 2002 Author Share Posted October 7, 2002 Originally posted by ASk Specially for you, coming from the depths of the K0D3: g_saberBoxTraceSize: defines a box size for tracing saber hits box size is controlled using these other variables: - g_saberghoul2collision makes the trace box bigger by 3 times g_saberghoul2collision enables Ghoul2 engine usage while calculating collisions, making the model bounding box very close to the model outline, instead of being just a BOX And it also makes blocks harder to execute. g_saberdmgvelocityscale: controls the knockback you experience when hit by saber g_saberdmgdelay_idle: once in how many milliseconds (or rather the units which level.time is calculated in) damage the other player if the saber is touching him g_saberdmgdelay_wound: defines the delay for dealing damage after the saber hit the player. g_sabertracesaberfirst: from a peek that I saw, it disables the tracing of saber against another saber hit. The behavior of the saber is then the same as in duels. g_saberalwaysboxtrace: forces the trace to be always as if the player is using the fast (blue) stance of the saber I'm sorry if some of these are stupid and/or incorrect, but I only took a brief glance at the code, and I have no real intention to dig deeper into these parts of the code. Hope this helped Ask, Thank you very much, this was exactly the information I was looking for. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.