[ddhoward]

If the command cannot be stopped by the server, then no. Retry, quit, etc. Not sure about fov_desired, will experiment with it after work.

EDIT: nope

[deathcurse]

Great plugin, seems to be working well. Is it possible to have a command within the current config to allow us to customise the chat messages returned to the player? With colours if possible.

[ddhoward]

I, errr. I suppose so? That actually would take me like 10 seconds to implement, sure. I will not use a colors/morecolors include, however.

EDIT: I LIED LOLOLOLOLOLOLOLOLOLOLOLOLOLOL

[The_Hairy_Baboon]

Originally Posted by ddhoward Until this is added (which it probably won't be) you can set a cooldown on sm_forcertd with this plugin.

I have this in my commandCooldowns.txt file

"sm_forcertd"
	{
		"cooldown"			"40"
		
	}

yet I can continually use sm_forcertd. (i set it so noone gets the override so I don't have to adjust admin permissions)

I loaded the plugin using "sm plugins load "commandcooldowns" in the console, said it loaded fine. I've also used "sm_commandcooldowns_reload" to try and reload the file, but it still isn't limiting my usage.

The only thing I can think of is "The cooldowns do not apply to client 0." but I don't know how to check if I am client 0, and if I am, how do I prevent people who join my server from being client 0 and therefore getting around this block?

[ddhoward]

Originally Posted by The_Hairy_Baboon how do I prevent people who join my server from being client 0 and therefore getting around this block?

Client 0 = RCON. The server itself, basically. Client 0 is not a player; it is the console. Basically, an with the RCON flag admin can use "sm_rcon sm_forcertd" to get around the block, and anyone with the rcon password can use rcon to get around the block.

Your issue is likely that you did not structure your txt file correctly. Please refer to the example on page 1.

"CommandCooldowns"
{
    "sm_forcertd"
    {
        "cooldown"            "40"
    }
}

[ddhoward]

Updated to 14.0910. This update features ddhoward_updater integration, as well as morecolors compatibility. Basically, this update is entirely thanks to Dr. McKay.

Also, the KeyValues file now supports a "reply" key for each command, which allows you to customize the "you must wait blah blah" message given to clients.

EDIT: Updated again, fixed a bug I thought I fixed months ago

[ddhoward]

Updated to 14.0921. Changes include:

• Added 'flags' keyvalue to replace 'defaultFlag'. 'defaultFlag' will be removed in a future version!!!
• Added flagstring cleaning up and verification.
• Added 'reset' keyvalue to allow server ops to specify that a command's cooldown should be RESET if a user tries to use a command too early.

The next update will introduce natives and forwards for interaction with other plugins.

[ddhoward]

Updated to 14.0926. The forwards and natives will wait until a future update. This update's changes include:

• Added support for multiple commands sharing a cooldown (up to 8 commands per cooldown)
• Reduced maximum number of cooldowns from 255 to 64
• Removed "%i" support from replies
• Replies now replace "{COMMAND_NAME}" and "{TIMELEFT}" with the appropriate information
• Removed pointless RemoveCommandListener calls in OnPluginEnd
• Added "shared" keyvalue key
• Switched to using BuildPath() rather than hard-coding in addons/sourcemod/
• Updated version of ddhoward_updater used
• other minor internal code improvements

[Horsedick]

Solution to this error?

L 11/02/2014 - 13:54:27: [commandCooldowns.smx] "defaultFlag" in commandCooldowns.txt has been replaced with "flags". Please update your commandCooldowns config file appropriately.

[ddhoward]

Replace all instances of the word "defaultFlag" in the file with the word "flags". "defaultFlag" is deprecated, and will stop working in a future update.