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
There is currently a conflict with both Battlemod and Chatmon concerning color codes.
It seems that Chatmon does not strip color codes prior to making a match, and Battlemod rewrites the log to include a lot of color coding around targets and ability names,
To exacerbate this further, Battlemod breaks up multi-word ability names with additional color codes per word, even if the color is not changing, causing a mismatch.
It will have to be the former, since the fix for battlemod is not very simple. The reason battlemod does this is because the color formatting will disappear after line breaks (a line break resets the color). And since we cannot detect when that happens, the idea was to prepend the currently active color code before every word. Ideally we'd find a solution to that as well as fix Chatmon to strip formatting prior to text matching.
There is currently a conflict with both Battlemod and Chatmon concerning color codes.
It seems that Chatmon does not strip color codes prior to making a match, and Battlemod rewrites the log to include a lot of color coding around targets and ability names,
To exacerbate this further, Battlemod breaks up multi-word ability names with additional color codes per word, even if the color is not changing, causing a mismatch.
Example:
<trigger match="*Phlegm Expulsion*" sound="..." />
Raw text, after Battlemod (simplified mode, default template):
[��Thillloab��] � Phlegm�� � Expulsion�� �¨ ��Thillloab��
From the example, color codes are unnecessarily injected between "Phlegm" and "Expulsion", causing the above trigger to not match.
For chatmon, a work around would be to place a wildcard between each word, which is not ideal:
<trigger match="*Phlegm*Expulsion*" sound="..." />
This needs to be resolved in one of two ways:
The text was updated successfully, but these errors were encountered: