[FlaminSarge]

Originally Posted by ddhoward I don't think that this will cause any problems with regards to that, no. However, you've made me realize that I could probably run a StrContains near the top of the function to check for any true doublequotes. If any are found, then immediately return Plugin_Continue. [I]This paragraph was written in response to a part of the previous post that has been edited out. In regards to the listener firing twice, that shouldn't be an issue.

Yeah I had noticed that you were covering most of the cases with true double quotes or 'say' anyways so a client sneaking in real double quotes using console-say plus a command chat trigger wasn't an issue, so I edited that bit out.

(Unless it is something you need to consider ¯\_(ツ)_/¯)

EDIT: Just noticed that the following in console:

say !sm_rename @me 'FS (nosound)'

results in my name changing to:

FS (nosound)

Where typically it would change to

'FS

with single quotes.
This is a super edge case, obviously, and can also serve as idiot-proofing, I suppose.

[ddhoward]

Hmm, I see what you mean. The case is this:

• A client is using the say command through the console
• The say command itself triggers a registered command
• The arguments for said command contain singlequote marks that might wrongly be processed by this plugin

This is a pretty unlikely scenario, but in the event that someone actually does run into this problem, I'd recommend temporarily deactivating the feature of this plugin. (This can be done through the /settings menu.)

Next version will include a check to see if the command arguments already contain any true doublequote marks (if it does, then don't modify anything) as well as hopefully preparing for the upcoming forced changes to Updater integration.

[ddhoward]

Updated to 18.0115.0. This update:

• updates the version of my ddhoward_updater include used
• changes the plugin's two main cvars with respect to what values do what
• minor optimizations

[FlaminSarge]

I noticed that the smart change functionality stops at the first pair it finds. Is this intended?
It doesn't do so well with things like sm_vote e.g.
!vote "Test vote" "Test answer 1" "Test answer 2"
FS : !vote 'Test vote' 'Test answer 1' 'Test answer 2'
*Started vote: Test vote?
1. 'Test
2. answer
3. 1'
4. 'Test
5. answer

[ddhoward]

Updated to version 18.0220.0. Fixes the above issue pointed out by FlaminSarge. Silly mistake on my part.

[mdrxd100]

Great plugin, fixes a problem that has been there forever.