As far as I know changing sys_ticrate on a live server does literally nothing than changing the cvar's value, but maximum FPS is still the value that the server was started with if the command line contains -sys_ticrate.
But if you have access to the starting line that actually launches the hlds process, you can change the -sys_ticrate to +sys_ticrate (yes, change the hyphen to a plus symbol), after that you can change the sys_ticrate value that will really change the server FPS maximum limit.
To test this, for example:
Start server with -sys_ticrate 300, then type stats in the console
You will get the following:
Quote:
stats
CPU In Out Uptime Users FPS Players
58.51 0.00 0.00 3 0 300.70 0
|
Type in console sys_ticrate 150, but you will still get 300 as current server FPS if you type stats again.
Now stop your server and start it with +sys_ticrate XYY and the command's value will directly affect the server FPS as you set it.
In the case you don't have access to your server's startup line, then you can't change the real FPS, but the cvar's value only.
Why do you use AMXX_VERSION_STR as your plugin's version?
This isn't an official plugin that comes with the package, you should do normal versioning.