Notpron Forums

but dont forget that as keeper you can catch the ball when its already in the goal, because your catch radius extends into the goal...
but when that happens it should not show "own goal"

how much will pushing the 8 units back affect when it is considered a goal? cuz it would stuck for what is now considered to be a goal to suddenly just bounce off ( i know that back when i was playing i had trianed myself to be hiting the inside of the post so that it went in if you changed that and made it so that it just bounced out that would suck cuz ppl won't know what they were doing wrong)

jue to the way the game catches the ball including ping (where the ball trail can appear behind the keep on catching jue to ping) might do something, might be made not to but in games like bombing run when it was first used for that sort of micro bug is invisible.

oh wait, is this straight after you catch or when you are holding and walk?

if i may explain this...

when the hitbox on the ball hits the goal volume at the same time as the keep this happens because the ball both belongs to the keeper and in the goal.

Technically it should be a goal, but it shouldnt be charged to the keeper.

to fix this while mapping the area between the outside of the keeper blocking volume and the outside of the goal volumes (inside the net) must be at least 1/2 the ball width.

Unfortunetally I have no idea how big that is, but it would fix the problem theoretically. If DB didnt use hit radiuses but instead used hit boxes we wouldn't have this problem because it'd be a lot harder to catch the ball and keepers would want to move forward at the attacker so they have less to shoot at.

mathematically it makes no sense
it must be some lag thing
(in curve its a map bug)
but in cube etc it hardly happens anyway

Well, either way it's gay, and it happesn in many official map, I am no expert to have any comment, but the only thing I know, it should be fixed.


-[V3]InSaNe

It happens on november too =)