Skip to content

Latest commit

 

History

History
150 lines (121 loc) · 8.94 KB

cmi-glow.md

File metadata and controls

150 lines (121 loc) · 8.94 KB

FAQ - CMI Glow Information

FAQ Menu

• CMI and Bungeecord info-, • Chance example, • CMI Chat manager, • Chat format info, • Chat filter, • Chat rooms, • CMI Commands info, • Custom Join and Leave, • CMI Economy manager, • Event commands, • Extending commands, • Getting started with CMI, • Glow info, • Create custom /help, • CMI Hex colors, • Importing data into CMI, • CMILib library info, • Customizing CMI Locale, • CMI Chat with LuckPerms prefix, • Migrate to MySQL database, • Player stuck in Mode?, • User-moderation info, • More message commands, • MOTD, • Parameters explained, • Ranks info, • Create custom /rules, • Running CMI, • Safety tips, • Specialized commands info, • Toggle example, • Trash example, • CMI Vote manager, • Worth info.

Official Zrips Links
  • Zrips Website 
    https://www.zrips.net/
    The official website, wiki/documentation/information
  • Zrips Discord 
    https://discord.gg/dDMamN4
    The official Discord community server with member-driven support
  • Zrips Github 
    https://github.com/Zrips
    The place for bug reports and feature suggestions
Prerequisites
  • Buy and Download CMI (premium plugin) 
    https://www.spigotmc.org/resources/3742/
    Get the CMI plugin if you haven't already, and then install it on all your servers
  • Also Download CMILib (free library) (more info) 
    https://www.spigotmc.org/resources/87610/
    All Zrips plugins require the CMILib .jar file. Get it and also put it on all your servers.
  • All my FAQ pages have been written for Spigot / Paper 1.20.x and CMI 9.6.x.x or newer.
  • The mrfdev Github page is not an official resource, we're building up our knowledge base as a courtesy.
  • I am an admin on the Zrips Discord, this does not mean what I share on here is official.

CMI can use a character Glow color, as well as nameplate colors, etc.

Hopefully this FAQ helps explain the issues with glow due to conflicting plugins and/or clients.

There's a little CMI glow youtube video I made that you can check out here: https://www.youtube.com/watch?v=6qHk9Po0aAg

ℹ️ CMI Glow

  • Commands:
/cmi glow (playerName) [true/false/color/gui]

To use /glow directly as a command, update ~/plugins/CMI/Alias.yml by setting The glow command from false to true.

Bonus: Rainbow glow colors? No, not by default, but you could make a /cmi aliaseditor command that uses the delay! 0.5 option and runs through all the colors once. Then players could use /glow rainbow if they have the correct permissions.

  • Permissions:
cmi.command.glow - Allows players to use /cmi glow command. (Player command)
cmi.command.glow.others - Allow players to set the glow of other players (Staff command)

cmi.command.glow.color.[colorname] - Allows to change glow color, you can * wildcard this, or be very specific.

cmi.command.armorstand.glow - Optionally you can grant a players to make glowing armorstands.
  • Placeholders:
%cmi_user_glow_code%
%cmi_user_glow_name%
  • Hex colors:
The glow effect does not support hex colors

ℹ️ It isn't working - help

Before we check if another plugin might cause a conflict (see below) we will have to request you to review your current set-up. I personally recommend to use Paper 1.19.x for the best results. But Spigot and Paper both are fine to use. Please note that forks of forks of forks could be a reason why glow on your server isn't working. Perhaps check first on a backup/test set-up with Spigot or Paper.

Next is to double check on SpigotMC if CMI and CMILib are both up to date.

And finally, be sure it's not your client or mods that are causing issues. Use the vanilla launcher and client and use the same version as the server engine. And ask another player to look at your character as you use /cmi glow to make changes.

ℹ️ It is always white - plugin conflicts

Due to the nature of how vanilla Minecraft is made developers are limited with what we can do/use in regards to using and controlling glow; which is done through the name tag prefix. And every plugin tries their best to work correctly. They're trying to stay in control over the features they offer. As a consequence you will have multiple plugins conflicting, and when something conflicts and doesn't work you will end up with a non working or white glow, or at least inconsistent results.

A random example is a popular CMI alternative to Settings/TabList.yml called TAB, it lets you resolve the issue by using %cmi_user_glow_code% placeholder. More information about that here.

A reasonable way to figure out if it's a plugin that's conflicting:

  • /stop the server, and back it up. Make a clone of it to test with.
  • Start the live server again of course, but not yet the test server.
  • Remove all the plugins from the test server - except CMI, CMILib, Vault and start the test server.
  • Login and try to use cmi glow again.
  • If it still doesn't work, it might be a client-side problem.
  • If it works now, it might be a plugin conflict. You can put back all the plugins you think that aren't causing this problem and start, repeat the test. Until you find it to break and then you know which plugin might cause the problem. You can then ask the developer of that plugin to (better) support CMI's glow feature to prevent conflicts.

Known plugins causing conflict:

  • TAB
  • Scoreboard R4
  • know of one? Let me know!

ℹ️ Misc.

If you are still having issues and want to report what you believe is a bug with the CMI glow feature? Please open a new Issue on Zrips' Github repository for CMI: https://github.com/Zrips/CMI/issues

Want to make suggestions to help improve the functionality of the CMI glow feature? Please open a new Discussion on Github: https://github.com/Zrips/CMI/discussions