vanilla-wow-addons – Blame information for rev 1

Subversion Repositories:
Rev:
Rev Author Line No. Line
1 office 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <html>
3 <head>
4 <meta name="GENERATOR" content="PageBreeze Free HTML Editor (http://www.pagebreeze.com)">
5 <title>Flex Bar Commands</title>
6 </head>
7 <body bgcolor="#ffffff">
8 <p>
9 <table cellspacing="0" cellpadding="3" width="100%" align="center" border="1" bordercolor="#000000">
10 <caption><font size="2"><strong>Complete
11 FlexBar Command List</strong> </font> </caption><tr><td>
12 <p align="center"><strong><font
13 size=2>Appearance Commands</font></strong></p></td></tr>
14 <tr>
15 <td width="100%">
16 <p><strong><font size="2">VERY
17 IMPORTANT NOTES ON COMMANDS:</font></strong></p>
18 <ol>
19 <li><font size="2">Square brackets denote an optional
20 parameter.&nbsp; The brackets are not entered on the command line.&nbsp;
21 IE: /flexbar hide button=1 always hides button 1, /flexbar hide button=1
22 toggle=
23  
24 'true' hides itif it's shown, shows it if it's
25 hidden.
26 <li><font size="2">Parameter values come in 2 main
27 types: Number and string.&nbsp; For numbers simply type
28 &lt;parameter&gt;=&lt;number&gt;&nbsp; IE: button=1&nbsp; For strings,
29 enclose them in single quotes&nbsp; IE: on='GainAura'&nbsp; Some
30 parameters can take multiple values.&nbsp; For numbers you can enter a
31 range IE: button=1-4 results in buttons 1, 2, 3 and 4 being done.&nbsp; For both strings and
32 numbers you can enter it as
33 aset&nbsp; IE: button=
34 [1 2] or target=
35 ['hostile' 'neutral'].&nbsp; Currently there is no way to
36 combine strings and numbers[1 'hostile'] (nor any reason to in the code),&nbsp; Nor
37 is there a way to combine ranges and numbers (so [1-3 5] will
38 not work).
39  
40  
41  
42 <li><font size="2">For many commands both button and
43 group appear optional.&nbsp; This is misleading - in the case of both
44 being present, ONE OR THE OTHER must be entered. </font>
45  
46  
47 <li><font size="2">My original parser didn't handle
48 decimals, so number values are often in tenths:&nbsp; scale=5 is
49 actually half size, color=
50 [10 1 1] is dark red, in= 50 will delay
51 5 seconds.
52 <li><font size="2">if you see
53 something like target=
54 &lt;target&gt;that just means that the parameter may be either
55 a string or a number, depending on context - it does not mean put &lt;
56 and &gt; around the value.
57  
58  
59  
60 <li><font size="2">You can put a single quote in a
61 string by escaping it with
62 a&nbsp;\&nbsp;EG:&nbsp;if='UnitDebuff&lt;["target" "Hunter\'s
63 Mark"]&gt;' or Macro= '/echo
64 Dhargo\'s
65 Test's </li></ol></font></font></font></font></font></td></tr>
66 <tr><td width="100%"><font
67 size=2><strong>/flexbar show [button=#] [group=#]
68 [toggle= 'true'] [on='event'] [target=&lt;target&gt;] [if='condition'] [in=#]
69 [tname= &lt;timername&gt;] [ttoggle=
70 'true']</font></strong></td></tr><tr><td><font size="2">Show the buttons or group
71 specified</font></td></tr>
72 <tr><td width="100%"><font
73 size=2><strong>/flexbar hide [button=#] [group=#]
74 [toggle= 'true'] [on='event'] [target=&lt;target&gt;] [if='condition'] [in=#]
75 [tname= &lt;timername&gt;] [ttoggle=
76 'true']</font></strong></td></tr><tr><td><font size="2">Hide the buttons or group
77 specified</font></td></tr>
78 <tr><td width="100%"><font
79 size=2><strong>/flexbar scale [button= #] [group=#] scale= # [toggle= #][reset='true'=] [on= 'event'] [target=
80 &lt;target&gt;][if='condition'] [in=#] [tname=
81 &lt;timername&gt;] [ttoggle= 'true']</font></strong></td></tr><tr><td><font size="2">Scale the buttons by scale.&nbsp;
82 Scale is a number from 5-50 (half size to 5X size)&nbsp; If toggle is
83 included, and the button is already the size you are trying to make it, it
84 will become the size in toggle.&nbsp; So, /flexbar scale button=1 scale=5
85 toggle=20 will make the button half size, unless it's already half size,
86 then it will become 2X size.&nbsp; If reset is 'true' then the button will
87 return to normal size.</font></td></tr>
88 <tr><td width="100%"><font
89 size=2><strong>/flexbar shade [button=#] [group= #] color= [## #]&nbsp;[toggle= [###]][reset='true'= ] [on= 'event'] [target=
90 &lt;target&gt;][if='condition'] [iftarg=] [in=#]
91 [tname= &lt;timername&gt;] [ttoggle=
92 'true']</font></strong></td></tr><tr><td><font size="2">Shades the button with the color
93 specified.&nbsp; The color must be a red/green/blue set surrounded by
94 brackets.&nbsp; Each element can range from 0-10&nbsp;- IE /flexbar shade
95 button=1 color=[10 1 1] will apply a dark red tint to the button.&nbsp; A
96 color like [5 5 5] will just dim the button.&nbsp; If toggle is specified,
97 and the button is already the color in color= then it will become the
98 color in toggle=&nbsp; While setting the color to [10 10 10] will seem to
99 restore it to normal, it will override any mana/range type shading that
100 FlexBar can do automatically.&nbsp; To restore this functionaliyt use
101 reset='true'</font></td></tr>
102 <tr><td width="100%"><font
103 size=2><strong>/flexbar fade [button= #] [group=#] alpha= # [toggle= #] [on='event'] [target= &lt;target&gt;] [if='condition']
104 [in=#] [tname= &lt;timername&gt;] [ttoggle=
105 'true']</font></strong></td></tr><tr><td><font size="2">Adjusts the alpha (transparency) of
106 the button.&nbsp; Alpha can ange from 1 (nearly invisible) to 10.&nbsp; If
107 toggle is specified, then if the button is already the specified alpha, it
108 will become the alpha in toggle.&nbsp; IE /flexbar fade button=1 alpha=1
109 will always make a button nearly invisible, /flexbar shade button=1
110 alpha=1 toggle=10 will make it nearly invisible if it's not, otherwise
111 make it fully visible again.</font></td></tr>
112 <tr><td width="100%"><font
113 size=2><strong>/flexbar text [button=#] [group=#]
114 [text= 'text'] [on='event'] [target=&lt;target&gt;] [if='condition'] [in=#]
115 [tname= &lt;timername&gt;] [ttoggle=
116 'true']</font></strong></td></tr><tr><td><font size="2">FlexBar buttons have 3 text
117 attributes you can modify to display information.&nbsp; The first defaults
118 to the top right corner.&nbsp; /flexbar text button=1 text='Hi' will set
119 that text to "Hi".&nbsp; There are a number of special values that text
120 can be set to:&nbsp; %c will display the cooldown of the spell on the
121 button, %b will display the hotkey assigned to the button and %d will
122 display the button number.&nbsp; Furthermore there is a whole slew of
123 special, dynamic variables it can be -- please see the appendix "Text
124 Substitutions" for a full list.</font></td></tr>
125 <tr><td width="100%"><font
126 size=2><strong>/flexbar text2 [button=#] [group=#]
127 [text= 'text'] [on='event'] [target=&lt;target&gt;] [if='condition'] [in=#]
128 [tname= &lt;timername&gt;] [ttoggle=
129 'true']</font></strong></td></tr><tr><td><font size="2">FlexBar buttons have 3 text
130 attributes you can modify to display information.&nbsp; The&nbsp;second
131 defaults to the&nbsp;bottom right corner.&nbsp; /flexbar text2 button=1
132 text='Hi' will set that text to "Hi".&nbsp; There are a number of special
133 values that text can be set to:&nbsp; %c will display the cooldown of the
134 spell on the button, %b will display the hotkey assigned to the button and
135 %d will display the button number.&nbsp; Furthermore there is a whole slew
136 of special, dynamic variables it can be -- please see the appendix "Text
137 Substitutions" for a full list.</font></td></tr>
138 <tr>
139 <td width="100%"><strong><font size="2">/flexbar text3 [button=#] [group=#]
140 [text='text'] [on='event'] [target=&lt;target&gt;] [if='condition'] [in=#]
141 [tname=&lt;timer name&gt;] [ttoggle='true']</font></strong></td></tr>
142 <tr>
143 <td width="100%"><font size="2">FlexBar buttons have 3 text attributes you
144 can modify to display information.&nbsp; The&nbsp;third defaults to
145 the&nbsp;center.&nbsp; /flexbar text3 button=1 text='Hi' will set that
146 text to "Hi".&nbsp; There are a number of special values that text can be
147 set to:&nbsp; %c will display the cooldown of the spell on the button, %b
148 will display the hotkey assigned to the button and %d will display the
149 button number.&nbsp; Furthermore there is a whole slew of special, dynamic
150 variables it can be -- please see the appendix "Text Substitutions" for a
151 full list.</font></td></tr>
152 <tr><td width="100%"><font
153 size=2><strong>/flexbar justifytext [button=#] [group=#]
154 [pos= &lt;position&gt;] [on='event'] [target=&lt;target&gt;] [if='condition']
155 [in=#] [tname= &lt;timername&gt;]
156 [ttoggle= 'true']</font></strong></td></tr><tr><td><font size="2">Both text attributes can be move to
157 one of nine spots on the button - 'topleft', 'top', 'topright', 'right',
158 'bottomright', 'bottom', 'bottomleft', 'left' and 'center'.&nbsp; IE
159 /flexbar justifytext button=1 pos='topleft' will move it to the top left
160 of the button and justify it left, /flexbar justifytext button=1 pos='top'
161 will center it on the top of the button and so on.</font></td></tr>
162 <tr><td width="100%"><font
163 size=2><strong>/flexbar justifytext2 [button=#] [group=#]
164 [pos= ] [on='event'] [target=&lt;target&gt;] [if='condition'] [in=#]
165 [tname= &lt;timername&gt;] [ttoggle=
166 'true']</font></strong></td></tr><tr><td><font size="2">Both text attributes can be move to
167 one of nine spots on the button - 'topleft', 'top', 'topright', 'right',
168 'bottomright', 'bottom', 'bottomleft', 'left' and 'center'.&nbsp; IE
169 /flexbar justifytext2 button=1 pos='topleft' will move it to the top left
170 of the button and justify it left, /flexbar justifytext2 button=1
171 pos='top' will center it on the top of the button and so on.</font></td></tr>
172 <tr><td width="100%"><font
173 size=2><strong>/flexbar shadetext [button=#] [group= #]
174 color= [## #]&nbsp;[toggle= [###]][reset='true'= ] [on= 'event']
175 [target= &lt;target&gt;][if='condition'] [iftarg=]
176 [in=#] [tname= &lt;timername&gt;] [ttoggle=
177 'true']</font></strong></td></tr><tr><td><font size="2">Both text attributes can be shaded -
178 this works just like shading the whole button.&nbsp; Please see /flexbar
179 shade for details.</font></td></tr>
180 <tr><td width="100%"><font
181 size=2><strong>/flexbar shadetext2
182 [button= #] [group= #] color= [toggle=
183 'true'][reset= 'true'= ] [on= 'event'] [target=
184 &lt;target&gt;][if='condition'] [iftarg=] [in=#]
185 [tname= &lt;timername&gt;] [ttoggle=
186 'true']</font></strong></td></tr><tr><td><font size="2">Both text attributes can be shaded -
187 this works just like shading the whole button.&nbsp; Please see /flexbar
188 shade for details.</font></td></tr>
189 <tr><td width="100%"><font
190 size=2><strong>/flexbar showgrid [button=#] [group= #] [toggle=
191 'true']</font></strong></td></tr><tr><td><font size="2">If showgrid is turned on, the button
192 is displayed even if it is empty.&nbsp; If toggle is true and showgrid is
193 on, then it is turned off, otherwise it is turned on</font></td></tr>
194 <tr><td width="100%"><font
195 size=2><strong>/flexbar hidegrid [button=#] [group= #] [toggle=
196 'true']</font></strong></td></tr><tr><td><font size="2">If Hidegrid is turned on, the button
197 is only displayed if it has an action on it, if it doesn't then the button
198 is hidden.&nbsp; Again, if toggle is true then it switches between
199 showgrid and hidegrid.</font></td></tr>
200 <tr>
201 <td width="100%">
202 <p align="center"><font size="2">Movement
203 Commands</font></p></td></tr>
204 <tr><td width="100%"><font
205 size=2><strong>/flexbar lock [button=
206 #] [group= #]</font></strong></td></tr><tr><td><font size="2">Lock a button to avoid accidentally
207 moving it.&nbsp; IE /flexbar lock button=1</font></td></tr>
208 <tr><td width="100%"><font
209 size=2><strong>/flexbar unlock [button=
210 #] [group= #]</font></strong></td></tr><tr><td><font size="2">Unlock a button again to move
211 it.&nbsp; Note:&nbsp; You cannot unlock buttons in a group except the
212 group anchor.</font></td></tr>
213 <tr><td width="100%"><font
214 size=2><strong>/flexbar moveabs button= # xx=# yy= # [on= 'event'] [target=&lt;target&gt;] [if= 'condition'] [in=#]
215 [tname= &lt;timername&gt;] [ttoggle=
216 'true']</font></strong></td></tr><tr><td><font size="2">Move a button to a location on the
217 screen.&nbsp; 0,0 is in the bottom left of the screen, and I am unsure as
218 to the exact dimensions of most desktops.&nbsp; Experimentation is in
219 order.&nbsp; Note - you can send it soaring off the screen never to be
220 seen again, and that may have adverse performance effects.&nbsp; Just use
221 /flexbar move button=1 xx=100 yy=100 to move it where you can get at it
222 again.&nbsp; The reference point on the button is the upper left
223 corner.&nbsp; So, /flexbar moveabs button=1 xx=0 yy=0 will hide it off the
224 bottom of the screen because the top left corner of the button will be in
225 the bottom left corner of the screen.</font></td></tr>
226 <tr><td width="100%"><font
227 size=2><strong>/flexbar moverel button=
228 # trgbtn= #dx= dy= [on= 'event']
229 [target= &lt;target&gt;] [if= 'condition'] [in=#]
230 [tname= &lt;timername&gt;] [ttoggle= 'true']&lt;
231 /STRONG&gt;</font></strong></td></tr><tr><td><font size="2">Like moveabs, but it moves the button
232 to a spot relative to the button name in trgbtn=.&nbsp; IE /flexbar move
233 button=2 trgbtn=1 dx=38 dy=38 will move button 2 to sit just off the upper
234 right corner of button 1 (if UI scale and button scale are normal - if
235 they are not, dx/dy will need to change to give the same
236 effect)</font></td></tr>
237 <tr><td width="100%"><font
238 size=2><strong>/flexbar movetomouse button=# dx= dy=
239 [on= 'event'] [target=&lt;target&gt;] [if= 'condition'] [in=#]
240 [tname= &lt;timername&gt;] [ttoggle=
241 'true']</font></strong></td></tr><tr><td><font size="2">Like moverel and moveabs but it
242 positions the button with respect to the current position of the mouse
243 cursor.&nbsp; IE /flexbar movetomouse button=1 dx=-19 dy=19 will center
244 button 1 on the mouse cursor (if UI scale and button scale are
245 1)</font></td></tr>
246 <tr>
247 <td width="100%">
248 <p align="center"><font size="2">Group
249 Commands</font></p></td></tr>
250 <tr><td width="100%"><font
251 size=2><strong>/flexbar group button= # anchor= # </font></strong></td></tr><tr><td><font size="2">Forms the specified buttons into a
252 group.&nbsp; The group may be moved/hidden/faded etc as a unit.&nbsp;
253 Anytime you specify group= in a command, it replaces the button list
254 (button=) with the members of the group.&nbsp; The anchor is going to be
255 the only button in the group with a handle to move it with (the rest will
256 be locked) and the group number will be the anchor button number.&nbsp;
257 The anchor button MUST be in the list of buttons in button=.&nbsp;
258 Currently the only way to add buttons to a group is to simply specify the
259 entire old group + the new buttons - IE:&nbsp; /flexbar group button=1-12
260 anchor=1 will form group #1 of 12 buttons (1-12).&nbsp; Moving button 1
261 will move all buttons.&nbsp; /flexbar group button=[1 2 3 4 5 6 7 8 9 10
262 11 12 15 16 17] anchor=1 will add buttons 15, 16 and 17 to the
263 group.&nbsp; I will eventually update my parser to allow button=[1-12
264 15-16] BUT IT DOES NOT SUPPORT THAT AS OF 1.37.</font></td></tr>
265 <tr><td width="100%"><font
266 size=2><strong> /flexbar
267 ungroupgroup= #</font></strong></td></tr><tr><td><font size="2">Disbands the named group</font></td></tr>
268 <tr><td width="100%"><font
269 size=2><strong> /flexbar
270 listgroups[group= #]</font></strong></td></tr><tr><td><font size="2">If group is specified, lists the
271 buttons in the group.&nbsp; If group is not specified, it lists all the
272 groups.</font></td></tr>
273 <tr><td width="100%"><font
274 size=2><strong>/flexbar circlegroup group=
275 # [padding= #]</font></strong></td></tr><tr><td><font size="2">1 of 3 auto-arrange commands.&nbsp;
276 Circlegroup tries to make a circle, starting at 10 O'clock and going
277 clockwise, with the 7th button in the middle.&nbsp; Limitation - This only
278 works with groups with 7 or less buttons.&nbsp; Padding is the space
279 between buttons.</font></td></tr>
280 <tr><td width="100%"><font
281 size=2><strong>/flexbar horizontalgroup group=# [padding= #] [height=
282 #]</font></strong></td></tr><tr><td>
283 <p><font size="2">2 of 3 auto-arrrange commands.&nbsp;
284 Horizontal group will make a horizontal bar out of the group.&nbsp; If the
285 optional height parameter is included, it will make the bar that many rows
286 high.&nbsp; However, be aware that the button numbers will go top-bottom
287 then left to right (which is counter-intuitive I agree, but too late to
288 fix I'm afraid as people are used to it).&nbsp;&nbsp; The optional padding
289 parameter is the space between buttons</font></p></td></tr>
290 <tr><td width="100%"><font
291 size=2><strong>/flexbar verticalgroup group=# [padding= #] [width=
292 #]</font></strong></td></tr><tr><td><font size="2">3 of 3 auto-arrange commands.&nbsp;
293 Veritcal group makes a vertical bar out of the group.&nbsp; If the
294 optional width parameter is included, the bar will be that many columns
295 wide.&nbsp; Button number goes left to right, top to bottom.&nbsp; The
296 optional padding parameter is the amount of space between buttons.&nbsp;
297 Examples:&nbsp; /flexbar verticalgroup group=1&nbsp; will make a single
298 column bar out of group one.&nbsp; If group 1 has buttons 1-12 then
299 /flexbar verticalgroup group=1 width=6 will make a 6 button wide, 2 button
300 high bar numbered 1-6 across the top and 7-12 across the
301 bottom.</font></td></tr>
302 <tr>
303 <td width="100%">
304 <p align="center"><font size="2">Miscellaneous
305 Commands</font></p></td></tr>
306 <tr><td width="100%"><font
307 size=2><strong>/flexbar remap [button= #] [group=#] base= # [toggle= 'true'][reset='true'=] [on= 'event'] [target=
308 &lt;target&gt;][if='condition'] [in=#] [tname=
309 &lt;timername&gt;] [ttoggle=
310 'true']</font></strong></td></tr><tr><td>
311 <p><font size="2">Remap is a very powerful, and slightly
312 confusing command.&nbsp; To understand Remap, you have to understand
313 buttons and ID's and their relationship:</font></p>
314 <p><font size="2">One of a button's attributes is it's
315 ID (NOT ITS NUMBER - THEY CAN BE DIFFERENT).&nbsp; This ID is how WoW
316 identifies the action to be taken when you click it.&nbsp; Two buttons
317 with the same ID will have the same icon and take the same action when you
318 click them.&nbsp; Drag the action off one and it will dissappear from the
319 other, put something on one it will appear in the other.&nbsp; While many
320 flexbar attributes (including hotkey bindings)&nbsp;are attached to the
321 button - the action it performs is always about the ID.</font></p>
322 <p><font size="2">Out of the box, the default ID of a
323 button is the same as it's number (as of 1.37 - prior to 1.37 there was
324 oddness in the mapping above button 73).&nbsp; To see a simple example of
325 remapping, look at the default action bar.&nbsp; It is only 12 buttons,
326 but they take on ID's 1-12 on page 1, 13-24 on page 2 through 61-72 on
327 page 6.&nbsp; WITH A SMALL EXCEPTION:&nbsp; Warriors, the first page takes
328 on ID's 73-84 if you're in battle stance, 85-96 if you're in defensive
329 stance and 97-108 if you're in berserker stance.&nbsp; Druids - page 1 is
330 1-12 in caster form, 83-96 in bear form and 97-108 in cat form.&nbsp;
331 Rogues, they remap to something above 73 on stealthing, 1-12
332 non-stealthed.</font></p>
333 <p><font size="2">This is remapping - the buttons take
334 on new actions, but the hotkeys etc. stay the same (allowing you to use
335 the same hotkeys for different actions in different
336 situations.)</font>
337  
338 </p>
339 <p><font size="2">/flexbar remap will remap the buttons
340 specified with ID's starting at base=&nbsp; IE:&nbsp; /flexbar remap
341 button=1-12 base=13 will make button 1 have ID 13, button 2 have ID 14
342 through button 12 having ID 24.&nbsp; If you do this, you'll notice that dragging an action to button 1
343 alsoplaces it in button 13.&lt; /FONT&gt;
344  
345  
346 </p>
347 <p><font size="2">While not particularly useful alone,
348 with events this is a mainstay for many classes (including warriors,
349 druids, rogues, hunters and priests).</font>
350  
351 </p></font></td></tr>
352 <tr><td width="100%"><font
353 size=2><strong>/flexbar advanced [button=#] [group= #]
354 state= &lt;'on'| 'off'&gt;
355 </font></strong></td></tr><tr><td><font size="2">When advanced mode is turned on
356 (/flexbar advanced button=1 state='on') only left clicks trigger the
357 action on the button.&nbsp; Right clicks do not.&nbsp; This is to allow
358 seperate functions on both rightclick and left click.&nbsp; Return it to
359 normal with /flexbar advanced button=1 state='off'</font></td></tr>
360 <tr><td width="100%"><font
361 size=2><strong>/flexbar disable [button=#] [group=#]
362 state=&lt;'on'&nbsp;| 'off'&gt; [toggle='true'] [on='event'] [target=
363 &lt;target&gt;] [if='condition'] [in=#] [tname=
364 &lt;timername&gt;] [ttoggle=
365 'true']</font></strong></td></tr><tr><td><font size="2">This will completely disable actions
366 from clicking on the button - some ingenius folks fond&nbsp;some neat
367 things to do with this.&nbsp; /flexbar disable&nbsp;button=1
368 state='off'&nbsp;returns it to normal.&nbsp;</font></td></tr>
369 <tr><td width="100%"><font
370 size=2><strong>/flexbar use button=# [on='event']
371 [target= &lt;target&gt;] [if='condition'] [in=#] [tname=
372 &lt;timername&gt;] [ttoggle=
373 'true']</font></strong></td></tr><tr><td><font size="2">This command will attempt to click
374 the named buttons.&nbsp; VERY IMPORTANT - this can not be used on ANY
375 event but button clicks.&nbsp; This is a limitation of the WoW engine put
376 there to prevent bots.&nbsp; You can NOT use this to automatically recast
377 a buff when it wears off - that simply is not possible -
378 sorry.</font></td></tr>
379 <tr><td width="100%"><font
380 size=2><strong>/flexbar echo [button= #] [group=#] base= # [toggle= 'true'][reset='true'=] [on= 'event'] [target=
381 &lt;target&gt;][if='condition'] [in=#] [tname=
382 &lt;timername&gt;] [ttoggle=
383 'true']</font></strong></td></tr><tr><td><font size="2">This will cause the named button to
384 raise button-click events for the specified numbers.&nbsp; This was a
385 first try at making expanded macros follow remaps - I see no real use for
386 it now that FlexActions are in, but it remains.&nbsp; If you have a notion
387 of how to use it, play with it and share :)</font></td></tr>
388 <tr><td width="100%"><font
389 size=2><strong>/flexbar lockicon [button=#] [group= #] [off=
390 'true']</font></strong></td></tr><tr><td><font size="2">This fixes icons onto the button and
391 prevents you from dragging them off in the heat of combat.&nbsp;
392 Shift-Click (not shift-drag) to get them off.&nbsp; Turn this off with
393 /flexbar lockicon button=1 off='true'</font></td></tr>
394 <tr><td width="100%"><font
395 size=2><strong>/flexbarraiseevent='event&nbsp;name'&nbsp;[source=
396 &lt;source&gt;][on='event'] [target=&lt;target&gt;] [if='condition']
397 [in=#] name= [toggle='true']
398 [tname= &lt;timer name&gt;] [ttoggle=
399 'true']</font></strong></td></tr><tr><td><font size="2">This was a first attempt to allow
400 timed actions - it allows you to raise an event in a specified amount of
401 time, then respond to that event in another command.&nbsp; Deprecated in
402 favor of the in= parameters in all commands that take on=.</font></td></tr>
403 <tr><td width="100%"><font
404 size=2><strong>/flexbar loadconfig config=
405 'config name' </font></strong></td></tr><tr><td>
406 <p><font size="2">This loads a config file, which is a
407 list of flexbar commands WITHOUT the /flexbar in the front.&nbsp; This may
408 reside either in the FlexBar_Config.lua file in your flexbar directory
409 (see the file for examples) or may be written in the FlexBar scripts
410 editor.&nbsp; If written in the scripts editor you can omit the quotes and
411 stuff found in the config file.</font></p>
412 <p><font size="2">Only one config may be running at
413 once, and there is a 2 second delay between commands.</font>
414 </p></td></tr>
415 <tr><td width="100%"><font
416 size=2><strong>/flexbar loadprofile profile=
417 'profile name' </font></strong></td></tr><tr><td><font size="2">The default profile for your
418 character is saved under &lt;character name&gt; of &lt;realm name&gt; - IE
419 Dhargo of Silver Hand.&nbsp; It is also Auto-loaded on logging in -- this
420 command is for loading another character's profile, or a saved backup of
421 your profile.&nbsp; Note that, while it changes all the info, any
422 currently remapped buttons may not be mapped back, so you may need to do a
423 /console reloadui to force everything to fully reload.&nbsp; One use for
424 this is saving a back up of a good setup before experimenting, then
425 reloading it if you mess up.&nbsp; IE - if I saved one under 'Dhargos
426 Backup' then:&nbsp; /flexbar loadprofile profile='Dhargos
427 Backup'</font></td></tr>
428 <tr><td width="100%"><font
429 size=2><strong>/flexbar saveprofile profile=
430 'profile name' </font></strong></td></tr><tr><td><font size="2">This saves your current profile under
431 another name.&nbsp; BE CAREFUL - if you specify the profile name of
432 another character, you will overwrite their profile.&nbsp; Primarily used
433 for backing up good configs before experimenting - /flexbar saveprofile
434 profile='Dhargos Backup'.</font></td></tr>
435 <tr><td width="100%"><font
436 size=2><strong> /flexbar resetall
437 confirm= 'yes' </font></strong></td></tr><tr><td><font size="2">Completely resets your character's
438 profile and reloads your UI - unless you backed it up, all your settings
439 are lost.</font></td></tr>
440 <tr><td width="100%"><font
441 size=2><strong> /flexbar restore
442 confirm= 'yes' </font></strong></td></tr><tr><td><font size="2">When you do a loadconfig command, a
443 temporary copy of your old profile is stored.&nbsp; This does not last
444 past logout/reloadui.&nbsp; Only one level is saved.&nbsp; Typing /flexbar
445 restore confirm='yes' will return you to that state.&nbsp; NOTE -&nbsp;
446 any remapped buttons will stay remapped until you /console
447 reloadui.</font></td></tr>
448 <tr><td width="100%"><font
449 size=2><strong>/flexbar safeload state= &lt;'on'
450 } 'off'&gt; </font></strong></td></tr><tr><td><font size="2">Safeload should be
451 obsolete.</font></td></tr>
452 <tr><td width="100%"><font
453 size=2><strong>/flexbar tooltip state=&lt;'on' |
454 'off'&gt;&lt; /STRONG&gt; </font></strong></td></tr><tr><td><font size="2">Turns on and off showing of tooltips
455 when you mouse over flexbar buttons.&nbsp; IE /flexbar tooltip state='off'
456 turns them off.&nbsp; (I find them annoying mostly)&nbsp; Deprecated in
457 favor of the Global Options panel (see keybindings under the main game
458 menu to bind a key to global options or to the FlexBar main menu to access
459 the global options panel)</font></td></tr>
460 <tr><td width="100%"><font
461 size=2><strong>/flexbar verbose state= &lt;'on'
462 | 'off'&gt; </font></strong></td></tr><tr><td><font size="2">Turns on or off detailed reporting of
463 what flexbar is doing - helpful for trouble shooting, but need to be OFF
464 for game play (trust me :) ) -- /flexbar verbose state='off' -- Deprecated
465 in favor of Global Options - see /flexbar tooltip.</font></td></tr>
466 <tr><td width="100%"><font
467 size=2><strong>/flexbar scripts</strong> </font></td></tr><tr><td><font size="2">Opens and closes the Scripts editor -
468 deprecated in favor of the keybinding / Flexbar main menu.</font></td></tr>
469 <tr>
470 <td width="100%">
471 <p align="center"><font size="2">Flex Action
472 Commands</font></p></td></tr>
473 <tr><td width="100%"><font
474 size=2><strong>/flexbar flexmacro id=#
475 texture= 'texturename'&nbsp; name=
476 'macro name'&nbsp;macro= 'macro'[toggle= 'true']
477 [reset= 'true'= ]</strong> </font></td></tr><tr><td>
478 <p><font size="2">ALL flexactions are attached to the
479 ID, NOT the button.&nbsp; This allows them to move with remaps just like
480 regular actions.&nbsp; Also note, currently there is not sanity check, if
481 you do a flexmacro on an ID with a FlexScript it will overwrite it.&nbsp;
482 It however will not let you attach one to an ID with a standard game
483 action on it.</font></p>
484 <p><font size="2">ID is a number from 1-120 (the maximum
485 ID allowed in WoW).&nbsp; Texture is the picture you want on the button -
486 you can either specify the texture from the list you'll find if you use
487 Blizzard's tool to unpack all the UI files OR you can use the followint
488 %variables:&nbsp; %backpack will give the backpack texture, %button##,
489 where ## is 1-120 will give teh texture currently on the named button and
490 %macro## where ## is a number from 1-430 (I think) will give you the icon
491 from the macro icon selection panel.&nbsp; The count left to right,. top
492 to bottom.&nbsp; So, %macro 21 is the 5th row, first icon on the
493 panel.&nbsp; A gui to select these will be coming.&nbsp; Name is a name
494 for the macro, this will eventually be displayed where Blizzard displays
495 their macro names, I just didn't do it for 1.37.&nbsp; Macro either the
496 macro text to perform (EG "/dance") or the name of a multiline macro you
497 created in the Scripts editor and saved.&nbsp; This must be exactly as you
498 saved it - capitalization and all.&nbsp;&nbsp; Another form of multiline
499 macro may also be used macro= ['/dance' /fbwait 30' '/salute'] will
500 execute those commands as a 3 line macro.</font></p>
501 <p><font size="2">If toggle is true and there is already
502 a flexmacro on the button, it will erase that macro.&nbsp; If reset is
503 true it will clear the macro.</font></p>
504 <p><font size="2">Example 1:&nbsp; /flexbar flexmacro
505 id=120 texture='%macro120' name='DANCE' macro='/dance'</font></p>
506 <p><font size="2">will create a macro that makes you
507 dance.&nbsp; If you haven't remapped button 120's ID, it will show up on
508 button 120, and any button you remap to ID 120.</font></p>
509 <p><font size="2">Example 2:&nbsp; /flexbar flexmacro
510 id=120 texture='%macro120' name='Dance2' macro='dance macro'</font></p>
511 <p><font size="2">If you have created a macro
512 like:</font></p>
513 <p><font size="2">/em is going nuts cause he wants to
514 dance</font></p>
515 <p><font size="2">/fbdoin 30 /dance</font></p>
516 <p><font size="2">will create a macro that makes you
517 emote "Dhargo is going crazy because he wants to dance" then executes the
518 dance emote in 3 seconds.&nbsp; If you haven't remapped button 120's ID,
519 it will show up on button 120, and any button you remap to ID
520 120.</font></p>
521 <p><font size="2">Note: to remove flexscript settings&nbsp;from a button
522 completely use&nbsp;<!--StartFragment --></font><font size="3"> /flexbar
523 flexmacro id=# reset='true' texture=' ' macro=' ' name=' '
524 </font></p></td></tr>
525 <tr><td width="100%"><font
526 size=2><strong>/flexbar flexscript id=# texture= 'texture
527 name'&nbsp;name= 'name' script= 'script'[toggle= 'true']
528 [reset= 'true'= ]</strong> </font></td></tr><tr><td>
529 <p><font size="2">Essentially like flexmacro, but uses
530 lua scripts instead:</font></p>
531 <p><font size="2">Example 1: /flexbar flexscript id=120
532 texture='%backpack' name='OpenBags' script='OpenAllBags()'</font></p>
533 <p><font size="2">creates an action at ID 120 that will
534 open/close all your bags when you click it.</font></p>
535 <p><font size="2">Example 2:&nbsp; If you have the
536 following script in the editor</font></p>
537 <p><font size="2">if FBConditions["hasaura"]("Battle
538 Stance") then</font></p>
539 <p><font size="2">&nbsp;&nbsp;&nbsp;
540 FB_CastSpellByName("Overpower")</font></p>
541 <p><font size="2">else</font></p>
542 <p><font size="2">&nbsp;&nbsp;&nbsp;
543 FB_CastSpellByName("Battle Stance")</font></p>
544 <p><font size="2">end</font></p>
545 <p><font size="2">Then save it as "my
546 overpower"</font></p>
547 <p><font size="2">/flexbar flexscript id=120
548 texture='%macro120' name='overpower' script='my overpower' </font></p>
549 <p><font size="2">will put an action&nbsp; on ID 120
550 that will check for battle stance and cast overpower if you're in it,
551 otherwise cast battle stance.</font></p>
552 <p><font size="2">The advantage of these is the
553 character limit for the editor is 10240 characters rather than 256 for
554 macros.</font></p>
555 <p><font size="2">Note: to remove flexscript settings&nbsp;from a button
556 completely use&nbsp;<!--StartFragment --></font><font size="3"> /flexbar
557 flexscript id=# reset='true' texture=' ' script=' ' name=' '
558 </font></p></td></tr>
559 <tr><td width="100%"><font
560 size=2><strong>/flexbarflexpet id= #&nbsp;petid= # '[toggle= 'true'][reset= 'true'= ]</strong>
561 </font></td></tr><tr><td>
562 <p><font size="2">Set's the specified ID to mimic the
563 specified pet button.&nbsp; Pet ID is the number of the button counting
564 from one starting at the left of the default pet bar.&nbsp; Note
565 a&nbsp;couple of limitations in these:&nbsp; 1 - you can't drag pet
566 actions into them at this time, you must show the original pet bar and put
567 the pet actions in there - the flex buttons will update to match.&nbsp;
568 2.&nbsp; If the mimiced pet button has no action and you have hidegrid on,
569 the button will not hide.</font></p>
570 <p><font size="2">Example:&nbsp; /flexbar flexpet id=1
571 petid= 1&lt; /FONT&gt;</p>
572 <p><font size="2">Any button with id 1 will now display
573 the the icon from and execute the action on pet button 1 (usually
574 "attack").</font>
575 </p></font></td></tr>
576 <tr><td width="100%"><font
577 size=2><strong> /flexbar clearflexid= #</font></strong></td></tr><tr><td>
578 <p><font size="2">Clear a flex action off the specified
579 ID</font></p></td></tr>
580 <tr><td width="100%"><font
581 size=2><strong>/flexbar runmacro macro= 'macro' [on='event']
582 [target= &lt;target&gt;] [if= 'condition'] [in=#]
583 [tname= &lt;timername&gt;] [ttoggle=
584 'true']</font></strong></td></tr><tr><td><font size="2">This is used to run a macro on a
585 specified event/time/if condition.&nbsp; THIS CAN NOT BE USED TO AUTOCAST
586 A SPELL - that is not allowed by the game engine.&nbsp; The only way to
587 cast a spell in here is if it comes from a buttonclick event - and that is
588 deprecated in favor of flex actions.&nbsp;&nbsp; Macro may be either a
589 direct macro (macro='/dance') or the name of a mutiline macro from the
590 scripts editor.&nbsp; Another form of multiline macro may also be used
591 macro= ['/dance'/fbwait 30' '/salute'] will execute those commands as a 3
592 line macro.</font></td></tr>
593 <tr><td width="100%"><font
594 size=2><strong>/flexbar runscript script= 'script'
595 [on='event'] [target= &lt;target&gt;] [if= 'condition'] [in=#]
596 [tname= &lt;timername&gt;] [ttoggle=
597 'true']</font></strong></td></tr><tr><td><font size="2">This is used to run a&nbsp;script on
598 a specified event/time/if condition.&nbsp; THIS CAN NOT BE USED TO
599 AUTOCAST A SPELL - that is not allowed by the game engine.&nbsp; The only
600 way to cast a spell in here is if it comes from a buttonclick event - and
601 that is deprecated in favor of flex actions.&nbsp;&nbsp;Script may be
602 either a direct lua command&nbsp;(macro='OpenAllBags()') or the name of
603 a&nbsp;long script from the scripts editor.</font></td></tr>
604 <tr><td width="100%"><font
605 size=2><strong>/flexbar settexture id=
606 [texture= ] [toggle= 'true'][reset= 'true'=
607 ][on= 'event'] [target= &lt;target&gt;][if='condition']
608 [in=#] [tname= &lt;timer name&gt;&lt;timername&gt;]
609 [ttoggle=
610 'true']</font></strong></td></tr><tr><td><font size="2">DEPRECATED in 1.37 - was the original
611 code to attach textures to AutoItems, FlexMacros, FlexScripts</font></td></tr>
612 <tr>
613 <td width="100%">
614 <p align="center"><font size="2">Event Commands
615 (deprecated - see event editor)</font></p></td></tr>
616 <tr><td width="100%"><font
617 size=2><strong> /flexbar deleteevent
618 event= # </font></strong></td></tr><tr><td><font size="2">DEPRECATED IN FAVOR OF THE EVENT
619 EDITOR</font></td></tr>
620 <tr><td width="100%"><font
621 size=2><strong>/flexbar listevents</strong> </font></td></tr><tr><td><font size="2">DEPRECATED IN FAVOR OF THE EVENT
622 EDITOR</font></td></tr>
623 <tr>
624 <td width="100%">
625 <p align="center"><font size="2">Commands to display usage
626 lists</font></p></td></tr>
627 <tr><td width="100%"><font
628 size=2><strong>/flexbar appearance</strong> </font></td></tr><tr><td><font size="2">Lists all appearance
629 commands</font></td></tr>
630 <tr><td width="100%"><font
631 size=2><strong>/flexbar eventhelp</strong> </font></td></tr><tr><td><font size="2">Lists all event commads (obsolete as
632 they are)</font></td></tr>
633 <tr><td width="100%"><font
634 size=2><strong>/flexbar grouphelp</strong> </font></td></tr><tr><td><font size="2">Lists all group commands</font></td></tr>
635 <tr><td width="100%"><font
636 size=2><strong>/flexbar mischelp</strong> </font></td></tr><tr><td><font size="2">Lists all
637 misc.&nbsp;commands</font></td></tr>
638 <tr><td width="100%"><font
639 size=2><strong>/flexbar movement</strong> </font></td></tr><tr><td><font size="2">Lists all movement
640 commands</font></td></tr>
641  
642 </table></p>
643 </body>
644 </html>