asofold 1510f01144 [BLEEDING] Fixes and refactoring for vertical velocity handling. ... This is not the thing (lots of yet), but it is a small step. Refactor: * Use access methods for several details on vertical velocity. Fixes: * Dont reset the current jump phase if there is vertical freedom left, because the next jump might then cause a violation. * Fix clearActiveVerVel (remainder used to clear hVel, yet unused). * Clear vertical velocity on removeAllVelocity (!). * Keep setting sfDirty if velocity is found, to prevent premature reset. Missing: * Some resetting conditions for sfDirty might be missing. * Implement an error counter increasing with velocity-add by 1.0 or slightly more , decreasing with violations, but undo violations if count is > 0.0. Use at least for vertical accounting, in order to go stricter on cheating with velocity. * Revise setting sfDirty on horizontal velocity as well. * Switch to AxisVelocity (vertical), accounting for + and -.		2015-03-29 03:19:35 +02:00
..
src	[BLEEDING] Fixes and refactoring for vertical velocity handling.	2015-03-29 03:19:35 +02:00
pom.xml	Revert module dependency versions to 1.1-SNAPSHOT.	2015-02-06 02:05:48 +01:00