farmbuyer@1: farmbuyer@1: local todo = [[ farmbuyer@1: - broadcasted entries triggering auto-shard don't have "shard" text farmbuyer@1: farmbuyer@1: - [DONE,TEST,comm] releasing before DBM signals wipe results in outdoor location farmbuyer@1: farmbuyer@1: - implement ack, then fallback to recording if not ack'd farmbuyer@1: farmbuyer@1: - special treatment for recipes / BoE items? default to guild vault? farmbuyer@1: farmbuyer@1: - rebroadcasting entire boss sections, entire days. maybe only whisper farmbuyer@1: to specific people rather than broadcast. farmbuyer@1: farmbuyer@16: - [DONE] signpost a potential boss kill, pipeline loot until the cache clears farmbuyer@1: farmbuyer@1: - Being able to drag rows up and down the main loot grid would be awesome. Coding farmbuyer@1: that would be likely to drive me batshiat insane. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: local addon = select(2,...) farmbuyer@1: farmbuyer@1: addon.helptree = { farmbuyer@1: { farmbuyer@1: value = "about", farmbuyer@1: text = "About", farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "basic", farmbuyer@1: text = "Basics", farmbuyer@1: children = { farmbuyer@1: { farmbuyer@1: value = "loot", farmbuyer@1: text = "Loot Entries", farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "boss", farmbuyer@1: text = "Boss Entries", farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "tracking", farmbuyer@1: text = "Tracking Loot", farmbuyer@1: children = { farmbuyer@1: { farmbuyer@1: value = "enabled", farmbuyer@1: text = "Full Tracking", farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "bcast", farmbuyer@1: text = "Rebroadcasting", farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "texts", farmbuyer@1: text = "Generated Texts", farmbuyer@1: children = { farmbuyer@1: { farmbuyer@1: value = "forum", farmbuyer@1: text = "Forum Markup", farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "other", farmbuyer@1: text = "Other Texts", farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "saved", farmbuyer@1: text = "Saved Texts", farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: { farmbuyer@7: value = "history", farmbuyer@7: text = "History Tab", farmbuyer@7: }, farmbuyer@7: { farmbuyer@1: value = "tips", farmbuyer@1: text = "Handy Tips", farmbuyer@1: children = { farmbuyer@1: { farmbuyer@1: value = "slashies", farmbuyer@1: text = "Slash Commands", farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "todo", farmbuyer@1: text = "TODOs, Bugs, etc", farmbuyer@1: children = { farmbuyer@1: { farmbuyer@1: value = "gotchas", farmbuyer@1: text = "Gotchas", farmbuyer@1: }, farmbuyer@1: { farmbuyer@1: value = "todolist", farmbuyer@1: text = "TODO/knownbugs", farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: }, farmbuyer@1: } farmbuyer@1: farmbuyer@1: -- Help text. Formatting doesn't matter, but use a blank line to split farmbuyer@1: -- paragraphs. This file needs to be edited with a text editor that doesn't farmbuyer@1: -- do anything stupid by placing extra spaces at the end of lines. farmbuyer@1: do farmbuyer@1: local replacement_colors = { ["+"]="|cff30adff", ["<"]="|cff00ff00", [">"]="|r" } farmbuyer@1: local T={} farmbuyer@1: T.about = [[ farmbuyer@1: Ouro Loot is the fault of Farmbuyer of Ouroboros on US-Kilrogg. Bug reports, farmbuyer@1: comments, and suggestions are welcome at the project page at curse.com or send farmbuyer@1: them to . farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.basic = [[ farmbuyer@1: The (and by default) command opens this display. The buttons farmbuyer@1: on the right side control operation and are mostly self-explanatory. Hovering over farmbuyer@1: things will usually display some additional text in the gray line at the bottom. farmbuyer@1: farmbuyer@1: Each tab on the left side can additionally create extra contols in the lower-right farmbuyer@1: section of the display. farmbuyer@1: farmbuyer@1: The first tab on the left side, , is where everything goes to and comes farmbuyer@1: from. Looting events and Deadly Boss Mods notifications go to the tab; the farmbuyer@1: other tabs are all generated from the information in the tab. farmbuyer@16: farmbuyer@16: |cffff335dNote about these Help pages:|r The category "titles" on the left side farmbuyer@16: have their own help text, in addition to the more specific entries in the expanded farmbuyer@16: list. Read those first before expanding the categories or you'll miss stuff. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.basic_loot = [[ farmbuyer@1: A "loot row" in the first tab has three columns: the item, the recipient, and any farmbuyer@1: extra notes. The recipient's class icon is displayed by their names, if class farmbuyer@1: information is available at the time. farmbuyer@1: farmbuyer@1: farmbuyer@1: farmbuyer@1: Hovering the mouse over the first column will display the item in a tooltip. farmbuyer@1: farmbuyer@1: Hovering over the second column will display a tooltip with the loot that person farmbuyer@1: has received. If they've won more than 10 items, the list is cut off with '...' farmbuyer@1: at the end; to see the full list, use the right-click +Show only this player> option farmbuyer@1: instead. farmbuyer@1: farmbuyer@1: farmbuyer@1: farmbuyer@1: Right-clicking a loot row shows a dropdown menu. farmbuyer@1: farmbuyer@1: Right-clicking in the first or third columns will display options for special farmbuyer@1: treatment of that loot entry (marking as offspec, etcetera). Using any of those farmbuyer@1: options will change the text in the third column (which will then affect the text farmbuyer@1: in the generated tabs, such as forum markup). farmbuyer@1: farmbuyer@1: Right-clicking in the second column allows you to temporarily remove all other farmbuyer@1: players from the loot display. Use the reset button in the lower-right corner to farmbuyer@1: restore the display to normal. The menu also allows you to +reassign> loot from farmbuyer@1: one player to another; if the new recipient is not in the raid group at the time, farmbuyer@1: use the +Enter name...> option at the bottom of the list of names to type the farmbuyer@1: name into a text box. If your raid takes advantage of the new ability to trade farmbuyer@1: soulbound items, you will need to reassign the item here for the generated text farmbuyer@1: to be factually correct. farmbuyer@1: farmbuyer@1: See the help screen on "Boss Entries" for the +Insert new boss kill event> option. farmbuyer@1: farmbuyer@1: farmbuyer@1: farmbuyer@1: Double-clicking a loot row in the third ("Notes") column allows you to edit that farmbuyer@1: field directly. The color of the text will still depend on any +Mark as ___> farmbuyer@1: actions done to that loot row, whether automatically or by hand. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.basic_boss = [[ farmbuyer@1: Boss wipe/kill entries are entirely dependant on Deadly Boss Mods being enabled and farmbuyer@1: up-to-date. The typical sequence of events for our usual raids goes like this: farmbuyer@1: farmbuyer@1: We make four or five attempts on Baron Steamroller. As DBM registers that combat farmbuyer@1: ends, a event is entered on the loot display along with the duration of the farmbuyer@1: fight. If the loot display is opened, the wipes will be visible with a light gray farmbuyer@1: background. farmbuyer@1: farmbuyer@1: After reminding the dps classes to watch the threat meters, we manage to kill farmbuyer@1: Steamroller. When DBM registers the win, a event is entered on the display farmbuyer@1: with a dark gray background. farmbuyer@1: All previous s are removed and collapsed into the event. The final farmbuyer@1: event shows the duration of the successful fight and the number of attempts farmbuyer@1: needed (or "one-shot" if we manage to be competent). farmbuyer@1: farmbuyer@1: Sometimes this goes wrong, when DBM misses its own triggers. If DBM does not catch farmbuyer@1: the start of the boss fight, it can't register the end, so nothing at all is farmbuyer@1: recorded. If the fight was a win but DBM does not catch the victory conditions, farmbuyer@1: then DBM will (after several seconds) decide that it was a wipe instead. And farmbuyer@1: sometimes useful loot will drop from trash mobs, which DBM knows nothing about. farmbuyer@1: farmbuyer@1: For all those reasons, right-clicking on a "boss row" will display options for farmbuyer@1: +Insert new boss kill event>, and for toggling a into a . We often farmbuyer@1: insert bosses named "trash" to break up the display and correct the forum markup farmbuyer@1: listing. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.tracking = [[ farmbuyer@1: The first button underneath +Main> in the right-hand column displays the current farmbuyer@1: status of the addon. If it is disabled, then no recording, rebroadcasting, or farmbuyer@1: listening for rebroadcasts is performed. Any loot already recorded will be restored farmbuyer@1: across login sessions no matter the status. farmbuyer@1: farmbuyer@1: You can turn on tracking/broadcasting before joining a raid. If you join a raid farmbuyer@1: and the addon has not been turned on, then (by default) a popup dialog will ask for farmbuyer@1: instructions. (This can be turned off in the advanced .) farmbuyer@1: farmbuyer@1: The addon tries to be smart about logging on during a raid (due to a disconnect or farmbuyer@1: relog). If you log in, are already in a raid group, and loot has already been farmbuyer@16: stored from tracking, it will re-enable itself automatically. farmbuyer@1: farmbuyer@1: The intent of the addon design is that, after the end of a raid, all the generated farmbuyer@1: markup text is done, optionally saved (see "Generated Texts - Saved Texts"), and farmbuyer@1: then cleared from farmbuyer@1: storage altogether. As a result, if you login with restored loot information but farmbuyer@1: are not in a raid, the addon will do nothing on its own -- but will assume that farmbuyer@1: you've forgotten to finish those steps and will yammer about it in the chat window farmbuyer@1: as a reminder. farmbuyer@1: farmbuyer@1: The +Threshold> drop-down has no connection at all with any current loot threshold farmbuyer@1: set by you or a master looter. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.tracking_enabled = [[ farmbuyer@1: Full tracking records all loot events that fulfill these criteria: farmbuyer@1: farmbuyer@1: 1) The loot quality is equal to or better than what you have selected in the farmbuyer@1: +Threshold> drop-down. farmbuyer@1: farmbuyer@1: 2) The loot is not one of the few items hardcoded to not be tracked (badges, farmbuyer@1: emblems, Stone Keeper Shards, etc). farmbuyer@1: farmbuyer@1: 3) More precisely, you need to be close enough farmbuyer@1: to the recipient of the loot to be able to see "So-And-So receives loot: [Stuff]" farmbuyer@1: in your chat window, even if you have those actual loot messages turned off. farmbuyer@1: farmbuyer@1: It is (3) that causes complications. A master looter can assign loot to anybody farmbuyer@1: anywhere in a raid instance, but the range on detecting loot events is much farmbuyer@1: smaller. If your raid does not use master looting then you merely need to be farmbuyer@1: close enough to the boss corpse, presuming that the winners will need to walk farmbuyer@1: over to get their phat epix. farmbuyer@1: farmbuyer@1: If you do use master looter, then you have two options: first, you can farmbuyer@1: require players farmbuyer@1: who might get loot to stay near the boss. You would then also need to stay near farmbuyer@1: the boss to detect the loot event. (This can be less hassle if you are also farmbuyer@1: the loot master.) The downside is that other players moving on to fight to the farmbuyer@1: next boss are doing so without the help of their teammates. farmbuyer@1: farmbuyer@1: The other option is to ask other players to also install Ouro Loot, and for farmbuyer@1: them to turn on the "Rebroadcasting" feature. Any loot events which they can farmbuyer@1: see will be communicated to you. Then it only becomes necessary for at least farmbuyer@1: one person to be close enough to the loot recipient to see the item awarded, farmbuyer@1: and you will record it no matter how far away you are -- even back in Dalaran. farmbuyer@1: farmbuyer@1: If you have Full Tracking enabled, then you are also automatically rebroadcasting. farmbuyer@1: Having more than one player with Full Tracking turned on is probably a good farmbuyer@1: idea, in case one of the trackers experiences a game crash or is suddenly kidnapped farmbuyer@1: by robot ninja monkeys. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.tracking_bcast = [[ farmbuyer@1: The simplest method of operation is only rebroadcasting the loot events that you farmbuyer@1: see, as you see them. Nothing is recorded in your local copy of the addon. farmbuyer@1: farmbuyer@1: If you logout for any reason, the addon will not reactivate when you log back in. farmbuyer@1: farmbuyer@1: You can use or to turn on rebroadcasting without farmbuyer@1: opening the GUI. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.texts = [[ farmbuyer@1: The middle tabs are just large editboxes. Their text is initially generated from farmbuyer@1: the information stored on the main tab, at the time you click on the tab. farmbuyer@1: Not every bit of information that farmbuyer@1: we want in the generated text is always available, or depends on things that the farmbuyer@1: game itself can't know. So you can edit the text in the tabs and your edits will farmbuyer@1: be preserved. farmbuyer@1: farmbuyer@1: Each time you click one of the text tabs, every new entry on the tab farmbuyer@1: since the last time this tab was shown will be turned into text. farmbuyer@1: farmbuyer@1: Clicking the +Regenerate> button will throw away all the text on that tab, including farmbuyer@1: any edits you've made, and recreate all of it from scratch. If you've accidentally farmbuyer@1: deleted the text from the editbox, or you've made manual changes to the tab, farmbuyer@1: you can use this button to start over. farmbuyer@1: farmbuyer@1: You can click in an editbox and use Control-A to select all text, then Control-C farmbuyer@1: to copy it to the system clipboard for subsequent pasting into a web browser or farmbuyer@1: whatever. If you're on a Mac, you probably already know the equivalent keys. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.texts_forum = [[ farmbuyer@1: The tab creates text as used by the guild forums for Ouroboros farmbuyer@1: of Kilrogg. By default this is fairly standard BBcode. The format of the farmbuyer@1: individual loot items can be adjusted via the dropdown menu on the lower right farmbuyer@1: of the tab. farmbuyer@1: farmbuyer@1: The [url] choice defaults to using Wowhead. If you have the [item] extension farmbuyer@1: for your BBcode installed, you can use either of those choices too. The "by ID" farmbuyer@16: variant is good for heroic raid items that share names with nonheroic items, farmbuyer@16: but the raw output is harder to read in the text tab. farmbuyer@1: farmbuyer@1: You can also specify a custom string. Formatting is done with these replacements: farmbuyer@1: farmbuyer@1: +$N>: item name|r farmbuyer@1: farmbuyer@1: +$I>: (capital "eye", not "ell") numeric item ID|r farmbuyer@1: farmbuyer@1: +$T>: loot recipient and any additional notes|r farmbuyer@1: farmbuyer@1: +$X>: if more than one of the item was looted, this is the "x2", "x3", etc farmbuyer@1: farmbuyer@1: farmbuyer@1: Pro tip #1: if something has happened on the main tab which cannot be farmbuyer@1: changed directly but would generate incorrect text, you can click this tab to farmbuyer@1: generate the text right away. Then edit/move the text as needed. When you farmbuyer@1: close the display or click back on the tab, your edited text will be farmbuyer@1: preserved for later. farmbuyer@1: farmbuyer@1: Pro tip #2: Barring things like pro tip #1, the author typically does not farmbuyer@1: generate any text until the end of the raid. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.texts_other = [[ farmbuyer@1: So far the only other generated text is the tab, an alphabetized list farmbuyer@1: on a per-boss basis. farmbuyer@1: farmbuyer@1: Other addons can register their own text tabs and corresponding generation farmbuyer@1: functions. If you want to be able to feed text into an offline program (for farmbuyer@1: example, a spreadsheet or DKP tracker), then this may be of use to you. farmbuyer@1: farmbuyer@1: Ideas for more tabs? Tell me! farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.texts_saved = [[ farmbuyer@16: The contents of the , , and other such tabs can be saved, farmbuyer@16: so that they will not be lost when you use the +Clear> button. farmbuyer@1: farmbuyer@1: Do any edits you want to the generated text tabs, then click the +Save Current As...> farmbuyer@1: button on the right-hand side. Enter a short descriptive reminder (for example, farmbuyer@1: "thursday hardmodes") in the popup dialog. The texts will remain in their tabs, farmbuyer@1: but clearing loot information will not lose them now. farmbuyer@1: farmbuyer@16: All saved texts are listed on the right-hand side. Clicking a saved text name farmbuyer@16: lets you +Load> or +Delete> that saved set. The primary tab is not saved farmbuyer@16: and restored by this process, only the generated texts. This also means you cannot farmbuyer@16: +Regenerate> the texts. farmbuyer@1: ]] farmbuyer@1: farmbuyer@7: T.history = [[ farmbuyer@7: The tab maintains a list of all loot. It is intended to help answer farmbuyer@7: questions such as "When was the last time PlayerX won something?" and "How much stuff farmbuyer@7: has PlayerY gotten lately?" The history tab is, by design, not as configurable farmbuyer@25: as the main tab; entries cannot be manually edited and so forth. farmbuyer@7: farmbuyer@25: This loot history is the only "live" data tab which persists across the +Clear Loot> command. farmbuyer@7: For this reason, very little information is stored: only the recipient, the item, farmbuyer@8: and a textual timestamp. Boss names, offspecs, and other notes are not preserved. farmbuyer@7: farmbuyer@7: The default history window shows the most recent item received by each person. It farmbuyer@7: is sorted with the most recent loot at the top, towards older loot at the bottom. farmbuyer@7: You can click the column headers to rearrange the rows, but doing so repeatedly can farmbuyer@7: lead to odd display issues. farmbuyer@7: farmbuyer@7: Left-clicking a row will change the window to display all recorded loot for that farmbuyer@25: player. While on that display, right-clicking any row will return to showing the farmbuyer@25: most recent single item for all players. farmbuyer@7: farmbuyer@7: Histories are maintained per-realm. This refers to the realm you are on when the farmbuyer@7: loot drops, not the realm of the player receiving it (in the case of cross-realm farmbuyer@7: groups). If you play multiple characters on the same realm, history will accumulate farmbuyer@7: across all your raids. To change the displayed realm, use the dropdown menu in farmbuyer@7: the lower right corner. farmbuyer@7: farmbuyer@7: The +Regenerate> button permanently erases the history of the displayed realm, and farmbuyer@7: creates fresh entries using whatever loot information is currently on the tab. farmbuyer@7: Be aware that the tab does not track realms, so if you have gathered data farmbuyer@7: for players on realm A, but are displaying realm B when you click the Regenerate button, farmbuyer@7: then your history for realm B will be... very odd. farmbuyer@7: farmbuyer@7: +Clear Realm History> and +Clear ALL History> are used to periodically wipe the farmbuyer@7: slate clean. They do not generate any new entries from existing loot. farmbuyer@7: farmbuyer@7: +Clear Older> deletes history information for all items not shown in the "most recent farmbuyer@7: loot" display. It is another good periodic maintenance step, but does not discard farmbuyer@7: as much data as the other actions. farmbuyer@7: farmbuyer@25: Using +Reassign to...> will also move the item between player histories. The timestamp farmbuyer@25: will not be changed; it will "always have been" received by the new recipient. farmbuyer@25: farmbuyer@25: Using +Mark as disenchanted> or +Mark as guild vault> will remove the item from farmbuyer@25: history altogether. Remarking such an item as +normal> or +offspec> will replace farmbuyer@25: the item back into the player's history. farmbuyer@25: farmbuyer@7: Note: the first time you display the histories during a game session, you will farmbuyer@7: likely see several items listed as +UNKNOWN>. This is not a bug; these items are farmbuyer@7: simply not in your local game cache. WoW will automatically retrieve the missing farmbuyer@7: data after several seconds, but the display will not update until the next time farmbuyer@7: the History tab is shown. Starting in WoW 4.0, the local game cache is not preserved farmbuyer@7: across play sessions, so the +UNKNOWN> entries will pop up from time to time. farmbuyer@7: ]] farmbuyer@7: farmbuyer@1: T.tips = [[ farmbuyer@16: Shift-clicking an item in the or display will paste it into an farmbuyer@16: open chat editbox. farmbuyer@1: farmbuyer@16: The |cffff8000[Ouro Loot]|r "legendary item" displayed at the start of all farmbuyer@1: chat messages is a clickable link. Clicking opens the main display. An option farmbuyer@1: on the tab will cause a message to be printed after a boss kill, farmbuyer@1: mostly for lazy loot trackers who don't like typing slash commands to open windows. farmbuyer@1: farmbuyer@1: If you are broadcasting to somebody else who is tracking, you should probably be farmbuyer@1: using the same threshold. If yours is lower, then some of the loot you broadcast farmbuyer@1: to him will be ignored. If yours is higher, then you will not be sending information farmbuyer@1: that he would have recorded. The "correct" setting depends on what your guild wants farmbuyer@1: to track. farmbuyer@1: farmbuyer@1: Ticking the "notraid" box in advanced debugging , before enabling tracking, farmbuyer@1: will make the tracking work outside of a raid group. Communication functions farmbuyer@1: will behave a little strangely when doing this. Be sure to check the threshold! farmbuyer@1: You can also use <"/ouroloot debug notraid"> instead. farmbuyer@1: farmbuyer@1: Using the "Saved Texts" feature plus the +Clear> button is a great way of putting farmbuyer@1: off pasting loot into your guild's website until a more convenient time. farmbuyer@20: farmbuyer@20: All of the choices in the right-click dropdown menus have tooltips with some farmbuyer@20: additional information, but these only appear when the Blizzard option "Beginner farmbuyer@20: Tooltips" is enabled (Interface - Game - Help - Beginner Tooltips). farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.tips_slashies = [[ farmbuyer@16: If you give an unrecognized argument to the slash command, it will farmbuyer@16: search the tab titles left to right for a title beginning with the same letters as farmbuyer@16: the argument, and open the display to that tab. For example, <"/loot a"> would farmbuyer@16: open the tab, and <"/loot ad"> would open the tab. If farmbuyer@16: you had added a theoretical tab, then <"/loot eq"> would be the fastest farmbuyer@16: way to see it. farmbuyer@16: farmbuyer@1: The command can take arguments to do things without going through farmbuyer@1: the UI. Parts given in *(angle brackets)* are required, parts in [square brackets] farmbuyer@1: are optional: farmbuyer@1: farmbuyer@1: +broadcast>/+bcast>: turns on rebroadcasting|r farmbuyer@1: farmbuyer@1: +on [T]>: turns on full tracking, optionally setting threshold to T|r farmbuyer@1: farmbuyer@1: +off>: turns off everything|r farmbuyer@1: farmbuyer@1: +thre[shold] T>: sets tracking threshold to T|r farmbuyer@1: farmbuyer@1: +list>: prints saved text names and numbers|r farmbuyer@1: farmbuyer@1: +save *(your set name)*>: saves texts as "your set name"|r farmbuyer@1: farmbuyer@1: +restore *(N)*>: restores set number N|r farmbuyer@1: farmbuyer@1: +delete *(N)*>: deletes set number N|r farmbuyer@1: farmbuyer@1: +help>: opens the UI to the help tab|r farmbuyer@1: farmbuyer@1: +toggle>: opens or closes the UI (used mostly in automated wrappers)|r farmbuyer@1: farmbuyer@1: farmbuyer@1: If you use the slash commands to enable tracking or set loot thresholds, you can farmbuyer@1: give numbers or common names for the threshold. For example, "0", "poor", "trash", farmbuyer@1: "gray"/"grey" are all the same, "4", "epic", "purple" are the same, and so on. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.todo = [[ farmbuyer@1: If you have ideas or complaints or bug reports, first check the Bugs subcategories farmbuyer@1: to see if they're already being worked on. Bug reports are especially helpful farmbuyer@1: if you can include a screenshot (in whatever image format you find convenient). farmbuyer@1: farmbuyer@1: Click the "About" line on the left for contact information. farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.todo_gotchas = [[ farmbuyer@1: (and things I'm not sure I like in the farmbuyer@1: current design): farmbuyer@1: farmbuyer@1: If you relog (or get disconnected) while in a raid group, behavior when you log farmbuyer@1: back in can be surprising. If you have already recorded loot (and therefore farmbuyer@1: the loot list is restored), then OL assumes it's from the current raid and should farmbuyer@1: reactivate automatically in full tracking mode. If you were tracking but no farmbuyer@1: loot had dropped yet (and therefore there was nothing *to* restore), then OL farmbuyer@1: will pop up its reminder and ask again. Either way, if you were only broadcasting farmbuyer@1: then OL will *not* go back to only broadcasting. This is probably a bug. farmbuyer@1: farmbuyer@1: The saved texts feature does exactly that: only saves the generated texts, not farmbuyer@1: the full loot list. Restoring will get you a blank first tab and whatever you farmbuyer@1: previously had in the various generated text tabs. farmbuyer@1: farmbuyer@1: Using the right-click menu to change an item's treatment (shard, offspec, etc) farmbuyer@1: does not broadcast that change to anyone else who is also tracking. Changing farmbuyer@1: the item and then selecting "rebroadcast this item" *does* include that extra farmbuyer@1: info. Doing that on the initial "mark as xxx" action is... tricky. farmbuyer@1: farmbuyer@1: The generated text tries to only list the name of the instance if it has not farmbuyer@1: already been listed, or if it is different than the instance of the previous farmbuyer@1: boss. If you relog, the "last printed instance name" will be forgotten, and farmbuyer@1: you'll see redundant raid instance names appearing in the text. farmbuyer@1: farmbuyer@1: After a boss wipe, multiple broadcasting players releasing spirit more than farmbuyer@1: several seconds apart can cause spurious "wipe" entries (of zero duration) on farmbuyer@1: the loot grid. The surefire way to avoid this is to not release spirit until farmbuyer@1: DBM announces the wipe, but the problem isn't serious enough to really worry farmbuyer@1: about. (Right-click the spurious entries and delete them.) farmbuyer@1: ]] farmbuyer@1: farmbuyer@1: T.todo_todolist = todo farmbuyer@1: farmbuyer@1: farmbuyer@1: -- Fill out the table that will actually be used. Join adjacent lines here so farmbuyer@1: -- that they'll wrap properly. farmbuyer@1: addon.helptext = {} farmbuyer@1: for k,text in pairs(T) do farmbuyer@1: local funkykey = k:gsub('_','\001') -- this is how TreeGroup makes unique keys farmbuyer@1: local wrapped = text farmbuyer@1: wrapped = wrapped:gsub ("[%+<>]", replacement_colors) farmbuyer@1: wrapped = wrapped:gsub ("([^\n])\n([^\n])", "%1 %2") farmbuyer@1: wrapped = wrapped:gsub ("|r\n\n", "|r\n") farmbuyer@1: wrapped = wrapped:gsub ("Ouroboros", "|cffa335ee|r") farmbuyer@1: wrapped = wrapped:gsub ("%*%(", "<") :gsub("%)%*", ">") farmbuyer@1: addon.helptext[funkykey] = wrapped farmbuyer@1: end farmbuyer@1: end -- do scope farmbuyer@1: todo = nil farmbuyer@1: farmbuyer@1: farmbuyer@1: -- Don't bother recording any of this loot: farmbuyer@1: addon.default_itemfilter = { farmbuyer@1: [29434] = true, -- Badge of Justice farmbuyer@1: [40752] = true, -- Emblem of Heroism farmbuyer@1: [40753] = true, -- Emblem of Valor farmbuyer@1: [45624] = true, -- Emblem of Conquest farmbuyer@1: -- could probably remove the above now farmbuyer@1: [43228] = true, -- Stone Keeper's Shard farmbuyer@1: [47241] = true, -- Emblem of Triumph farmbuyer@1: [49426] = true, -- Emblem of Frost farmbuyer@1: } farmbuyer@1: farmbuyer@1: -- vim:noet