Zrips / CMI

116 stars 98 forks source link

Hex color nicknames aren't working: nicks get the codes with added | #5653

Closed Momshroom closed 3 years ago

Momshroom commented 3 years ago

Description of issue: After a recent update, I can no longer give people hex nicknames:

I enter: /nick {#7fffd4>}Per{#7da98d<>}ry{#717486<} Perry OR /cmi nick .... and get: https://prnt.sc/13xadgd

I initially got told that I couldn't use that as a nickname, then gave myself the bypass perm and started getting told that the nick was too long and exceeded the 16 characters allowed. "Nickname is too long. Max is 16 symbols" After giving myself the length bypass perm as well, I get this as a nick. LP isn't showing me failing any perm checks, so I don't think it's still a permission issue and it worked without all the extra permissions before. Even opping myself doesn't fix it. The problem is the same with normal hex codes without the gradient.

Using /cmi nick does not fix it. (I've read the other issue)

I've got cmi.colors.nickname.* perms

I can use the hex codes in chat with no issues.

I've tried having the filtering in the config set to both true and false


CONFIG SECTION (DELETE IF NOT RELEVANT):

    # If set to true then nickName will be filtered from color codes when player changes it
    # cmi.colors.nickname.[colorName]
    NickName: false  
   # (Note, I've also tried this with true... same result)
  # If set to true, players public message who is in your ignore list will not be shown

Cmi Version (using/cmi version):

18:58:19 INFO: CMI plugin version: 8.8.4.8 MySQL 18:58:19 INFO: CMILib: 1.0.0.2 18:58:19 INFO: Server: Paper(756) 1.16.5-R0.1-SNAPSHOT 18:58:19 INFO: CMI economy: Disabled Vault: 1.7.3-b131 CMI Chat: Disabled 18:58:19 INFO: Modules -> 48 enabled 8 disabled: spawnerProximity, flightCharge, disabledEnchants, mirror, ranks, moneyCheque, spawners, spawnerCharge

Server Type (Spigot/Paperspigot/etc): Paper Server Version (using /ver): Paper version git-Paper-756 (MC: 1.16.5) Relevant plugins (Delete if this isn't needed):

CloudeLecaw commented 3 years ago

you need to set them to true so cmi can handle colorcodes

/cmi nick {#cc2500>}Cloude{#e68773<>}_Lecaw{#e6c8b8<} Cloude_Lecaw result Snag_8b1fa96

are you using CMI chat Modul? and if so you have enabled colored nicks in config? here the config part from our server - we let CMI handle all colors.. (means all need to be set to true, even if the descrptions are a bit confusing sometimes because they speak of filtering)

  Colors:
    # If set to true then all public messages will be filtered from color codes and will allow to colorize them with appropriate permission node
    # cmi.colors.publicmessage.[colorName]
    # Colors: black(&0), darkblue(&1), darkgreen(&2), darkaqua(&3), darkred(&4), darkpurple(&5), gold(&6), gray(&7), darkgray(&8), blue(&9), green(&a), aqua(&b), red(&c), lightpurple(&d), yellow(&e), white(&f), magic(&k), bold(&l), strikethrough(&m), underline(&n), italic(&o), reset(&r)
    PublicMessage: true
    PrivateMessage: true
    # If set to true then /me messages will be filtered from color codes and will allow to colorize them with appropriate permission node
    # cmi.colors.me.[colorName]
    me: true
    # If set to true, then color codes will get removed from text instead of leaving them if player dont have appropriate permission node for that color
    CleanUp:
      publicmessage: true
      privatemessage: true
      me: true
      signs: true
      books: true
      # List of strings to ignore when checking chat for color codes player cant use.
      # This will bypass players colorcode restrictions and will allow usage of particular chat formats
      # Applies only for public and private messages
      WhiteList:
      - '&c❤&7'
    # If set to true then nickName will be filtered from color codes when player changes it
    # cmi.colors.nickname.[colorName]
    NickName: true
Momshroom commented 3 years ago

I'm not using CMI's chat module and I thought I'd tried changing NickName to true... but apparently the change didn't get saved. Thank you, it's working now, though the wording in the config comment sounds like it works the other way around.