chat message manager: don't apply color changes to message nodes
Apply the color changes at chat build time directly to the message being set on the component, instead of prepending the color change onto the message itself. This is a bit more robust since it doesn't break things which depend on the chat message not starting with a color, which they would not otherwise, such as the chat filter.
This commit is contained in:
@@ -440,11 +440,17 @@ LABEL391:
|
||||
jump LABEL1721
|
||||
LABEL405:
|
||||
iload 10 ; message uid
|
||||
sload 17 ; message channel
|
||||
sload 16 ; message name
|
||||
sload 18 ; message
|
||||
sload 21 ; message timestamp
|
||||
sconst "chatMessageBuilding"
|
||||
runelite_callback
|
||||
pop_int ; pop uid
|
||||
sstore 21 ; message timestamp
|
||||
sstore 18 ; message
|
||||
sstore 16 ; message name
|
||||
sstore 17 ; message channel
|
||||
iload 11
|
||||
switch
|
||||
1: LABEL408
|
||||
|
||||
@@ -413,11 +413,17 @@ CHAT_FILTER:
|
||||
jump LABEL562
|
||||
LABEL368:
|
||||
iload 12 ; message uid
|
||||
sload 2 ; message timestamp
|
||||
sconst "" ; message channel
|
||||
sload 1 ; message name
|
||||
sload 0 ; message
|
||||
sload 2 ; message timestamp
|
||||
sconst "chatMessageBuilding"
|
||||
runelite_callback
|
||||
pop_int
|
||||
pop_int ; uid
|
||||
sstore 2 ; message timestamp
|
||||
sstore 0 ; message
|
||||
sstore 1 ; message name
|
||||
pop_string ; message channel
|
||||
iload 18
|
||||
switch
|
||||
3: LABEL371
|
||||
|
||||
Reference in New Issue
Block a user