Skip to content

Latest commit

 

History

History
106 lines (91 loc) · 6.74 KB

cmi-commands.md

File metadata and controls

106 lines (91 loc) · 6.74 KB
Raw

FAQ - How do I deal with CMI commands?

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.

Both base commands and your own custom commands

ℹ️ CMI can handle Commands.

By default CMI has all it's commands underneath /cmi <command> you can find them all by typing: /cmi help and by viewing the list on the website here: (https://www.zrips.net/cmi/commands/) If you wish to use /<command> and not just /cmi <command>, then you can edit the /Settings/Alias.yml file and change the Enabled option from false to true.

  #  
  # /cmi home $1-
  /home:
    Enabled: true
    Tab: true

You can now save the file and type: /cmi reload, but to properly register the commands, you must /stop your server and start it again.

Your own custom alias commands

Another option is to add your own commands. For example: /banana. Custom Aliases (commands) are stored in the ~/plugins/CMI/CustomAlias/ folder, and by default, are stored in the CustomAlias.yml file. However, as of version 9.0.3.x and upwards, you can also store Custom Aliases in their own .yml file in the ~/plugins/CMI/CustomAlias/ directory. To get started type /cmi aliaseditor. It will come up with an interface of all the registered custom aliases. Clicking on the green + will display a prompt in chat, asking you to enter the name of the command in the chat. Once you have done this, it will open another interface which will also show a green +. Clicking on it will prompt you to enter the command that should be executed in the chat box, without the starting /. For example: cmi say I am a banana. You can press the green + again to add another command. This feature is very dynamic, extensive and flexible. You can learn much more about it here.

Your new command will show red, but it will still work. To properly register it, you must /stop your server and start it again. Once the server has restarted, the command will be properly registered and will auto-complete too. To edit existing custom aliases, you can type /cmi aliaseditor and then click on the command in the list. Optionally, you can type /cmi aliaseditor <command> to quickly navigate to a specific command.

A visual YouTube tutorial can be found here

  • And finally; /stop the server, and start it up again to guarantee that everything's working properly.