Mercurial > wow > ouroloot
diff verbage.lua @ 47:1070a14cfee4
Updated lib-st widget from WRDW. Properly notice new generating tabs. Updated help text.
author | Farmbuyer of US-Kilrogg <farmbuyer@gmail.com> |
---|---|
date | Sat, 28 Jan 2012 18:24:22 +0000 |
parents | 85532921829d |
children | fcc0d0ff5832 |
line wrap: on
line diff
--- a/verbage.lua Sat Jan 21 01:39:44 2012 +0000 +++ b/verbage.lua Sat Jan 28 18:24:22 2012 +0000 @@ -117,8 +117,8 @@ on the right side control operation and are mostly self-explanatory. Hovering 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 of the display. +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 @@ -157,7 +157,7 @@ restore the display to normal. The menu also allows you to +reassign> loot from one player to another; if the new recipient is not in the raid group at the time, use the +Enter name...> option at the bottom of the list of names to type the -name into a text box. If your raid takes advantage of the new ability to trade +name into a text box. If your raid takes advantage of the ability to trade soulbound items, you will need to reassign the item here for the generated text to be factually correct. @@ -179,12 +179,12 @@ fight. If the loot display is opened, the wipes will be visible with a light gray background. -After reminding the dps classes to watch the threat meters, we manage to kill +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 with a dark gray background. All previous <wipe>s are removed and collapsed into the <kill> event. The final <kill> event shows the duration of the successful fight and the number of attempts -needed (or "one-shot" if we manage to be competent). +needed (or "one-shot" if we're competent). Sometimes this goes wrong, when DBM misses its own triggers. If DBM does not catch the start of the boss fight, it can't register the end, so nothing at all is @@ -205,7 +205,7 @@ 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 (by default) a popup dialog will ask for +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 @@ -230,8 +230,8 @@ 1) The loot quality is equal to or better than what you have selected in the +Threshold> drop-down. -2) The loot is not one of the few items hardcoded to not be tracked (badges, -emblems, Stone Keeper Shards, etc). +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]" @@ -254,7 +254,7 @@ 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 Dalaran. +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. Having more than one player with Full Tracking turned on is probably a good @@ -273,7 +273,8 @@ ]] T.texts = [[ -The middle tabs are just large editboxes. Their text is initially generated from +The middle tabs are simply large editable text boxes. Their text is initially +generated from the information stored on the main <Loot> tab, at the time you click on the tab. Not every bit of information that we want in the generated text is always available, or depends on things that the @@ -321,8 +322,9 @@ close the display or click back on the <Loot> tab, your edited text will be preserved for later. -Pro tip #2: Barring things like pro tip #1, the author typically does not -generate any text until the end of the raid. +Pro tip #2: Barring situations like pro tip #1, this addon author typically +does not generate any text until the end of the raid, simplifying things +considerably. ]] T.texts_other = [[ @@ -492,11 +494,12 @@ Using the right-click menu to change an item's treatment (shard, offspec, etc) does not broadcast that change to anyone else who is also tracking. Changing -the item and then selecting "rebroadcast this item" *does* include that extra -info. Doing that on the initial "mark as xxx" action is... tricky. +the item and then selecting "rebroadcast this item" <does> include that extra +info. Automatically doing that on the initial "mark as xxx" action would +be... tricky. -The generated text tries to only list the name of the instance if it has not -already been listed, or if it is different than the instance of the previous +The generated forum text tries to only list the name of the instance if it has +not already been listed, or if it is different than the instance of the previous boss. If you relog, the "last printed instance name" will be forgotten, and you'll see redundant raid instance names appearing in the text. @@ -533,7 +536,7 @@ [40752] = true, -- Emblem of Heroism [40753] = true, -- Emblem of Valor [45624] = true, -- Emblem of Conquest - -- could probably remove the above now + -- could probably remove most of this now [43228] = true, -- Stone Keeper's Shard [47241] = true, -- Emblem of Triumph [49426] = true, -- Emblem of Frost