The installer should've created a "Quick Raid Buttons" folder in your start menu with a shortcut to run the utility and another to this documentation file. You'll need .Net 4.0 installed to run the utility.

The first screen will be the button assignment screen. If this is the first time you've run the program and there's no stored information, it'll be blank with the Guardian class selected. At the top is a set of radio buttons to let you select what class's buttons you're assigning. Below is a set of 5 pull-down list boxes where you assign specific spell lines to each of the 5 quick-raid buttons. To set up a class you select that class, use the pull-down lists to set up the buttons, then save and generate the UI code.

The Save button saves the current state of button assignments for all classes into the utility's long-term storage. The Revert button reverts back to the state as of the last save. Button assignments are saved when you hit the Save button, when you generate UI code, or when you exit the program. You can edit your assignments and if you don't like it you can revert back to where you started. The Generate UI Code button causes the _ProfitUI_QuickRaidButtons.txt file to be generated. You'll get a standard Windows file save dialog come up, and you can browse to wherever you want the file saved, change it's name, and if you elect to save in the dialog the file will be written. The utility remembers the last filename you used and the last place you saved it, and will start there the next time you save the UI code file.

The Edit Spell Lines button brings up the second window. This window has a class and a spell line pull-down list at the top. It's main body is taken up by 16 lines where you can enter the spells in a single spell line. Each entry has a level spinner where you can set the level of a spell or CA, and a text box where you can enter it's name. For things like AA abilities that don't have a specific level, if it's the only ability in the line you can use any non-zero level. Level 1 and the maximum level would be reasonable choices. For other abilities you'd select levels where you want to switch from using one ability to another. You can also enter arbitrary commands by using a level of zero and entering the command text in the textbox. Commands here work like they do when creating macros in-game. As with macros, you don't want to use commands that could be interrupted or that could interrupt spells. /cancel_spellcast, /gsay, /raidsay and /shout would be the most common commands you'd put in. You can use %T and %I (case of the letter doesn't matter) to mark where to insert the target (the group or raid member you're using the ability on) or the implied target (whatever the target is targetting) for when you need to put that information in an announcement (so for instance the raid knows who you're trying to rez or who you cast a short-term buff on). The tooltip textbox at the top is where you can enter the text that'll appear when you mouse over the button. The Clear button on the right of each entry line clears that line's text and spinner.

The Save and Revert buttons at the bottom work like the ones on the button assignment screen. Cancel and Done return you to the button assignment screen, either cancelling any changes in progress or saving the changes. The Delete Spell Line button deletes all the information about a spell line. The New Spell Line button brings up a dialog to let you enter the name of a new line of spells. When you create a new spell line it starts out with the tooltip set to the name of the spell line and all the entry boxes blank. The Sort/Cleanup button sorts the entries into level order and removes any blank entries in the middle of the set. The sorting is in increasing order by level, and where two entries have the same level the physical order going down the screen is maintained. The Auto Fill Spells button currently does nothing. Eventually I intend it to fill in spell entries based on either the last populated textbox or the name of the spell line, appending Roman numerals to the end of the text. There's a bit more logic needed though, so I'm putting that off until later.

Data storage locations:

• Roaming\QuickRaidButtons beneath the user's AppData folder: this is where the QRBStorage.xml file holding all the data about button assignments and spell lines is saved.
• Local\Silverglass_Technical beneath the user's AppData folder: this is where the program settings the user can change are stored.
• _ProfitUI_QuickRaidButtons.txt under the Public Documents folder: the default location for the generated UI code. Windows 7 defaults to the Public Documents folder for the Public user rather than the user's My Documents folder. If you change the location you save the generated UI code to, the utility will remember the new location.

In _ProfitUI_QuickRaidButtons.txt the utility puts all arbitrary commands (level 0) first, then the conditional code to select the spell based on your current level, and finally the /useabilityonplayer command to cast the spell.