04.11.2009, 05:43
This is just awesome, the coolest thing i've ever seen on samp 
Some suggestions:
A 20 ms timer is a lot of work for the server. Let's say that a object is 16 byte (x+y+z+ID), in 1 second it is fired 50 times so it is a 800 byte load for every ball.
With 15+1 balls.... 12,8 kb/s for every player for the server.
It's a LOT!
So try to do this:
1)Update only the balls that need update (the ones that are moving)
2)I think that you can use a 50 ms timer
3)Let more the client move the objects, cause i think it can predict movements by itself

Some suggestions:
A 20 ms timer is a lot of work for the server. Let's say that a object is 16 byte (x+y+z+ID), in 1 second it is fired 50 times so it is a 800 byte load for every ball.
With 15+1 balls.... 12,8 kb/s for every player for the server.
It's a LOT!
So try to do this:
1)Update only the balls that need update (the ones that are moving)
2)I think that you can use a 50 ms timer
3)Let more the client move the objects, cause i think it can predict movements by itself
