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
We encountered an issue where the chat prefixes and suffixes were not displaying correctly due to an invalid regular expression in the mention pattern. The error in the logs was a PatternSyntaxException caused by an unclosed group.
Steps Taken:
Fixed the pattern handling to properly escape special characters in the player's display name.
Updated the mentions.pattern configuration to avoid unclosed groups and ensure compatibility with the regex engine.
Code Fix: In the MentionsTransformStrategy class, modify the patternForPlayer method to properly escape player names in the regex pattern:
This fix ensures that the player's display name is safely inserted into the regular expression without causing syntax errors.
Additional Information: After modifying the pattern handling, the chat now displays prefixes and suffixes correctly, and mentions are processed as expected.
The text was updated successfully, but these errors were encountered:
We encountered an issue where the chat prefixes and suffixes were not displaying correctly due to an invalid regular expression in the mention pattern. The error in the logs was a PatternSyntaxException caused by an unclosed group.
Steps Taken:
Fixed the pattern handling to properly escape special characters in the player's display name.
Updated the mentions.pattern configuration to avoid unclosed groups and ensure compatibility with the regex engine.
Code Fix: In the MentionsTransformStrategy class, modify the patternForPlayer method to properly escape player names in the regex pattern:
This fix ensures that the player's display name is safely inserted into the regular expression without causing syntax errors.
Additional Information: After modifying the pattern handling, the chat now displays prefixes and suffixes correctly, and mentions are processed as expected.
The text was updated successfully, but these errors were encountered: