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
OS/device including version:
OS: Windows 11 21H2, GPU: RTX2080, drivers: 510.06, renderer: modern
Describe the bug
Seems like if mod sends two lines of text with svc_print and after \n is not a space then to first line applied some sort of color change.
To Reproduce
It particularly seen during race, in order to isolate what is going on I just put problematic G_print() in locally modified KTX /status command. So I does not have to race...
Could be seen in provided screenshot where I increase lenght of my name and this affects how it rendered in ezquake.
The text was updated successfully, but these errors were encountered:
meag
added a commit
to meag/ezquake-source
that referenced
this issue
Dec 28, 2021
Would still highlight if player name at start
Also fixes highlighting if frag message found on
second line but should eventually have
Stats_ParsePrint set the color highlighting as
two frag messages could come in the same
svc_print...
FixesQW-Group#623QW-Group@d41aacc
ezQuake version:
3.6a10 96ee7ab
OS/device including version:
OS: Windows 11 21H2, GPU: RTX2080, drivers: 510.06, renderer: modern
Describe the bug
Seems like if mod sends two lines of text with svc_print and after \n is not a space then to first line applied some sort of color change.
To Reproduce
It particularly seen during race, in order to isolate what is going on I just put problematic G_print() in locally modified KTX /status command. So I does not have to race...
Could be seen in provided screenshot where I increase lenght of my name and this affects how it rendered in ezquake.
The text was updated successfully, but these errors were encountered: