vanilla-wow-addons – Blame information for rev 1
?pathlinks?
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>Getting Started</title> |
||
6 | </head> |
||
7 | <body bgcolor="#ffffff"> |
||
8 | <p align="center"><strong><em><font size="5">Getting Started |
||
9 | with FlexBar</font></em></strong></p> |
||
10 | <p align="left"><strong>Introduction:</strong> Flexbar provides 120 buttons |
||
11 | that can be moved, scaled, shaded, hidden, shown and alpha blended completely |
||
12 | independently of one another. This allows you to put just as many buttons |
||
13 | as you need, just where you need.</p> |
||
14 | <p align="left">In additon to basic extra bar functionality, FlexBar employs an |
||
15 | event (think trigger) / action (command) architecture. It is constantly |
||
16 | keeping track of the status of a wide number of things from your buffs to your |
||
17 | health to whether you have a target or not. When it detects a change in |
||
18 | these it raise an event that you can have a command respond to - such as showing |
||
19 | your overpower button when your opponent dodges.</p> |
||
20 | <p align="left">Additionally FlexBar provides some extras that just came with the |
||
21 | territory:</p> |
||
22 | <p align="left">Extra macros/scripts beyond the limit of 18 with a character limit |
||
23 | of 10240 (nearly limitless if you break your scripts into preloaded |
||
24 | functions).</p> |
||
25 | <p align="left">AutoItems - makes it so, when you run out of a potion that was on |
||
26 | a button, the icon stays there, and when you get more, it automatically puts |
||
27 | them back on.</p> |
||
28 | <p align="left">Extra macro commands (these were 5 line bonuses that just expose |
||
29 | some things that flexbar already had in it)</p> |
||
30 | <ul> |
||
31 | <li> |
||
32 | <div align="left">/fbuse Item -- uses an item by name from your |
||
33 | inventory</div></li> |
||
34 | <li> |
||
35 | <div align="left">/fbdoin delay /command -- delays execution of a macro command |
||
36 | for delay tenths of a second</div></li> |
||
37 | <li> |
||
38 | <div align="left">/fbcast -- like cast but will cast pet spells, stances |
||
39 | etc. Also, if you omit the rank it uses the highest rank of that |
||
40 | spell.</div></li> |
||
41 | <li> |
||
42 | <div align="left">/echo #color message -- echos a message above your character's |
||
43 | head in the specified color (white, green, red, blue, cyan, yellow, |
||
44 | magenta). Omitting color makes it white.</div></li> |
||
45 | <li> |
||
46 | <div align="left">/print #color message -- like echo but writes the message to |
||
47 | your chat box.</div></li></ul> |
||
48 | <blockquote dir="ltr" style="MARGIN-RIGHT: 0px"> |
||
49 | <p align="left"><strong>A Note on Performance:</strong> On my low end |
||
50 | system (1.1 GHZ Celeron, 512MB, GF2 MX400) - without any mods I get 21FPS at |
||
51 | the tower of Azora facing the road. With FlexBar installed with 120 |
||
52 | buttons showing and a couple of events (not many), and Auto Performance |
||
53 | Options checked I get 20. With more events this might go lower, but it |
||
54 | shouldn't be much. On the memory side, it may show temporary drain |
||
55 | during configuration, but the amount of that that goes on in normal play is |
||
56 | low and will not force the Lua environment to frequently garbage |
||
57 | collect.</p></blockquote> |
||
58 | <p align="left"><strong>Installation:</strong> If you have already installed |
||
59 | FlexBar, skip this.</p> |
||
60 | <p align="left">If this is the first time you've installed a mod, there are a |
||
61 | couple of preparatory steps to take:</p> |
||
62 | <p align="left">1. Find your World of Warcraft\ directory, inside it, if |
||
63 | there is not a directory name Interface, create it.</p> |
||
64 | <p align="left">2. Inside the Interface\ directory, create a directory named |
||
65 | Addons. </p> |
||
66 | <p align="left">NOTE: A common mistake is to put Addons in the World of |
||
67 | Warcraft\Data\Interface\Addons directory, this is not correct.</p> |
||
68 | <p align="left">3. Unzip FlexBar, put the entire folder in the addons |
||
69 | directory. You should now have a directory that looks something like (mine |
||
70 | is on my D drive) D:\\World of Warcraft\Interface\Addons\FlexBar.</p> |
||
71 | <p align="left">4. Log in, check the Addons GUI (see the button at the |
||
72 | bottom left of the character screen) and verify that FlexBar is installed and |
||
73 | enabled. </p> |
||
74 | <p align="left">5. If, for any reason after a patch FlexBar does not load |
||
75 | because it is out of date, check the "Load out of date addons" box in the Addons |
||
76 | GUI - DO NOT edit the .toc as some people will tell you. This is a sure |
||
77 | way not to know what addon is causing trouble after a patch.</p> |
||
78 | <p align="left"><strong>Getting Started: </strong>A New FlexBar installation |
||
79 | starts with all buttons hidden, in a grid 12 buttons wide by 10 buttons |
||
80 | tall.</p> |
||
81 | <p align="left">The first thing to do is to display a few buttons to play |
||
82 | with: (note: all these commands are covered in depth in the Commands |
||
83 | appendix - including all parameters)</p> |
||
84 | <p align="left">/flexbar show button=1-12</p> |
||
85 | <p align="left">will do the trick.</p> |
||
86 | <p align="left">Now, so you know which is which:</p> |
||
87 | <p align="left">/flexbar text button=1-12 text='%d'</p> |
||
88 | <p align="left">You'll note (if you're not a warrior) that the actions on these |
||
89 | buttons duplicate your default action bar page 1 - this is normal and is a |
||
90 | result of the way WoW allocates Button ID's.*</p> |
||
91 | <p align="left">Now, the initial location is not where you want it, so look to the |
||
92 | top left corner of the button, click on the little handle you see there and drag |
||
93 | the button around.</p> |
||
94 | <p align="left">Once you have them where you want them, you'll often want them to |
||
95 | stay put - /flexbar lock button=1-12 will make them unable to move.</p> |
||
96 | <p align="left">Sometimes you want the buttons to stay put relative to one another |
||
97 | and to drag them as a group:</p> |
||
98 | <p align="left">/flexbar group button=1-12 anchor=1</p> |
||
99 | <p align="left">Now you can drag the entire group as a whole by button 1's |
||
100 | anchor. </p> |
||
101 | <p align="left">Also, sometimes dragging individual buttons is a pain, so :</p> |
||
102 | <p align="left">/flexbar verticalgroup group=1 width=6 </p> |
||
103 | <p align="left">will make that group a 2 button high, 6 button wide bar.</p> |
||
104 | <p align="left">Take a look in the command appendix at the appearance, group and |
||
105 | movement commands for further details.</p> |
||
106 | <p align="left">If all you need is a few extra bars where you need them, that's |
||
107 | all you need to know - but there's more :) See the advanced topics.</p> |
||
108 | <p align="left">*There are only 120 to go around, and any buttons with the same |
||
109 | ID's show the same actions. By default a flexbar buttons ID is the same as |
||
110 | it's number. On the default action bar, the ID for buttons 1-12 on page 1 |
||
111 | are 1-12, on page 2 it's 13-24, on page 3 it's 25-36, on page 4 it's 37-48 , |
||
112 | page 5 it's 49-60 and page 6 it's 61-72. With the exception of Warriors - |
||
113 | page 1 is 73-84 in Battle Stance, 85-96 in Defensive Stance, 97-108 in Berserker |
||
114 | Stance.</p> |
||
115 | </body> |
||
116 | </html> |