TheUnnamedOne

Quote:

Originally Posted by Silencer7 This seems pretty neat, but I have a couple questions (primarily since I haven't gotten to play with it myself yet.)' Will popmenu execute an entire command string with one click? Like, if I were to include a targeting function of some kind along with a power to use, that works in a single click like a bind would? (and is teamselect busted or did someone figure that out? I want to use it for ST buffs.)

powexectoggleon POWER1$$popmenu BuffMenu
powexectoggleon POWER2$$popmenu BuffMenu
powexectoggleon POWER3$$popmenu BuffMenu
etc...

Quote:

Originally Posted by DarkGob So glad the forums are back up. I was experimenting with popmenu during the downtime by viewing the Google cached version of this thread (or the first page of it, anyway), but my menu doesn't seem to be loading. I have the .mnu file in the appropriate folder, but when I do the command "/popmenu InspCombine" ingame nothing happens. I created and edited the .mnu file with the game client closed, I'm using the MenuName as the argument, but nothing happens.

• Double-check your menu structure again. I had a text error in the initial post about the folder pathing. The google cached version may not have refleced the edit. From the folder where you have CoX installed make sure your .MNU files are in the \data\texts\English\Menus folder. Make SURE you have the folders all spelled right. "texts" not "text" for example. This path will be different if you're not using the USA version. Find the appropriate folder for your language version inside your TEXTS folder.
• Make sure you .MNU file starts with a comment on the very first line. There HAS to be // in column 1 of line one of every .MNU file.
• Make sure you're using the top-level "Menu" title in the /popmenu command and NOT the .MNU's filename. Check for spelling mistakes here too.
• Make sure all your opening and closing braces (i.e. curly brackets) { } are set right. Each "MENU" item needs an opening brace { and a closing brace }, including the first one so the final character of the file should be a } unless you have a comment at the end too.

• The FastForm switching menus work AWESOMELY!
• The Attack Chain menuing works good but the fact that if you hit ANYTHING else but a valid menu key (like targeting another enemy) makes it a little wonky.
• The Dual Blade combo menus work only okay. Since timing is such a critical factor in Combos, it seems really easy to lose track and spoil the combo. I'm guessing a hotkey /binding method with changing the hotkey's powexecname command using /bindloadfile would work better since moving and targeting won't spoil the order of your attacks needed to complete the combo. I think I'll try a PopMenu Macro for initially selecting the Combo then switching to a /bindloadfile method to change the function of the hotkey used to pick the next attack power...

• The two lines at the top of the list starting with double frontslashes are comments. It has been determined by a couple people in FW's post that there must be some kind of lines ending in carriage-returns at the top of the file before the first "Menu" entry. Might as well make a few comments ( //Whatever...) describing the file.
• The top-level "Menu" name has no spaces in it to make the MACRO command work right the first time. /MACRO "PETS" "POPMENU ROBOTSANDDARKPETS" will make a working button. If there were spaces in the Menu name "Robots and Dark Pets" then I'd have to make the macro button then EDIT it and add in the quotes to make the POPMENU command work properly with Quote Marks around the Menu Name: POPMENU "Robots and Dark Pets". It works fine, there's just an extra step when you add spaces in the Menu Name and it reallly has NO effect on the functioning of the menu anyway so you might as well just not have spaces.
• As per FW's guide, the & symbol makes the NEXT character be the "Hotkey" when the PopMenu is opened. I can click the "Pets" Macro Button and then either click the "Assault Bot" item or hit my "1" key to activate the power. Flexibility is nice!

• The POPMENU command puts the pop-up menu right under your cursor. This makes it awesomely appropriate to having customized Powerbar buttons with integrated menus.
• To make customized Popup Menus, you have to have the proper folder structure and a few properly formated Menu (.mnu) files. To sum this up from FW's Guide, you need a "Data\Texts\English\Menus\" folder underneath the folder where you have CityOfHeroes.exe. This is where you have to store your Menu (.mnu) text files filled with a properly formatted menu structure and commands.
• Menu names used by the POPMENU command are determined by the top-level "Menu" entry INSIDE the file, NOT what the Menu (.mnu) file is named. This is very important! To load my custom popup menu shown in the next post into a macro button, after you created the Menu (.mnu) file named "{whateveryouwant}.mnu" with the Top-Level Menu label of "RobotsAndDarkPets" you would create the Macro button with this command:
  
  Quote:

  Macro "Pets" "popmenu RobotAndDarkPets"

• The Macro command can only accept 2 arguments; The name of the Macro Button and the Command String to execute. The command string MUST have quote marks around it if there are ANY spaces in the command string. Since a Top-Level Menu Name CAN have spaces in the title, this puts a cramp in the Macro command. The CityOfHeroes command interpreter can only understand ONE set of quote marks. Of course, you can use the Macro command and then go back and manually edit the Macro Button to put the quote marks in but since it really doesn't matter what the Name of the Menu is, I just scrunch them all together without quote marks for ease of applying the Macro command.
• Menu (.mnu) files are parsed (loaded into memory) when the CityOfHeroes.exe program is loaded. This means you cannot create or edit them on the fly. You MUST completely exit the game and reload it for the new menu to take effect.