The current block rule set up to fight against hyperlinks Ex: [Google](https://www.google.com) is set up to block anything containing square and rounded brackets in that order.
Most times when someone is posting an error they received to ask for help, their message gets blocked.
This happens because some errors (Especially LinQ errors) are logged in a similar way to the hyperlink markdown.
Ex: System.Linq.Enumerable.Count[TSource](IEnumeralbe1 source, Func2 predicate) at Editor.GameObjectNode.<>c.b__21_3(PrefabFile x)
How would you like it to work?
Since the hyperlink markdown shows up only when using it with a full url, the block rule regex can be set up to only block messages formatted this way: [*](http*.)
Here's what the regex looks like:
\[[^\]]+\]\(\s*(?:https?|ftp):\/\/[^\s\)]+\s*\)
Server Settings
Safety Setup
AutoMod
Find the current Hyperlink rule
Replace old regex with the one above
What have you tried?
Since the block rule was added, people had to either paste a screenshot of the error or painfully replace square brackets with round ones.
Additional context
The Manage Server permission is required, so only Yellow roles can do it
For?
Other
What can't you do?
The current block rule set up to fight against hyperlinks
Ex: [Google](https://www.google.com)
is set up to block anything containing square and rounded brackets in that order. Most times when someone is posting an error they received to ask for help, their message gets blocked.This happens because some errors (Especially LinQ errors) are logged in a similar way to the hyperlink markdown.
Ex: System.Linq.Enumerable.Count[TSource](IEnumeralbe1 source, Func2 predicate) at Editor.GameObjectNode.<>c.b__21_3(PrefabFile x)
How would you like it to work?
Since the hyperlink markdown shows up only when using it with a full url, the block rule regex can be set up to only block messages formatted this way: [*](http*.)
Here's what the regex looks like:
\[[^\]]+\]\(\s*(?:https?|ftp):\/\/[^\s\)]+\s*\)
What have you tried?
Since the block rule was added, people had to either paste a screenshot of the error or painfully replace square brackets with round ones.
Additional context
The
Manage Server
permission is required, so only Yellow roles can do itI've already tried it on my server and it works