Player collision manager module

[GoogleCodeExporter]

Since changing player collision settings might be a common task, ZR should 
have a collision manager module where anti-stick and other features would 
be sub modules.

The manager should take care of conflict handling if multiple features try 
to do something at the same time with the same player.

Features that would need conflict handling:
- Anti-stick
- No block on ladders
- Volumetric features

How this manager should deal with conflicts is a question to be answered 
here.

Some of my collision manager API ideas:

* SetCollisionMode(client, CollisionMode:mode, bool:force = false)
Sub modules uses this one to change collision, and the manager decides if 
collisions should be done or not. It will have its own enumeration of 
allowed collision modes. However there should be some way to force 
collision mode to be set (bypassing conflict handling).

* CollisionMode:GetCollisionMode(client)

Original issue reported on code.google.com by richard.helgeby@gmail.com on 2 Feb 2010 at 1:39

• Blocking: #117

[GoogleCodeExporter]

Added milestone tag. If we don't make it for the 3.0 release this feature can 
be 
moved to 3.1

Original comment by richard.helgeby@gmail.com on 2 Feb 2010 at 1:44

• Added labels: Milestone-Release3.0

[GoogleCodeExporter]

Also, the new sdkhooks has (or will) provide a new way to handle collisions.  
Maybe 
it's the long-awaited fix for physical mayhem.  It's a ShouldCollide hook where 
you can 
change what entities will collide with each other.

I'll experiment with it once it's officially released (I compiled an unofficial 
version)

Original comment by andrewbo...@gmail.com on 2 Feb 2010 at 10:48

[GoogleCodeExporter]

While I realize this is an oldish bug. ShouldCollide isn't nearly as fluid as 
one would expect (There's noticeable blocking). There's also a huge issue with 
hit registration while using this (Tested using Strontiumdog's snippet).

https://forums.alliedmods.net/showpost.php?p=1270623&postcount=128

Original comment by kyle.l...@gmail.com on 10 May 2011 at 8:22

[GoogleCodeExporter]

Should we still consider using ShouldCollide? How reliable is it? We don't 
really have many options left anyways. :P

Original comment by richard.helgeby@gmail.com on 10 May 2011 at 11:42