comparison 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
comparison
equal deleted inserted replaced
46:0b1e703a6954 47:1070a14cfee4
115 T.basic = [[ 115 T.basic = [[
116 The </ouroloot> (and </loot> by default) command opens this display. The buttons 116 The </ouroloot> (and </loot> by default) command opens this display. The buttons
117 on the right side control operation and are mostly self-explanatory. Hovering over 117 on the right side control operation and are mostly self-explanatory. Hovering over
118 things will usually display some additional text in the gray line at the bottom. 118 things will usually display some additional text in the gray line at the bottom.
119 119
120 Each tab on the left side can additionally create extra contols in the lower-right 120 Each tab on the left side can additionally create extra contols in the lower right
121 section of the display. 121 section (with the same name as the tab).
122 122
123 The first tab on the left side, <Loot>, is where everything goes to and comes 123 The first tab on the left side, <Loot>, is where everything goes to and comes
124 from. Looting events and Deadly Boss Mods notifications go to the <Loot> tab; the 124 from. Looting events and Deadly Boss Mods notifications go to the <Loot> tab; the
125 other tabs are all generated from the information in the <Loot> tab. 125 other tabs are all generated from the information in the <Loot> tab.
126 126
155 Right-clicking in the second column allows you to temporarily remove all other 155 Right-clicking in the second column allows you to temporarily remove all other
156 players from the loot display. Use the reset button in the lower-right corner to 156 players from the loot display. Use the reset button in the lower-right corner to
157 restore the display to normal. The menu also allows you to +reassign> loot from 157 restore the display to normal. The menu also allows you to +reassign> loot from
158 one player to another; if the new recipient is not in the raid group at the time, 158 one player to another; if the new recipient is not in the raid group at the time,
159 use the +Enter name...> option at the bottom of the list of names to type the 159 use the +Enter name...> option at the bottom of the list of names to type the
160 name into a text box. If your raid takes advantage of the new ability to trade 160 name into a text box. If your raid takes advantage of the ability to trade
161 soulbound items, you will need to reassign the item here for the generated text 161 soulbound items, you will need to reassign the item here for the generated text
162 to be factually correct. 162 to be factually correct.
163 163
164 See the help screen on "Boss Entries" for the +Insert new boss kill event> option. 164 See the help screen on "Boss Entries" for the +Insert new boss kill event> option.
165 165
177 We make four or five attempts on Baron Steamroller. As DBM registers that combat 177 We make four or five attempts on Baron Steamroller. As DBM registers that combat
178 ends, a <wipe> event is entered on the loot display along with the duration of the 178 ends, a <wipe> event is entered on the loot display along with the duration of the
179 fight. If the loot display is opened, the wipes will be visible with a light gray 179 fight. If the loot display is opened, the wipes will be visible with a light gray
180 background. 180 background.
181 181
182 After reminding the dps classes to watch the threat meters, we manage to kill 182 After reminding the melee dps to move out of fire, we manage to kill
183 Steamroller. When DBM registers the win, a <kill> event is entered on the display 183 Steamroller. When DBM registers the win, a <kill> event is entered on the display
184 with a dark gray background. 184 with a dark gray background.
185 All previous <wipe>s are removed and collapsed into the <kill> event. The final 185 All previous <wipe>s are removed and collapsed into the <kill> event. The final
186 <kill> event shows the duration of the successful fight and the number of attempts 186 <kill> event shows the duration of the successful fight and the number of attempts
187 needed (or "one-shot" if we manage to be competent). 187 needed (or "one-shot" if we're competent).
188 188
189 Sometimes this goes wrong, when DBM misses its own triggers. If DBM does not catch 189 Sometimes this goes wrong, when DBM misses its own triggers. If DBM does not catch
190 the start of the boss fight, it can't register the end, so nothing at all is 190 the start of the boss fight, it can't register the end, so nothing at all is
191 recorded. If the fight was a win but DBM does not catch the victory conditions, 191 recorded. If the fight was a win but DBM does not catch the victory conditions,
192 then DBM will (after several seconds) decide that it was a wipe instead. And 192 then DBM will (after several seconds) decide that it was a wipe instead. And
203 status of the addon. If it is disabled, then no recording, rebroadcasting, or 203 status of the addon. If it is disabled, then no recording, rebroadcasting, or
204 listening for rebroadcasts is performed. Any loot already recorded will be restored 204 listening for rebroadcasts is performed. Any loot already recorded will be restored
205 across login sessions no matter the status. 205 across login sessions no matter the status.
206 206
207 You can turn on tracking/broadcasting before joining a raid. If you join a raid 207 You can turn on tracking/broadcasting before joining a raid. If you join a raid
208 and the addon has not been turned on, then (by default) a popup dialog will ask for 208 and the addon has not been turned on, then a popup dialog will ask for
209 instructions. (This can be turned off in the advanced <Options>.) 209 instructions. (This can be turned off in the advanced <Options>.)
210 210
211 The addon tries to be smart about logging on during a raid (due to a disconnect or 211 The addon tries to be smart about logging on during a raid (due to a disconnect or
212 relog). If you log in, are already in a raid group, and loot has already been 212 relog). If you log in, are already in a raid group, and loot has already been
213 stored from tracking, it will re-enable itself automatically. 213 stored from tracking, it will re-enable itself automatically.
228 Full tracking records all loot events that fulfill these criteria: 228 Full tracking records all loot events that fulfill these criteria:
229 229
230 1) The loot quality is equal to or better than what you have selected in the 230 1) The loot quality is equal to or better than what you have selected in the
231 +Threshold> drop-down. 231 +Threshold> drop-down.
232 232
233 2) The loot is not one of the few items hardcoded to not be tracked (badges, 233 2) The loot is not in the list of items to filter out (see the <Options> tab).
234 emblems, Stone Keeper Shards, etc). 234 These are things like shards from disenchanting and Darkmoon Faire quest items.
235 235
236 3) <You can see the loot event.> More precisely, you need to be close enough 236 3) <You can see the loot event.> More precisely, you need to be close enough
237 to the recipient of the loot to be able to see "So-And-So receives loot: [Stuff]" 237 to the recipient of the loot to be able to see "So-And-So receives loot: [Stuff]"
238 in your chat window, even if you have those actual loot messages turned off. 238 in your chat window, even if you have those actual loot messages turned off.
239 239
252 252
253 The other option is to ask other players to also install Ouro Loot, and for 253 The other option is to ask other players to also install Ouro Loot, and for
254 them to turn on the "Rebroadcasting" feature. Any loot events which they can 254 them to turn on the "Rebroadcasting" feature. Any loot events which they can
255 see will be communicated to you. Then it only becomes necessary for at least 255 see will be communicated to you. Then it only becomes necessary for at least
256 one person to be close enough to the loot recipient to see the item awarded, 256 one person to be close enough to the loot recipient to see the item awarded,
257 and you will record it no matter how far away you are -- even back in Dalaran. 257 and you will record it no matter how far away you are -- even back in Orgrimmar.
258 258
259 If you have Full Tracking enabled, then you are also automatically rebroadcasting. 259 If you have Full Tracking enabled, then you are also automatically rebroadcasting.
260 Having more than one player with Full Tracking turned on is probably a good 260 Having more than one player with Full Tracking turned on is probably a good
261 idea, in case one of the trackers experiences a game crash or is suddenly kidnapped 261 idea, in case one of the trackers experiences a game crash or is suddenly kidnapped
262 by robot ninja monkeys. 262 by robot ninja monkeys.
271 You can use </loot bcast> or </loot broadcast> to turn on rebroadcasting without 271 You can use </loot bcast> or </loot broadcast> to turn on rebroadcasting without
272 opening the GUI. 272 opening the GUI.
273 ]] 273 ]]
274 274
275 T.texts = [[ 275 T.texts = [[
276 The middle tabs are just large editboxes. Their text is initially generated from 276 The middle tabs are simply large editable text boxes. Their text is initially
277 generated from
277 the information stored on the main <Loot> tab, at the time you click on the tab. 278 the information stored on the main <Loot> tab, at the time you click on the tab.
278 Not every bit of information that 279 Not every bit of information that
279 we want in the generated text is always available, or depends on things that the 280 we want in the generated text is always available, or depends on things that the
280 game itself can't know. So you can edit the text in the tabs and your edits will 281 game itself can't know. So you can edit the text in the tabs and your edits will
281 be preserved. 282 be preserved.
319 changed directly but would generate incorrect text, you can click this tab to 320 changed directly but would generate incorrect text, you can click this tab to
320 generate the text right away. Then edit/move the text as needed. When you 321 generate the text right away. Then edit/move the text as needed. When you
321 close the display or click back on the <Loot> tab, your edited text will be 322 close the display or click back on the <Loot> tab, your edited text will be
322 preserved for later. 323 preserved for later.
323 324
324 Pro tip #2: Barring things like pro tip #1, the author typically does not 325 Pro tip #2: Barring situations like pro tip #1, this addon author typically
325 generate any text until the end of the raid. 326 does not generate any text until the end of the raid, simplifying things
327 considerably.
326 ]] 328 ]]
327 329
328 T.texts_other = [[ 330 T.texts_other = [[
329 So far the only other generated text is the <Attendance> tab, an alphabetized list 331 So far the only other generated text is the <Attendance> tab, an alphabetized list
330 on a per-boss basis. 332 on a per-boss basis.
490 the full loot list. Restoring will get you a blank first tab and whatever you 492 the full loot list. Restoring will get you a blank first tab and whatever you
491 previously had in the various generated text tabs. 493 previously had in the various generated text tabs.
492 494
493 Using the right-click menu to change an item's treatment (shard, offspec, etc) 495 Using the right-click menu to change an item's treatment (shard, offspec, etc)
494 does not broadcast that change to anyone else who is also tracking. Changing 496 does not broadcast that change to anyone else who is also tracking. Changing
495 the item and then selecting "rebroadcast this item" *does* include that extra 497 the item and then selecting "rebroadcast this item" <does> include that extra
496 info. Doing that on the initial "mark as xxx" action is... tricky. 498 info. Automatically doing that on the initial "mark as xxx" action would
497 499 be... tricky.
498 The generated text tries to only list the name of the instance if it has not 500
499 already been listed, or if it is different than the instance of the previous 501 The generated forum text tries to only list the name of the instance if it has
502 not already been listed, or if it is different than the instance of the previous
500 boss. If you relog, the "last printed instance name" will be forgotten, and 503 boss. If you relog, the "last printed instance name" will be forgotten, and
501 you'll see redundant raid instance names appearing in the text. 504 you'll see redundant raid instance names appearing in the text.
502 505
503 After a boss wipe, multiple broadcasting players releasing spirit more than 506 After a boss wipe, multiple broadcasting players releasing spirit more than
504 several seconds apart can cause spurious "wipe" entries (of zero duration) on 507 several seconds apart can cause spurious "wipe" entries (of zero duration) on
531 addon.default_itemfilter = { 534 addon.default_itemfilter = {
532 [29434] = true, -- Badge of Justice 535 [29434] = true, -- Badge of Justice
533 [40752] = true, -- Emblem of Heroism 536 [40752] = true, -- Emblem of Heroism
534 [40753] = true, -- Emblem of Valor 537 [40753] = true, -- Emblem of Valor
535 [45624] = true, -- Emblem of Conquest 538 [45624] = true, -- Emblem of Conquest
536 -- could probably remove the above now 539 -- could probably remove most of this now
537 [43228] = true, -- Stone Keeper's Shard 540 [43228] = true, -- Stone Keeper's Shard
538 [47241] = true, -- Emblem of Triumph 541 [47241] = true, -- Emblem of Triumph
539 [49426] = true, -- Emblem of Frost 542 [49426] = true, -- Emblem of Frost
540 } 543 }
541 544