Difference between revisions of "Quickchat (Slash Command)"
From Paragon Wiki Archive
(New page: ==SlashCommand== {{SlashCommandArticle|command=quickchat|note=Pops up the quickchat menu.}}) |
Blondeshell (Talk | contribs) m (→External Links: update link) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
+ | {{TOCright}} | ||
==SlashCommand== | ==SlashCommand== | ||
{{SlashCommandArticle|command=quickchat|note=Pops up the quickchat menu.}} | {{SlashCommandArticle|command=quickchat|note=Pops up the quickchat menu.}} | ||
+ | |||
+ | == Customizing the QuickChat Menu == | ||
+ | |||
+ | Custom Quickchat Menus can be created by placing a properly formatted text file named '''quickchat.mnu''' in the following directory and then restarting COH after completely exiting to the desktop: | ||
+ | ''<COH_INSTALL_DIRECTORY>''\data\texts\''<LANGUAGE>''\Menus\ | ||
+ | |||
+ | '''<tt>''<LANGUAGE>''</tt>''' may be one of the following and needs to match the language of the version of City of Heroes that is installed: | ||
+ | * ''ChineseTraditional'' | ||
+ | * ''English'' | ||
+ | * ''French'' | ||
+ | * ''German'' | ||
+ | * ''Japanese'' | ||
+ | * ''Korean'' | ||
+ | * ''uk'' | ||
+ | |||
+ | === Syntax === | ||
+ | MNU files can be created and edited in any text editor. QuickChat Menus have the following general structure: | ||
+ | |||
+ | // Opening comment line for the QuickChat Menu | ||
+ | |||
+ | Menu QuickChat | ||
+ | { | ||
+ | {{color|gray|Title ''TitleName''}} | ||
+ | Option ''OptionName'' ''Command'' | ||
+ | {{color|gray|Divider}} | ||
+ | {{color|gray|Title ''TitleName''}} | ||
+ | Option ''OptionName'' ''Command'' | ||
+ | Menu ''SubMenuName'' | ||
+ | { | ||
+ | {{color|gray|Title ''SubMenuTitleName''}} | ||
+ | Option ''OptionName'' ''Command'' | ||
+ | {{color|gray|Divider}} | ||
+ | Option ''OptionName'' ''Command'' | ||
+ | } | ||
+ | } | ||
+ | |||
+ | * '''<tt>Menu</tt>''' defines a group of '''<tt>Option</tt>'''s. Menus can be nested, but each sub-menu requires its own pair of curly braces. | ||
+ | ** To create a submenu name of more than one word with spaces between them, enclose it in quotes. | ||
+ | * '''<tt>Option</tt>''' is a selectable command within a menu. | ||
+ | ** One letter in '''''<tt>OptionName</tt>''''' can be designated as a hotkey by prefixing an ampersand (&). | ||
+ | ** To create an option name of more than one word with spaces between them, enclose it in quotes. | ||
+ | ** '''''<tt>Command</tt>''''' is one or more [[slash commands]] (separated by '''<tt>$$</tt>'''). | ||
+ | * '''<tt>Title</tt>''' is an optional element. | ||
+ | ** '''''<tt>TitleName</tt>''''' labels a menu, or a section of a menu. Titles are not selectable. | ||
+ | ** Menus can have more than one Title. | ||
+ | * '''<tt>Divider</tt>''' places a horizontal line in the menu. | ||
+ | |||
+ | === Notes === | ||
+ | * MNU files allow comments. Use a double forward slash (<tt>//</tt>) anywhere on a line to force the client to ignore anything between the double slash and the line return. | ||
+ | * '''{{red|IMPORTANT:}}''' MNU files must have at least one line containing a carriage-return at the end of the line above the first "Menu" entry. It can be blank, a full comment, or just the comment tag (//) or any number of those lines otherwise it will not function. | ||
+ | * Changes to custom menus require you to exit the client in order for the changes to take effect. | ||
+ | * Custom menus are accessible by all characters on the same machine. By extension, you can send custom menu files to other people so that they can use them as well. | ||
+ | * '''<tt>Option</tt>''' and its parameters must be on one line. Otherwise, the menu will not function. | ||
+ | ** Inspiration and power names with spaces can be used in commands by replacing the spaces with an underscore (for example, Catch_a_Breath). You can also enclose the entire ''<tt>Command</tt>'' portion in quotation marks. | ||
+ | ** Multiple '''<tt>Command</tt>'''s can be executed by one '''<tt>Option</tt>''' by joining them with <tt>$$</tt>, just as they would be on the client command line. | ||
+ | |||
+ | ==See Also== | ||
+ | *{{slashcommand|popmenu}} | ||
+ | |||
+ | ==External Links== | ||
+ | * [http://web.archive.org/web/20120905021611/http://boards.cityofheroes.com/showthread.php?p=867593 Customizing the QuickChat Menu] by Fleeting_Whisper |
Latest revision as of 20:06, 3 November 2013
SlashCommand
- /quickchat
Pops up the quickchat menu.
Customizing the QuickChat Menu
Custom Quickchat Menus can be created by placing a properly formatted text file named quickchat.mnu in the following directory and then restarting COH after completely exiting to the desktop:
<COH_INSTALL_DIRECTORY>\data\texts\<LANGUAGE>\Menus\
<LANGUAGE> may be one of the following and needs to match the language of the version of City of Heroes that is installed:
- ChineseTraditional
- English
- French
- German
- Japanese
- Korean
- uk
Syntax
MNU files can be created and edited in any text editor. QuickChat Menus have the following general structure:
// Opening comment line for the QuickChat Menu Menu QuickChat { Title TitleName Option OptionName Command Divider Title TitleName Option OptionName Command Menu SubMenuName { Title SubMenuTitleName Option OptionName Command Divider Option OptionName Command } }
- Menu defines a group of Options. Menus can be nested, but each sub-menu requires its own pair of curly braces.
- To create a submenu name of more than one word with spaces between them, enclose it in quotes.
- Option is a selectable command within a menu.
- One letter in OptionName can be designated as a hotkey by prefixing an ampersand (&).
- To create an option name of more than one word with spaces between them, enclose it in quotes.
- Command is one or more slash commands (separated by $$).
- Title is an optional element.
- TitleName labels a menu, or a section of a menu. Titles are not selectable.
- Menus can have more than one Title.
- Divider places a horizontal line in the menu.
Notes
- MNU files allow comments. Use a double forward slash (//) anywhere on a line to force the client to ignore anything between the double slash and the line return.
- IMPORTANT: MNU files must have at least one line containing a carriage-return at the end of the line above the first "Menu" entry. It can be blank, a full comment, or just the comment tag (//) or any number of those lines otherwise it will not function.
- Changes to custom menus require you to exit the client in order for the changes to take effect.
- Custom menus are accessible by all characters on the same machine. By extension, you can send custom menu files to other people so that they can use them as well.
- Option and its parameters must be on one line. Otherwise, the menu will not function.
- Inspiration and power names with spaces can be used in commands by replacing the spaces with an underscore (for example, Catch_a_Breath). You can also enclose the entire Command portion in quotation marks.
- Multiple Commands can be executed by one Option by joining them with $$, just as they would be on the client command line.
See Also
External Links
- Customizing the QuickChat Menu by Fleeting_Whisper