He removed all of his plugins for some reason a while back.

Best thing to do is play with your server rates. These directly effect all the players who connect to your server. You basically want to set it for the connection your server has. This doesn't always mean how fast it is capable of though as many factors can come into play. The rate settings go in your server.cfg file. They are as follows:nsv_maxratensv_minratensv_maxupdateratensv_minupdateratennRate it's self determines the maximum amount of data in bytes that will be sent to a player. Updaterate is the amount of updates (packets) that will be sent to a client. If your server is hosted by the shared server type, I.G. GameServers You will have to have lower rates set. When I used to run my own server on GS, I found the following to work great:nsv_maxrate 17000nsv_minrate 15000nsv_maxupdaterate 70.0nsv_minupdaterate 40.0nnFor the max values, you will want to lower these to the point a full server keeps good hit reg. The min values you can lower to make it better for people with slower connections to get reg. It's all trial and error. There are calculators out there to get the recommended rates but as I mentioned before, it is almost never going to be ideal but will serve as a good starting point.nnNow the next thing that will effect shot reg is your sys_ticrate. This is also something you put in your server.cfg file. This tells the server how many times it is allowed to make a complete cycle (handling players, bullets, etc. etc.). The higher this is, the more it can calculate thus being more responsive and accurate. Generally most game server hosts will lock this out, or will only allow it to go to a certain amount. Windows based copies of HLDS server suffer from the issue of no high precision timer which limits the how high your sys_ticrate can go. There are multiple apps out there that will fix this, I wrote one that is hosted on this site as well. You can even load up windows media player as it will fix this too. If you don't have direct access to your server though, you are going to be limited by your host. You may be able to ask them to set a higher sys_ticrate and they may or may not do it. Best bet is to set it to 300 and see if you can hit this. When on your server, use rcon stats and it will tell you the FPS which is how many times your HLDS is making a complete program loop per second. Don't be alarmed to see it jump around a bit, this is normal. Usually you have to view it a few times. One thing to mention though is the speed of your server's hardware. Too high of a sys_ticrate can cause it to eat all your CPU time thus causing problems. Unless you have your own dedicated box with lots of power, anything above 300 will be pointless.nnThe last thing you might want to play with are the lag compensation settings. These are:nsv_unlag 1 // Default 1 - Enables lag compensationnsv_maxunlag 1.75 // Default .5 - Increase time allowed to interpolate between packetsnsv_unlagsamples 2 // Default 1 - Make checks between 2 packets instead of 1 against originalnnThese effect how the lag compensation is handled between players. Unless you are on a LAN, you always want lag compensation on, sv_unlag. sv_maxunlag and sv_unlagsamples can be increased to help players with higher latency connections get shots in. The higher you go though the longer HLDS will take to cycle through so it is something to consider. If you don't care about higher ping players 150+, just leave the settings default.nnNow on to the clients. It is just as important that they set their rates for the server they are playing at. Almost all servers will require different rates to achieve good reg. Some servers are so horribly setup or lack the power/connection and are hopeless from the start.nnA more in depth read can be found here covering server settings I have mentioned and client rates:nhttp://www.gotfrag.com/cs/story/5577/nnAnother thing you want to do is kill off the bots. Even when bots aren't playing, I have found ShrikeBot to add some overhead to the server that negatively effects reg.nnTo get an idea of an ideally configured server, you can check out the ClanBAM server @ 64.34.171.29:27015. It is hosted on a dedicated box for maximum performance. It took me awhile to tweak the settings for the reg since we have members from all over the world and just about every connection speed/latency type out there but I got it nailed down pretty good.nnSome other random stuffn- Always stop and restart the server after making changes to settings.n- Use the Speex voice codec for in game voicensv_voicecodec voice_speexnsv_voicequality 4nIt is better sounding and uses less bandwidthn- Turn off all logging if it is on and you don't have any web based stats setups I.G. PsychoStats, HLStatsX

I'll stop by your server and see how it runs. You can start with those values then play around with them to fine tune it. Higher is always better for your maxes. The best thing to do is to set some rates you want to try then get the server full if possible or to your highest average player count and find what works best.

Choke is caused when the bandwidth limit is reached either client or server side or the system is unable to keep up. Some network cards work off of your CPU. XD Loss is packet loss, data that was sent but never received. I did just hop on your server and the reg is off quite a bit. Even running with a updaterate of 20 I was still getting about 6 choke. Something isn't right. I would inspect all installed plugins to see if there is any causing issues. Some may not report errors but are just super slow because of how they were programmed. Try disabling all third party ones and see if the choke goes away. If it does, enable them one at a time to find the culprit. Also start playing with low rates server side and let me know how it goes. I'll jump on to test as I'm available.

They would be correct.nThis hopn9 107 ms 167 ms 173 ms 0.te1-4.tsr1.lga5.us.voxel.net [213.248.73.18] nlooks to be the start of the problem. It's possible to contact them to let them know there is an issue with that router and see if they will fix the problem. Some hosts will, some won't. I've never heard of voxel.net so not sure how they will respond. Even with a bad connection, you should still be able to get good reg though. On my old DoD server, I had a similar problem but it was with Level 3 which is a major backbone. The only solution was to switch the server from Chicago to Texas in my case.

Ping looks fine. Is your comp using a wireless connection?

Good to hear. XD My ISP is just horrid, only high speed out here and they have oversold the bandwidth. Constant pings above 200+ but I still don't get very much choke or loss except in peak hours. As for the old IP, you would have to get a server running on there again and use a redirect plugin.

I did write a personal plugin that adjusted people's rates but the problem with that is it can turn out bad for other players. All the connections are different so a cookie cutter doesn't work so hot. XD

Where can I find Dr.G's plugin? Thanks.

http://www.clan-go.net/forum/showthread.php?t=9

Can anyone help me out here?, here's the error from log files, error logs size is in MB's instead of KB's:-rnrnL 03/03/2011 - 17:06:42: [AMXX] Displaying debug trace (plugin "Improved_Registry.amxx")rnL 03/03/2011 - 17:06:42: [AMXX] Run time error 4: index out of bounds rnL 03/03/2011 - 17:06:42: [AMXX] [0] Improved_Registry.sma::func_TraceLine (line 145)rnrnrnI've attached DrG's orginal Improved_Registry.sma:-rnrnAny help would be appreciated

If I remember right there are tracelines created for entities other than players so the ID may not always represent a player ID and since the array is only a size of 33, any number higher will bork out. So changing the code:nnif(chance[id] == 0)nnto:nnif(id < 33 && chance[id] == 0)nnwill fix it.nnOh and on your request basic, unfortunately I really do not have the free time to do anything. I've gotten myself deep into a myriad of large/small AMX plugins and other programming projects that I need to focus on completing. I have a bad habit of taking on too much at once which causes problems and working full time makes this process even longer for me. Also, to be honest, the boost plugin is more of a closed project for BAM to provide it's uniqueness. I can help with coding questions though if you want to attempt to make one yourself.