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.