Unlagged code review and to add to third party sources

[GoogleCodeExporter]

Overall description of the new feature:
1) client-prediction-errors: it seems that the parts of the opponent's body 
displayed in console you appear to hit are predicted clientside, and that 
prediction seems to fail here and then, since the console-messages the 
opponent recieves, tells about different body-parts (e.g. my console said, 
i hit 3 times legs and one time stomache -- and the enemy's console said 3 
times stomache and one time leg) - i guess the
server sees what the wounded enemy gets displayed
2) probably unlagged-code didn't get implemented properly
3) Unlagged source must be added to third-party directory in source code!
4) Total review of implementatino according to Unllaged documentation is 
required!

Variables to control the new feature:
cg_drawSGbboxes <0/1> CHEAT

Which game parts are involved:
binary?
No
game?
Yes
cgame?
Yes
ui?
No
media?
No

Original issue reported on code.google.com by igorpana...@gmail.com on 23 Aug 2009 at 7:07

[GoogleCodeExporter]

Blocked by issue 20.
Current hit system is ugly. First it has to be clean and simple.
After that adoptation of unlagged to be applied.

Original comment by igorpana...@gmail.com on 19 Sep 2009 at 3:57

• Changed state: Blocked

[GoogleCodeExporter]

Original comment by igorpana...@gmail.com on 23 Nov 2009 at 11:44

• Added labels: Milestone-Alfa1.0