You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both issues I've encountered appear to be parser related:
If a swear word is at the very end of a string and it's last character of a swear word has a non-allowed character before it, it will not be censored. So f_u_c_k won't be censored, but f_u_c_k_ and f_u_ck will be.
If too many characters in a swear word have separators between them, the swear word won't be censored. This appears to happen when the number of separations exceeds MAX_NUMBER_COMBINATIONS. So w i l l i es_ will be censored but not w i l l i e s_ (underscore included to avoid issue described in 1).
The text was updated successfully, but these errors were encountered:
Both issues I've encountered appear to be parser related:
f_u_c_k
won't be censored, butf_u_c_k_
andf_u_ck
will be.MAX_NUMBER_COMBINATIONS
. Sow i l l i es_
will be censored but notw i l l i e s_
(underscore included to avoid issue described in 1).The text was updated successfully, but these errors were encountered: