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
This is a little ambiguous so I wasn't sure if this fell on MiniMessage or not.
The goal is to change the color of the user with a command in a book.
<click:run_command:"/nick &0%player_name%">TEST
To the console is /nick <reset><black>[PlayerName]
It would be really nice if could be omitted in the even of the /nick command and &0 went through.
EDIT: Realizing I was on 1.7.1. It now looks like <!obf><!b><!st><!u><!i> on 1.7,2
Hopefully it's as simple as maybe adding a unique tag that an if/else statement can remove those tags and append what you typed literally in the event there's other use cases without singling out the condition of /nick command being parsed.
The text was updated successfully, but these errors were encountered:
After discovering HTML codes will work such as this, the problem took care of itself. You can either close it. Or this can just be a workaround until conditions are cleaned up in the string builder /nick &#FAD7A0%player_name%
This is a little ambiguous so I wasn't sure if this fell on MiniMessage or not.
The goal is to change the color of the user with a command in a book.
<click:run_command:"/nick &0%player_name%">TEST
To the console is
/nick <reset><black>[PlayerName]
It would be really nice if could be omitted in the even of the /nick command and &0 went through.
EDIT: Realizing I was on 1.7.1. It now looks like <!obf><!b><!st><!u><!i> on 1.7,2
Hopefully it's as simple as maybe adding a unique tag that an if/else statement can remove those tags and append what you typed literally in the event there's other use cases without singling out the condition of /nick command being parsed.
The text was updated successfully, but these errors were encountered: