LostControl

2017-08-12 (3.9)

• Changed how the debuff watch checkboxes have their config saved
• Airborne message now uses same player role config as other messages

2017-07-16 (3.8)

• Fixed bug that meant the first report of a problem ignored your min debuff time configuration
• Fixed bug that meant the recovery message could be sent when the initial message wasn't
• Fixed bug that meant some debug messages ended up in chat
• Improved logic around when to say the recovery message
• Added spec & role updates to a couple of game events to ensure I'm working with the correct role

2017-07-05 (3.7)

• Fixed bug with 'player is airborne' alert introduced by an API change at some point
• Added ability to toggle the falling message in the options panel

2017-06-03 (3.6)

• Updated interface number to remove 'out of date addon' warnings

2015-10-07 (3.5)

• Minor change - reduced sensitivity of "player is airborne" message and updated interface number to stop the addon seeming out of date

2015-01-03 (3.4)

• Made it possible to customise the whole announcement message, not just the second part
• (If you have already customised the second part of the message, to make it look like before start the message with "%REF ")

2015-01-01 (3.3)

• Fixed possible error in messaging code
• Moved Charge as a named debuff from stun to root
• Fixed detection of phrases disoriented and sapped under incap
• Fixed usage of the min debuff time config
• Added ability to customise the second part of the announcements (i.e. The healer (Shamlot) {your text here})

2014-12-30 (3.2)

• Fixed numerous messaging issues, including requiring a group to use the SAY channel and missing/repeated callouts

2014-12-29 (3.1)

• Stopped messages appearing too close to each other near the end (avoids "1 second remaining", "no longer..." chat spam)

2014-12-29 (3.0)

• Added support for multiple languages (translations require completion)
• Changed storage of configs, so that they are now not only per character, but also per role (dps/healer/tank)
• Fixed a bug introduced in v2.6 with the 'say' channel
• Some behind-the-scenes improvements