wow/ouroloot: verbage.lua comparison

comparison verbage.lua @ 142:375059a11c1d 2.21.0

Updates for WoD. - Basic WoD changes (TOC bump, LE_* constants, etc) - The instance_abbrev table is now indexed by InstanceMapID values; the old method is still supported for transition. - Some initial placeholder values for WoD until we actually start seeing them.

author	Farmbuyer of US-Kilrogg <farmbuyer@gmail.com>
date	Thu, 13 Nov 2014 22:12:33 -0500
parents	2731702567c4
children	63bda09d88fe

comparison

equal deleted inserted replaced

-:13d81d7faa0a
+:375059a11c1d
 <www.curse.com/addons/wow/ouroloot>
 or send them to <farmbuyer@gmail.com> in non-HTML format.
-If you have downloaded this addon from anywhere other than Curse or WoWInterface,
+If you have downloaded this addon from anywhere other than Curse or
-then it is probably outdated at best or stuffed full of |cffff335dmalware and
+WoWInterface, then it is probably outdated at best or stuffed full
-viruses|r at worst.  Get your addons from reputable safe sites!
+of |cffff335dmalware and viruses|r at worst.  Get your addons from reputable
+safe sites!
 ]]
 T.basic = [[
 The </ouroloot> command opens this display.  The buttons
-on the right side control operation and are mostly self-explanatory.  Hovering over
+on the right side control operation and are mostly self-explanatory.  Hovering
-things will usually display some additional text in the gray line at the bottom.
+over things will usually display some additional text in the gray line at the
+bottom.
-Each tab on the left side can additionally create extra contols in the lower right
-section (with the same name as the tab).
+Each tab on the left side can additionally create extra contols in the lower
+right section (with the same name as the tab).
 The first tab on the left side, <Loot>, is where everything goes to and comes
-from.  Looting events and Deadly Boss Mods notifications go to the <Loot> tab; the
+from.  Looting events and Deadly Boss Mods notifications go to the <Loot> tab;
-other tabs are all generated from the information in the <Loot> tab.
+the other tabs are all generated from the information in the <Loot> tab.
-|cffff335dNote about these Help pages:|r  The category "titles" on the left side
+|cffff335dNote about these Help pages:|r  The category "titles" on the left
-have their own help text, in addition to the more specific entries in the expanded
+side have their own help text, in addition to the more specific entries in the
-list.  Read those first before expanding the categories or you'll miss stuff.
+expanded list.  Read those first before expanding the categories or you'll
+miss stuff.
 ]]
 T.basic_loot = [[
-A "loot row" in the first tab has three columns:  the item, the recipient, and any
+A "loot row" in the first tab has three columns:  the item, the recipient, and
-extra notes.
+any extra notes.
 <Mouse Hover>
 Hovering the mouse over the first column will display the item tooltip.
 Hovering over the second column will display a tooltip with the loot that person
 has received.  If they've won more than 10 items, the list is cut off with '...'
-at the end; to see the full list, use the right-click +Show only this player> option
+at the end; to see the full list, use the right-click +Show only this player>
-instead.
+option instead.
 <Right-Click>
 Right-clicking a loot row shows a dropdown menu.
 treatment of that loot entry (e.g., marking as offspec).  Using any of those
 options will change the text in the third column, which will then affect the
 text in the generated tabs, such as forum markup.
 Right-clicking in the second column allows you to temporarily remove all other
-players from the loot display.  Use the reset button in the lower-right corner to
+players from the loot display.  Use the reset button in the lower-right corner
-restore the display to normal.  The menu also allows you to +reassign> loot from
+to restore the display to normal.  The menu also allows you to +reassign> loot
-one player to another; if the new recipient is not in the raid group at the time,
+from one player to another; if the new recipient is not in the raid group at
-use the +Enter name...> option at the bottom of the list of names to type the
+the time, use the +Enter name...> option at the bottom of the list of names to
-name into a text box.  If your raid takes advantage of the ability to trade
+type the name into a text box.  If your raid takes advantage of the ability to
-soulbound items, you will need to reassign the item here for the generated text
+trade soulbound items, you will need to reassign the item here for the
-to be factually correct.
+generated text to be factually correct.
-See the help screen on "Boss Entries" for the +Insert new boss kill event> option.
+See the help screen on "Boss Entries" for the +Insert new boss kill event>
+option.
 <Double-Click>
 Double-clicking a loot row in the third ("Notes") column allows you to edit that
 field directly.  The color of the text will still depend on any +Mark as ___>
 actions done to that loot row, whether automatically or by hand.
 ]]
 T.basic_boss = [[
-Boss wipe/kill entries are entirely dependant on Deadly Boss Mods being enabled and
+Boss wipe/kill entries are entirely dependant on Deadly Boss Mods being enabled
-up-to-date.  The typical sequence of events for our usual raids goes like this:
+and up-to-date.  The typical sequence of events for our usual raids goes like
+this:
-We make four or five attempts on Baron Steamroller.  As DBM registers that combat
-ends, a <wipe> event is entered on the loot display along with the duration of the
+We make four or five attempts on Baron Steamroller.  As DBM registers that
-fight.  If the loot display is opened, the wipes will be visible with a light gray
+combat ends, a <wipe> event is entered on the loot display along with the
-background.
+duration of the fight.  If the loot display is opened, the wipes will be
+visible with a light gray background.
 After reminding the melee dps to move out of fire, we manage to kill
-Steamroller.  When DBM registers the win, a <kill> event is entered on the display
+Steamroller.  When DBM registers the win, a <kill> event is entered on the
-with a dark gray background.
+display with a dark gray background.  All previous <wipe>s are removed and
-All previous <wipe>s are removed and collapsed into the <kill> event.  The final
+collapsed into the <kill> event.  The final <kill> event shows the duration
-<kill> event shows the duration of the successful fight and the number of attempts
+of the successful fight and the number of attempts needed (or "one-shot" if
-needed (or "one-shot" if we're competent).
+we're competent).
-Sometimes this goes wrong, when DBM misses its own triggers.  If DBM does not catch
+Sometimes this goes wrong, when DBM misses its own triggers.  If DBM does not
-the start of the boss fight, it can't register the end, so nothing at all is
+catch the start of the boss fight, it can't register the end, so nothing at
-recorded.  If the fight was a win but DBM does not catch the victory conditions,
+all is recorded.  If the fight was a win but DBM does not catch the victory
-then DBM will (after several seconds) decide that it was a wipe instead.  And
+conditions, then DBM will (after several seconds) decide that it was a wipe
-sometimes useful loot will drop from trash mobs, which DBM knows nothing about.
+instead.  And sometimes useful loot will drop from trash mobs, which DBM knows
+nothing about.
 For all those reasons, right-clicking on a "boss row" will display options for
 +Insert new boss kill event>, and for toggling a <wipe> into a <kill>.  We often
 insert bosses named "trash" to break up the display and correct the forum markup
 listing.
 ]]
 T.tracking = [[
 The first button underneath +Main> in the right-hand column displays the current
 status of the addon.  If it is disabled, then no recording, rebroadcasting, or
-listening for rebroadcasts is performed.  Any loot already recorded will be restored
+listening for rebroadcasts is performed.  Any loot already recorded will be
-across login sessions no matter the status.
+restored across login sessions no matter the status.
 You can turn on tracking/broadcasting before joining a raid.  If you join a raid
 and the addon has not been turned on, then a popup dialog will ask for
 instructions.  (This can be turned off in the advanced <Options>.)
-The addon tries to be smart about logging on during a raid (due to a disconnect or
+The addon tries to be smart about logging on during a raid (due to a disconnect
-relog).  If you log in, are already in a raid group, and loot has already been
+or relog).  If you log in, are already in a raid group, and loot has already
-stored from tracking, it will re-enable itself automatically.
+been stored from tracking, it will re-enable itself automatically.
-The intent of the addon design is that, after the end of a raid, all the generated
+The intent of the addon design is that, after the end of a raid, all the
-markup text is done, optionally saved (see "Generated Texts - Saved Texts"), and
+generated markup text is done, optionally saved (see "Generated Texts - Saved Texts"),
-then cleared from
+and then cleared from storage altogether.  As a result, if you login with
-storage altogether.  As a result, if you login with restored loot information but
+restored loot information but are not in a raid, the addon will do nothing on
-are not in a raid, the addon will do nothing on its own -- but will assume that
+its own -- but will assume that you've forgotten to finish those steps and will
-you've forgotten to finish those steps and will yammer about it in the chat window
+yammer about it in the chat window as a reminder.
-as a reminder.
+The +Threshold> drop-down has no connection at all with any current loot
-The +Threshold> drop-down has no connection at all with any current loot threshold
+threshold set by you or a master looter.
-set by you or a master looter.
 ]]
 T.tracking_enabled = [[
 Full tracking records all loot events that fulfill these criteria:
 2)  The loot is not in the list of items to filter out (see the <Options> tab).
 These are things like shards from disenchanting and Darkmoon Faire quest items.
 3)  <You can see the loot event.>  More precisely, you need to be close enough
-to the recipient of the loot to be able to see "So-And-So receives loot: [Stuff]"
+to the recipient of the loot to be able to see "So-And-So receives loot:
-in your chat window, even if you have those actual loot messages turned off.
+[Stuff]" in your chat window, even if you have those actual loot messages
+turned off.
 It is (3) that causes complications.  A master looter can assign loot to anybody
 anywhere in a raid instance, but the range on detecting loot events is much
 smaller.  If your raid does not use master looting then you merely need to be
 close enough to the boss corpse, presuming that the winners will need to walk
 over to get their phat epix.
 If you do use master looter, then you have two options:  first, you can
-require players
+require players who might get loot to stay near the boss.  You would then also
-who might get loot to stay near the boss.  You would then also need to stay near
+need to stay near the boss to detect the loot event.  (This can be less hassle
-the boss to detect the loot event.  (This can be less hassle if you are also
+if you are also the loot master.)  The downside is that other players moving
-the loot master.)  The downside is that other players moving on to fight to the
+on to fight to the next boss are doing so without the help of their teammates.
-next boss are doing so without the help of their teammates.
 The other option is to ask other players to also install Ouro Loot, and for
 them to turn on the "Rebroadcasting" feature.  Any loot events which they can
 see will be communicated to you.  Then it only becomes necessary for at least
 one person to be close enough to the loot recipient to see the item awarded,
 and you will record it no matter how far away you are -- even back in Orgrimmar.
-If you have Full Tracking enabled, then you are also automatically rebroadcasting.
+If you have Full Tracking enabled, then you are also automatically
-Having more than one player with Full Tracking turned on is probably a good
+rebroadcasting.  Having more than one player with Full Tracking turned on is
-idea, in case one of the trackers experiences a game crash or is suddenly kidnapped
+probably a good idea, in case one of the trackers experiences a game crash or
-by robot ninja monkeys.
+is suddenly kidnapped by robot ninja monkeys.
 ]]
 T.tracking_bcast = [[
-The simplest method of operation is only rebroadcasting the loot events that you
+The simplest method of operation is only rebroadcasting the loot events that
-see, as you see them.  Nothing is recorded in your local copy of the addon.
+you see, as you see them.  Nothing is recorded in your local copy of the addon.
-If you logout for any reason, the addon will not reactivate when you log back in.
+If you logout for any reason, the addon will not reactivate when you log back
+in.
 You can use </ouroloot bcast> or </ouroloot broadcast> to turn on rebroadcasting
 without opening the GUI.
 ]]
 T.texts = [[
 The middle tabs are simply large editable text boxes.  Their text is initially
-generated from
+generated from the information stored on the main <Loot> tab, at the time you
-the information stored on the main <Loot> tab, at the time you click on the tab.
+click on the tab.  Not every bit of information that we want in the generated
-Not every bit of information that
+text is always available, or depends on things that the game itself can't know.
-we want in the generated text is always available, or depends on things that the
+So you can edit the text in the tabs and your edits will be preserved.
-game itself can't know.  So you can edit the text in the tabs and your edits will
-be preserved.
 Each time you click one of the text tabs, every new entry on the <Loot> tab
 since the last time this tab was shown will be turned into text.
-Clicking the +Regenerate> button will throw away all the text on that tab, including
+Clicking the +Regenerate> button will throw away all the text on that tab,
-any edits you've made, and recreate all of it from scratch.  If you've accidentally
+including any edits you've made, and recreate all of it from scratch.  If
-deleted the text from the editbox, or you've made manual changes to the <Loot> tab,
+you've accidentally deleted the text from the editbox, or you've made manual
-you can use this button to start over.
+changes to the <Loot> tab, you can use this button to start over.
 You can click in an editbox and use Control-A to select all text, then Control-C
 to copy it to the system clipboard for subsequent pasting into a web browser or
 whatever.  If you're on a Mac, you probably already know the equivalent keys.
 ]]
 The [url] choice defaults to using Wowhead.  If you have the [item] extension
 for your BBcode installed, you can use either of those choices too.  The "by ID"
 variant is good for heroic raid items that share names with nonheroic items,
 but the raw output is harder to read in the text tab.
-You can also specify a custom string.  Formatting is done with these replacements:
+You can also specify a custom string.  Formatting is done with these
+replacements:
 +$N>:  item name|r
 +$I>:  (capital "eye", not "ell") numeric item ID|r
 does not generate any text until the end of the raid, simplifying things
 considerably.
 ]]
 T.texts_other = [[
-So far the only other generated text is the <Attendance> tab, an alphabetized list
+So far the only other generated text is the <Attendance> tab, an alphabetized
-on a per-boss basis.  Players who are probably inside the raid are grouped
+list on a per-boss basis.  Players who are probably inside the raid are grouped
-under [:PLUS:], and the remaining players are under [-].  "Probably inside" is an
+under [:PLUS:], and the remaining players are under [-].  "Probably inside" is
-assumption that groups 1 and 2 are raiding in a 10-player instance, groups 1-5
+an assumption that groups 1 and 2 are raiding in a 10-player instance,
-are raiding in a 25-player instance, and so forth.
+groups 1-5 are raiding in a 25-player instance, and so forth.
 Other addons can register their own text tabs and corresponding generation
 functions.  If you want to be able to feed text into an offline program (for
 example, a spreadsheet or DKP tracker), then this may be of use to you.
 Ideas for more tabs?  Tell me!
 ]]
 T.texts_saved = [[
-The contents of the <Forum Markup>, <Attendance>, and other such tabs can be saved,
+The contents of the <Forum Markup>, <Attendance>, and other such tabs can be
-so that they will not be lost when you use the +Clear> button.
+saved, so that they will not be lost when you use the +Clear> button.
 Do any edits you want to the generated text tabs, then click the +Save Current As...>
-button on the right-hand side.  Enter a short descriptive reminder (for example,
+button on the right-hand side.  Enter a short descriptive reminder (for
-"thursday hardmodes") in the popup dialog.  The texts will remain in their tabs,
+example, "thursday hardmodes") in the popup dialog.  The texts will remain in
-but clearing loot information will not lose them now.
+their tabs, but clearing loot information will not lose them now.
 All saved texts are listed on the right-hand side.  Clicking a saved text name
-lets you +Load> or +Delete> that saved set.  The primary <Loot> tab is not saved
+lets you +Load> or +Delete> that saved set.  The primary <Loot> tab is not
-and restored by this process, only the generated texts.  This also means you cannot
+saved and restored by this process, only the generated texts.  This also means
-+Regenerate> the texts.
+you cannot +Regenerate> the texts.
 ]]
 T.history = [[
 The <History> tab maintains a list of all loot.  It is intended to help answer
-questions such as "When was the last time PlayerX won something?" and "How much stuff
+questions such as "When was the last time PlayerX won something?" and "How
-has PlayerY gotten lately?"  The history tab is, by design, not as configurable
+much stuff has PlayerY gotten lately?"  The history tab is, by design, not as
-as the main <Loot> tab; entries cannot be manually edited and so forth.
+configurable as the main <Loot> tab; entries cannot be manually edited and so
+forth.
-This loot history is the only "live" data tab which persists across the +Clear Loot> command.
-For this reason, very little information is stored:  only the recipient, the item,
+This loot history is the only "live" data tab which persists across the
-and a textual timestamp.  Boss names, offspecs, and other notes are not preserved.
++Clear Loot> command.  For this reason, very little information is stored:
+only the recipient, the item, and a textual timestamp.  Boss names, offspecs,
-The default history window shows the most recent item received by each person.  It
+and other notes are not preserved.
-is sorted with the most recent loot at the top, towards older loot at the bottom.
-You can click the column headers to rearrange the rows, but doing so repeatedly can
+The default history window shows the most recent item received by each person.
-lead to odd display issues.
+It is sorted with the most recent loot at the top, towards older loot at the
+bottom.  You can click the column headers to rearrange the rows, but doing so
-Left-clicking a row will change the window to display all recorded loot for that
+repeatedly can lead to odd display issues.
-player.  While on that display, right-clicking any row will return to showing the
-most recent single item for all players.
+Left-clicking a row will change the window to display all recorded loot for
+that player.  While on that display, right-clicking any row will return to
-Histories are maintained per-realm.  This refers to the realm you are on when the
+showing the most recent single item for all players.
-loot drops, not the realm of the player receiving it (in the case of cross-realm
-groups).  If you play multiple characters on the same realm, history will accumulate
+Histories are maintained per-realm.  This refers to the realm you are on when
-across all your raids.  To change the displayed realm, use the dropdown menu in
+the loot drops, not the realm of the player receiving it (in the case of
-the lower right corner.
+cross-realm groups).  If you play multiple characters on the same realm,
+history will accumulate across all your raids.  To change the displayed realm,
-The +Regenerate> button permanently erases the history of the displayed realm, and
+use the dropdown menu in the lower right corner.
-creates fresh entries using whatever loot information is currently on the <Loot> tab.
-Be aware that the <Loot> tab does not track realms, so if you have gathered data
+The +Regenerate> button permanently erases the history of the displayed realm,
-for players on realm A, but are displaying realm B when you click the Regenerate button,
+and creates fresh entries using whatever loot information is currently on the
-then your history for realm B will be... very odd.
+<Loot> tab.  Be aware that the <Loot> tab does not track realms, so if you have
+gathered data for players on realm A, but are displaying realm B when you click
+the Regenerate button, then your history for realm B will be... very odd.
 +Clear Realm History> and +Clear ALL History> are used to periodically wipe the
 slate clean.  They do not generate any new entries from existing loot.
 +Clear Older> deletes history information older than a certain threshold (by
 +Mark as disenchanted> or +Mark as guild vault> will remove the item from
 history altogether.  Remarking such an item as +normal> or +offspec> will
 replace the item back into the player's history.
 Note:  the first time you display the histories during a game session, you will
-likely see several items listed as +UNKNOWN>.  This is not a bug; these items are
+likely see several items listed as +UNKNOWN>.  This is not a bug; these items
-simply not in your local game cache.  WoW will automatically retrieve the missing
+are simply not in your local game cache.  WoW will automatically retrieve the
-data after several seconds, but the display will not update until the next time
+missing data after several seconds, but the display will not update until the
-the History tab is shown.  Starting in WoW 4.0, the local game cache is not preserved
+next time the History tab is shown.  Starting in WoW 4.0, the local game cache
-across play sessions, so the +UNKNOWN> entries will pop up from time to time.
+is not preserved across play sessions, so the +UNKNOWN> entries will pop up
+from time to time.
 ]]
 T.tips = [[
 The |cffff8000[Ouro Loot]|r "legendary item" displayed at the start of all
 chat messages is a clickable link.  Clicking opens the main display, and if
 possible will jump to and/or highlight the relevent data which caused the
 associated chat message to be printed in the first place.
 The "Be chatty" options on the <Options> tab will cause a chat message to be
 printed after various events, thus providing a way to quickly view them.
-If you are broadcasting to somebody else who is tracking, you should probably be
+If you are broadcasting to somebody else who is tracking, you should probably
-using the same threshold.  If yours is lower, then some of the loot you broadcast
+be using the same threshold.  If yours is lower, then some of the loot you
-to him will be ignored.  If yours is higher, then you will not be sending information
+broadcast to him will be ignored.  If yours is higher, then you will not be
-that he would have recorded.  The "correct" setting depends on what your guild wants
+sending information that he would have recorded.  The "correct" setting depends
-to track.
+on what your guild wants to track.
-Ticking the "notraid" box in advanced debugging <Options>, before enabling tracking,
+Ticking the "notraid" box in advanced debugging <Options>, before enabling
-will make the tracking work outside of a raid group.  Communication functions
+tracking, will make the tracking work outside of a raid group.  Communication
-will behave a little strangely when doing this.  Be sure to check the threshold!
+functions will behave a little strangely when doing this.  Be sure to check
-You can also use <"/ouroloot debug notraid"> instead.
+the threshold!  You can also use <"/ouroloot debug notraid"> instead.
-Using the "Saved Texts" feature plus the +Clear> button is a great way of putting
+Using the "Saved Texts" feature plus the +Clear> button is a great way of
-off pasting loot into your guild's website until a more convenient time.
+putting off pasting loot into your guild's website until a more convenient time.
 Shift-clicking an item in the <Loot> or <History> display will paste it into an
 open chat editbox.
 ]]
 T.tips_slashies = [[
 A text field in the <Options> tab lets you use additional slash commands as a
 shortcut for </ouroloot>.  The author prefers </ol>, as an example.  The
 default used to be </loot> until that became a builtin command in MoP.
-If you give an unrecognized argument to a slash command, it will
+If you give an unrecognized argument to a slash command, it will search the
-search the tab titles left to right for a title beginning with the same letters as
+tab titles left to right for a title beginning with the same letters as
 the argument, and open the display to that tab.  For example, <"/ol a"> would
 open the <Attendance> tab, and <"/ol o"> would open the <Options> tab.  If
 you had added a theoretical <EQDKP> tab, then <"/ol eq"> would be the fastest
 way to see it.  Only enough text to be unambiguous is required, and all of it
 is case-insensitive.
 searching is used for names as for tab titles, so <"/ol hi farm"> is enough to
 trigger Farmbuyer's history display (as long as nobody named Farmville joins
 the raid), and so forth.
 The </ouroloot> command can take arguments to do things without going through
-the UI.  Parts given in *(angle brackets)* are required, parts in [square brackets]
+the UI.  Parts given in *(angle brackets)* are required, parts
-are optional:
+in [square brackets] are optional:
 +help>:  opens the UI to the help tab|r
 +broadcast>/+bcast>:  turns on rebroadcasting|r
 +toggle>:  opens or closes the UI (used mostly in automated wrappers)|r
 +fix ?>:  lists the available automated data integrity fixes|r
-If you use the slash commands to enable tracking or set loot thresholds, you can
+If you use the slash commands to enable tracking or set loot thresholds, you
-give numbers or common names for the threshold.  For example, "0", "poor", "trash",
+can give numbers or common names for the threshold.  For example, "0", "poor",
-"gray"/"grey" are all the same, "4", "epic", "purple" are the same, and so on.
+"trash", "gray"/"grey" are all the same, "4", "epic", "purple" are the same,
+and so on.
 ]]
 T.tips_prescan = [[
 When loot is manipulated, the history of previous loot entries must be scanned
 to determine whether you already have any information for that loot.  In this
 worth turning on.  This also means that you need to relog or /reload to have
 the option take effect once you enable it.
 ]]
 T.todo = [[
-If you have ideas or complaints or bug reports, first check the Bugs subcategories
+If you have ideas or complaints or bug reports, first check the Bugs
-to see if they're already being worked on.  Bug reports are especially helpful
+subcategories to see if they're already being worked on.  Bug reports are
-if you can include a screenshot (in whatever image format you find convenient),
+especially helpful if you can include a screenshot (in whatever image format
-and a copy of your SavedVariables file.  This is found in your World of Warcraft
+you find convenient), and a copy of your SavedVariables file.  This is found
-installation folder, named "WTF/Account/you/SavedVariables/Ouro_Loot.lua"
+in your World of Warcraft installation folder, named
-(where "you" is your account name).  You may need to compress this file
+"WTF/Account/you/SavedVariables/Ouro_Loot.lua" (where "you" is your account
-before the ticket system will accept it.
+name).  You may need to compress this file before the ticket system will
+accept it.
 Click the "About" line on the left for contact information.
 ]]
 T.todo_gotchas = [[
 realm represented by that same information can yield strange results, including
 outright breakage.
 If you relog (or get disconnected) while in a raid group, behavior when you log
 back in can be surprising.  If you have already recorded loot (and therefore
-the loot list is restored), then OL assumes it's from the current raid and should
+the loot list is restored), then OL assumes it's from the current raid and
-reactivate automatically in full tracking mode.  If you were tracking but no
+should reactivate automatically in full tracking mode.  If you were tracking
-loot had dropped yet (and therefore there was nothing *to* restore), then OL
+but no loot had dropped yet (and therefore there was nothing *to* restore),
-will pop up its reminder and ask again.  Either way, if you were only broadcasting
+then OL will pop up its reminder and ask again.  Either way, if you were only
-then OL will *not* go back to only broadcasting.  This is probably a bug.
+broadcasting then OL will *not* go back to only broadcasting.  This is
+probably a bug.
 The saved texts feature does exactly that: only saves the generated texts, not
 the full loot list.  Restoring will get you a blank first tab and whatever you
 previously had in the various generated text tabs.

Mercurial > wow > ouroloot

comparison verbage.lua @ 142:375059a11c1d 2.21.0