WowAce

What

Ouro Loot tracks loot during a raid and then produces output formatted for pasting on a guild forum or similar place. Loot is optionally categorized by boss if you have Deadly Boss Mods installed. Loot can be annotated with notes (getting disenchanted, awarded for offspec, going to a guild vault, etcetera) and the forum output will be marked up appropriately. A longer-term history of loot is kept also.

This addon does not replace or augment the Master Looter interface or behavior. In fact, it specifically has nothing to do with the actual awarding of loot, only the tracking of it. So if your raids already have an addon to help with that (loot council, GDKP, whatever), you can continue using it without interference.

Some stats on the raid roster are kept for attendance tracking, although this is not the main goal. That info is primarily intended for other modules to use for data export.

If you have downloaded this addon from anywhere other than directly from Curse or WoWInterface, then it is outdated at best and infected with viruses at worst. Clone sites not only leech bandwidth from real sites, lately they've been adding malware as well. Get your addons from safe sites with a good reputation!

How

Instructions and documentation are built in. Just use the /ouroloot command, or click the help link that comes up when you login the first time after installing it. There is deliberately no minimap icon or similar "always visible" component to soak up valuable screen space or CPU cycles.

Best coverage of loot tracking is obtained if multiple people in your raid are running the addon, with at least one person tracking and the others broadcasting. This allows loot to be noticed even when the looting is happening out of detection range of the person doing the tracking. This is explained further in the help screens.

If you have Addon Loader installed, this addon will delay loading until you use any of its configuration methods or join a raid group.

It is relatively simple to add more output formats. Each one appears as one or more additional tabs. They are implemented as load-on-demand plugin modules and are dropped in as standalone addons.

How (Else)

Plugins can do other things besides generate output text. Ouro Loot implements the standard CallbackHandler approach of firing off your addon's functions in response to events related to tracking loot, like "player received loot", "loot was reassigned between players", and so forth. Coming from the other side, your code can control things that would normally require human interaction in the Ouro Loot UI, like marking loot as offspec. You can even register your own options and actions inside the main addon, such as additional choices for the "Mark as offspec / guild vault / disenchanted" list. This means if you want to do additional work for your guild's loot tracking, you can let this addon handle all the network-related issues, and just do your tasks as event callbacks are fired off, saving a ton of development work!

See Plugins for more information. (The plugins link might only work if you view this page at the Project Site link above; it's curse.com brokenness, sorry.)

Feedback and bug reports are welcome; see the help screens for how. A list of known bugs, occasional gotchas, and future ideas is also built in.

When

Notable changes in 2.21

• Stuff for WoD and some brief pokes at the new loot and raiding systems. Upgrade! 2.21.0 is the latest release.

Notable changes in 2.20

• MoP, MoP, MoP.
• Saved options have transitioned to Ace profiles. (Only your options are stored in profiles, actual loot data is not.) Settings from 2.19 and earlier are just tossed out, since the default options have gotten smarter with this release. In particular, the way the item filter lists are managed, and their initial contents.
• Plugin settings are saved in your profile, as namespace variables.
• The options tab got a facelift, allowing for other addons (including plugins) to register their own entries.
• The extra "/loot" command is gone, as it's now a builtin command in MoP. There's a control on the options tab for other slash commands.
• Clicking on chat links to open the main display will now try and scroll/page/highlight the corresponding entry that caused the chat message to be printed in the first place, e.g., clicking the prefix in "[Ouro Loot] SomeOfficer has changed RaiderX's [New Shiny Toy] to offspec." will open the display as usual, but also find the New Shiny Toy from two hours earlier.
• Only of interest to programmers: an initial set of history and loot management events has been added. Code can register callbacks to be notified on simple things like receiving loot, and synchronized things like reassigning loot. These callbacks happen after all notifications from other trackers and broadcasters have all been sifted.

Notable changes in 2.19

• Raiders running older versions will not see all the data rebroadcast from players running 2.19 and later.
• Raiders running 2.19 will see data broadcast from older versions, however.
• Items can be marked as automatically assigned to the guild bank, exactly like the current list of items automatically marked as disenchanted. The default list is crafting materials dropping from Cataclysm raid bosses.
• Player names are colored by class when their data is available; the CUSTOM_CLASS_COLORS array is supported.
• The first combat after a boss kill clears the internal "most recent boss name" record, so that subsequent loot from yard trash will be marked as such. (This can mean a spurious "trash" entry if your raidmates go off and kill things while loot is still being handed out. Right-click and delete it.)
• Loot events have associated unique IDs, enabling some new actions over the network. These IDs are preserved as part of realm history. As a result, the stored history format has completely changed (and requires less memory as a bonus).
• "Mark as <x>" and "Reassign to..." are now broadcast to other Ouro Loot trackers. Older versions can't receive the message, of course. New options added controlling whether to print a message (and to which chat window) when another player broadcasts those kinds of changes, as they err on the side of wordiness.
• The History tab now has dropdown menus that let you remove individual entries instead of using the entire-realm action buttons in the lower right corner. Dropdowns are accessed with shift-right-clicking; if you forget, the new "Show UI Tips" option will remind you.
• The slash command handler has always had a feature which searches for the text of tab names if you give it an unrecognized command (e.g., "/ouroloot options" to open directly to the Options tab). Added in this release is the ability for each tab to handle additional arguments and perform appropriate actions. Currently only the History tab takes advantage of this: "/loot history blah" will search for a player's name beginning with "blah", and if found, will act as if you had clicked on that row, switching the display to every loot received by that player. All such slash command text is case-insensitive. Only enough text to be unambiguous is required, so "/loot o" will still display the Options tab in the default configuration, "/loot hi farm" is enough to trigger Farmbuyer's history display (as long as nobody named Farmville joins the raid), and so forth.
• Initial API changes for MoP; this version should run on either the live or beta realms.
• Lots of minor bugfixes.

Notable changes in 2.18

• A new option, "Show rebroadcasting player", has been added. This controls whether the "(from So-and-so)" is shown in the Notes column.
• Text output for the Attendance tab has changed to indicate which players are in the raid and which are in standby/outside groups. This assumes that your entire 10-player raid is in groups 1 & 2, your entire 15-player raid is in groups 1, 2, and 3, and so forth.
• Many other things only affecting plugins.

Notable changes in 2.17

• Support for Addon Loader
• Support for LoD plugin modules.

Older releases

• Just assume it was several years of bugfixing and get the latest version.