Mercurial > wow > ouroloot

comparison verbage.lua @ 69:8442272a8418

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
- Make sure popup dialogs are on top of Ace3's widgets. - Minor code reorganization. Safety hook for future boss-entry code. - Avoid same bug from a couple revs ago when adding manual boss kills. - Ask players about snapshot data when manually entering boss kills. - Blizzard rearranged the button order in 3-entry popups some time ago and I failed to adapt the code until now.
author Farmbuyer of US-Kilrogg <farmbuyer@gmail.com>
date Fri, 11 May 2012 03:08:12 +0000
parents c01875b275ca
children cdee65c1bd8c
comparison
equal deleted inserted replaced
68:3bed6d51e077 69:8442272a8418
510 After a boss wipe, multiple broadcasting players releasing spirit more than 510 After a boss wipe, multiple broadcasting players releasing spirit more than
511 several seconds apart can cause spurious "wipe" entries (of zero duration) on 511 several seconds apart can cause spurious "wipe" entries (of zero duration) on
512 the loot grid. The surefire way to avoid this is to not release spirit until 512 the loot grid. The surefire way to avoid this is to not release spirit until
513 DBM announces the wipe, but the problem isn't serious enough to really worry 513 DBM announces the wipe, but the problem isn't serious enough to really worry
514 about. (Right-click the spurious entries and delete them.) 514 about. (Right-click the spurious entries and delete them.)
515
516 When a boss is killed, ALL previous wipes for that boss are removed and
517 collapsed... even if they're on other days with other raids. If you only
518 raid with one guild, this can result in some amusing statistics ("kill
519 on 27th attempt" would actually mean something), but if there are multiple
520 raid configurations without clearing loot in between, then this number
521 is simply garbage.
515 ]] 522 ]]
516 523
517 T.todo_todolist = todo 524 T.todo_todolist = todo
518 525
519 526