[xPaw]

Originally Posted by kielor How can you prove the detection other way? It works and it is perfect, dunno why?

What?

[kielor]

Originally Posted by xPaw What?

The thing I wanted to tell you is that it's not good when you code something and dunno how and why it works. You know why your detection works? I guess not.

Kthxbai pr@ c@der.

[xPaw]

Originally Posted by kielor The thing I wanted to tell you is that it's not good when you code something and dunno how and why it works. You know why your detection works? I guess not. Kthxbai pr@ c@der.

Boy, you can go rage somewhere else.

[EXteRmiNaToR]

Originally Posted by kielor The thing I wanted to tell you is that it's not good when you code something and dunno how and why it works. You know why your detection works? I guess not. Kthxbai pr@ c@der.

I really can't understand what your problem is...
Nice plugin xPaw!Tested it and works nice!

[kielor]

Originally Posted by xPaw Boy, you can go rage somewhere else.

Lolwut? You didn't answer and tell me that I'm a boy? Fail, oh fail.

[vato loco [GE-S]]

Originally Posted by kielor and tell me that I'm a boy? Fail, oh fail.

are you a girl

[xPaw]

New version 2.1

• Removed "beam", because it takes useless calculations to find perfect origin
• Removed duck detection and use AbsMins instead
• Added trigger_teleport reset
• Fixed hudmessage show to spectators
• Slightly lowered memory usage

[xPaw]

New version 2.2

• Removed const of 0.4 in formula and replaced with gravity calculating

  EdgeBug stats are now working with any gravity

• Fixed trigger_teleport touching
• Corrected jump off detection
• Added forward: kz_edgebug for plugin developers

  Someone can make Top15 using this forward

[kielor]

Now it's far much understandable. But still are some bugs:
- as far as I remember you should calculate velocity[2] with 2 frames earlier msec and not one (but dunno - check this better to avoid bugs with laggers like me)
- Touch bug (read below)

Here's what I use:

 ebstats.sma (61.0-63.170):
    if(g_bFalling[id]
    && floatabs(fPrevVelocity[id] - g_iFrameTime[id][1] * iCvarGravity * fGravity * 0.001 - fVelocity[2]) > EPSILON // strange vertical movement
    && floatabs(fVelocity[2] + 0.5 * iCvarGravity * fGravity * g_iFrameTime[id][1] * 0.001) < EPSILON) // almost equal, have to use epsilon due to shitty float roundings

On some maps there's a bug with Touch, it isn't called when two "touches" are made - one to the ground and second to some entity like healer. With this code you don't have to use Touch hook.

[xPaw]

Originally Posted by kielor Now it's far much understandable. But still are some bugs: - as far as I remember you should calculate velocity[2] with 2 frames earlier msec and not one (but dunno - check this better to avoid bugs with laggers like me) - Touch bug (read below) Here's what I use: ebstats.sma (61.0-63.170): if(g_bFalling[id] && floatabs(fPrevVelocity[id] - g_iFrameTime[id][1] * iCvarGravity * fGravity * 0.001 - fVelocity[2]) > EPSILON // strange vertical movement && floatabs(fVelocity[2] + 0.5 * iCvarGravity * fGravity * g_iFrameTime[id][1] * 0.001) < EPSILON) // almost equal, have to use epsilon due to shitty float roundings On some maps there's a bug with Touch, it isn't called when two "touches" are made - one to the ground and second to some entity like healer. With this code you don't have to use Touch hook.

Your first floatabs is not needed in my code because i have similiar but simpler part already.

floatabs( g_flTouchedVelocity[ id ] ) > iPossibleGain