"jumped too high" kick in 2.1.11

[tadd]

Code: Select all

Kicking Player Morfeusz_pl [2] jumped too high [max: 36.548470 height: 36.700001]
Kicking Player Morfeusz_pl [2] jumped too high [max: 44.548470 height: 44.759998]
Kicking Player tadd [0] jumped too high [max: 29.148468 height: 53.740002]
Kicking Player tadd [0] jumped too high [max: 32.548470 height: 45.939999]

Is there a way to disable this auto-kick? It seems to happen pretty often.
Tadd

[blast]

Code: Select all

Kicking Player Morfeusz_pl [2] jumped too high [max: 36.548470 height: 36.700001]
Kicking Player Morfeusz_pl [2] jumped too high [max: 44.548470 height: 44.759998]
Kicking Player tadd [0] jumped too high [max: 29.148468 height: 53.740002]
Kicking Player tadd [0] jumped too high [max: 32.548470 height: 45.939999]

Is there a way to disable this auto-kick? It seems to happen pretty often.
Tadd

Rather than disable it, the height check should be fixed. What is the exact situation that this is happening? (What flag, map, modified BZDB variables, etc)

[ts]

How recent is the build? I changed the check to be disabled when a map uses physics drivers at Saturday.

There is also a way to turn it off, however I would rather want to fix it. For the final release build I would be willing to turn it off by default but as it's currently unstable, I'm looking for people reporting reproduceable problems.

[tadd]

BZFlag server 2.1.11.20070127-DEVEL-darwin8.8.0-SDL

I'm using the client from the same build.

THere was no flag involved but it did involve the tank running over a mesh face that had 'physics' to toss the tank up in the air.

Tadd

[blast]

Yeah, ts made the change rather recently. You should upgrade your source and rebuild.