Item previews for items that utilize an On Use bonus, as well as charges and cooldowns, will be displayed a bit differently now.

- The charges have been changed to show in white and on the line below the "On Use" spell text. This is so that the preview matches more closely what sites like Wowhead show.

- The cooldown is now formatted into hours, minutes, and seconds and will display in parenthesis on the same line (and directly after) the "On Use" spell text. This is again to mimic what Wowhead uses. This is also the first time the cooldown has been shown on the preview here at WoW-V. If an item has no cooldown, it will not show the text.

- The global cooldown is formatted similarly to the regular cooldown, but is displayed at the bottom of the preview (above the buy/sell info and below the ilevel) in gray text if one has been set.

All item previews have been refreshed to reflect this change.

Enjoy, and let us know if there are any issues.

Thanks to one dedicated MaNGOS user (truekush) we are able to finally add MaNGOS (the latest database structure) quest support!

Like other cores, the MaNGOS batch does not utilize all the creator functionality (moreso than the other cores):

- No "Repeatable?" field
- No "Reward: Honor" field
- No "Reward: Talents" field
- No "Reward: Faction Rep #6" field
- No "Reward: Rep Limit" field
- No "Req. Completed Quests #2-4" fields (the #1 field does work, however)
- No "Allowable Class" field
- No "Money at Max Level" field (we utilize the field, but it appears to only award XP)
- "Sort" options don't work (only ZoneIDs do)

Now, we realize through truekush's generous testing that the MaNGOS-unique field called `ZoneOrSort` may somewhat support ZoneIDs, Sort, _and_ Required Class values all in one. HOWEVER, because of the overlapping values the three have, it is not possible for us to properly support anything but the ZoneID.

You can obviously edit the query manually if you know how to get them to work, but we will NOT be supporting Sort values or Required Class values for the MaNGOS batch because of this issue, since it would cause major confusion for our ArcEmu, Aspire, and Ascent users.

Thank you truekush for your testing, data, and question answering. This wouldn't have been possible without you!

Because badges were not playing out how we liked, we've implemented some major changes:

Point rewards were based directly on rank before. They have stayed that way in a broad sense, but the point value is being reduced per rank:

Rank 1 = 0 points per badge vote
Rank 2 = 0 points per badge vote
Rank 3 = 1 points per badge vote
Rank 4 = 2 points per badge vote
Rank 5 = 3 points per badge vote
Rank 6 = 4 points per badge vote
Rank 7 = 5 points per badge vote

We have also changed it so that you can only vote once per hour, per badge type. What this means is that while you can still only vote on one badge type per item, you can give one item a Blizz badge, another a Fun badge, another a Humor badge, and another a Unique badge.

The bottom line: users get 4 votes per hour, 1 badge vote per item, 1 vote per badge type.

The "cooldown" left on your badge voting shows on items you have not yet voted a badge on (below the applicable badge).