[sneaK]

Another question here. I have a section setup for dealing with racism. However, if a person types in a specified word twice in one sentence, it automatically skips action #1 and goes straight to #2. How can I avoid that?

	"limit1"	1
	"action1"	"sm_psay #userid \"Please do not use racism here!\""
	"limit2"	2
	"action2"	"sm_psay #userid \"If you continue using racist language here, you will be banned on your next offense!\""
	"limit3"	3
	"action3"	"sm_ban #userid 4320 Auto-banned for repeated racism"

Mode is 4, penalty is set to 1.

Also, completely unrelated, is it possible to add cooldown as an option? For example, cooldown for an action or replacement? Closest I see so far is probability.

[almostagreatcoder]

Originally Posted by blackhawk74 Another question here. I have a section setup for dealing with racism. However, if a person types in a specified word twice in one sentence, it automatically skips action #1 and goes straight to #2. How can I avoid that? "limit1" 1 "action1" "sm_psay #userid \"Please do not use racism here!\"" "limit2" 2 "action2" "sm_psay #userid \"If you continue using racist language here, you will be banned on your next offense!\"" "limit3" 3 "action3" "sm_ban #userid 4320 Auto-banned for repeated racism" Mode is 4, penalty is set to 1.

I'm not quite sure, since I couldn't test it - but using mode 3 should do the trick.

Also, completely unrelated, is it possible to add cooldown as an option? For example, cooldown for an action or replacement? Closest I see so far is probability.

That's an interesting idea and could totally be possible. But what would you expect to happen if someone triggers a certain action with the cooldown time not passed yet. Nothing? (Which would be odd if you try to prevent some unwanted behaviour in the chat.)

[sneaK]

Originally Posted by almostagreatcoder I'm not quite sure, since I couldn't test it - but using mode 3 should do the trick.

Hey, I prefer to use mode #4, because if I use mode #3, the message shows up as a blank sent message to everyone in the server. I discovered indeed that Mode #4 causes this issue.

I messed around with my config and this is how I consistently "skipped" action #1, using mode 4.

My test config:

Spoiler

"Test"
{
	"section id"	1
	
	"limit1"	1
	"action1"	"sm_psay #userid \"Detection #1\""
	"limit2"	2
	"action2"	"sm_psay #userid \"Detection #2\""
	"limit3"	3
	"action3"	"sm_psay #userid \"Detection #3\""

	"keep penalty"	0
	
	"Test-Words"
	{
		"mode"			4
		"penalty"		1
		"find"		"pleb"
	}
}

How to reproduce:
1. Use this config or similar
2. Type in chat (without quotes): "pleb pleb" or "pleb i am a pleb" or even "pleb test pleb test pleb" (note that the word to be found was used 3 times)
3. Every single time, detection #2 is popped at the very first.

Mode #3 did not have this issue.

Originally Posted by almostagreatcoder That's an interesting idea and could totally be possible. But what would you expect to happen if someone triggers a certain action with the cooldown time not passed yet. Nothing? (Which would be odd if you try to prevent some unwanted behaviour in the chat.)

Here's an example of what I was hoping to accomplish with "cooldown" - sometimes players wish to get information about the server, or other features that may be available. For example, the player wishes to know what the IP is to Teamspeak - so they can type !ts, and get responded to with the IP address. However, adding cooldown would be helpful as to avoid spamming, since in some instances it would be broadcast to the entire server, instead of just the user.

[ChoclatePancake]

How would i go about setting this up for synergy?

[almostagreatcoder]

Originally Posted by blackhawk74 Hey, I prefer to use mode #4, because if I use mode #3, the message shows up as a blank sent message to everyone in the server. I discovered indeed that Mode #4 causes this issue.

Oh - you are right. Using mode #3 resulted in blank lines in the chat. This was not the intended behaviour - it was a mistake in the code.

I just now released a new version (1.0.1) of the plugin. Using it should eleminate your problem. Just use mode #3 and everything's fine!

[almostagreatcoder]

Originally Posted by blackhawk74 Here's an example of what I was hoping to accomplish with "cooldown" - sometimes players wish to get information about the server, or other features that may be available. For example, the player wishes to know what the IP is to Teamspeak - so they can type !ts, and get responded to with the IP address. However, adding cooldown would be helpful as to avoid spamming, since in some instances it would be broadcast to the entire server, instead of just the user.

I see! I just wonder: wouldn't sourcemod's antiflood feature do exactly what you want? If you take a look into the sourcemod.cfg file (located in [game folder]/cfg/sourcemod/):

// Specifies the amount of time that is allowed between chat messages.  This
// includes the say and say_team commands.  If a client sends a message faster
// than this time, they receive a flood token.  When the client has accumulated
// 3 or more tokens, a warning message is shown instead of the chat message.
// --
// Requires: antiflood.smx
// Default: 0.75
sm_flood_time 0.75

Or do you think it would be useful to have a separate cooldown timing for the chat triggers you described in your example?

[almostagreatcoder]

Originally Posted by ChoclatePancake How would i go about setting this up for synergy?

I'm sorry, I don't have a Synergy server, so I cannot give any hints. But since it is a HL2 mod and if you are able to set up sourcemod on your server, it should be possible?!

[kriz_cold]

This plugin is almost perfect...
But there's some glitches with the COLORFLOW function:
With some lenghts of the chat message, the string just cut the final letters in some ranges,
For example: I can tip:
||||||||||||||||||||||||||||||
and
|||||||||||||||||||||||||||||||||||
but I can't
||||||||||||||||||||||||||||||||
Basically, I can tip strings<80 and strings>85 but no 81, 82... characters (cutting to 80)
That happend with more ranges

Also, when you are reaching the chat lenght limit, the coloflow looses and the chat say something like:
[SampleTag] Kriz_cold: {COLORFLOW:0033FF-00F2F2}teeeeeeeeeeeeeeeeeeeeesting stuffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffff
(This can be fixed using a non direct replacing method, like the plugin uses, or just disabling the colorflow when a limit is reached)

I apologize for my bad english, but I hope you can fix these glitches, specially the first one. You can talk with me if you need more details.

[almostagreatcoder]

Oh sorry for letting you wait so long! I haven't been active here for a while - but I will look into this in the next days.

Originally Posted by kriz_cold This plugin is almost perfect... Also, when you are reaching the chat lenght limit, the coloflow looses and the chat say something like: [SampleTag] Kriz_cold: {COLORFLOW:0033FF-00F2F2}teeeeeeeeeeeeeeeeeeeeesting stuffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffff (This can be fixed using a non direct replacing method, like the plugin uses, or just disabling the colorflow when a limit is reached) I apologize for my bad english, but I hope you can fix these glitches, specially the first one. You can talk with me if you need more details.

OK, this one is a litte bit tough, because it leads to the question: what should happen, when a replacement exceeds the max. no. of characters? If the plugin would always ignore this very replacement rule, it would probably not be the expected behaviour (e.g. when you want to filter out bad language). So, I could try to implement this only for color flows: when the resulting string is too long, don't do anything. But due to the logic of replacements, this is not an easy thing to do. Will take some time...

[almostagreatcoder]

Originally Posted by kriz_cold This plugin is almost perfect... But there's some glitches with the COLORFLOW function: With some lenghts of the chat message, the string just cut the final letters in some ranges, For example: I can tip: |||||||||||||||||||||||||||||| and ||||||||||||||||||||||||||||||||||| but I can't |||||||||||||||||||||||||||||||| Basically, I can tip strings<80 and strings>85 but no 81, 82... characters (cutting to 80) That happend with more ranges

I lost some hours of lifetime testing that...
You are right, I can reproduce this behaviour as well - but I didn't manage to fix it, yet. This may also take some time to be solved...