1.2.1
- The 'event' option is now an actual command-line option
- Removed minutes from the timestamp
- Added feedback when you add or remove filters
- Should no longer be possible to add overlapping filters

1.2.0
- Added a 'filter' set of options to the command line. When one of the filter strings is found in the combat message, it will not be recorded
- The 'dest' option now determines what channel Expiration reports to by default
- Added two optional arguments to /expiration report <name> [channel] [lines]
	- [channel] overrides the default channel for reports
	- [lines] causes expiration to only report the last n lines of logged events
	- if the second argument is a number, it is assumed [channel] has been omitted and the argument is [lines]
- Fixed spam when trying to report to a channel that doesn't exist (party when you're not in a party, raid when you're not in a raid, etc)
- If the 'event' option is true, Expiration will attach the combat event which caused each message to the end of the message. This can be set with a script command: /script Expiration.db.profile.event = true;

1.1.1
- Now when the death option is on the next 5 events after the player's death will be tracked
- The report command is no longer case-sensitive
- Reports should return fewer false positives
- Removed many events that contributed nothing (or spam) to the reports.

1.1.0
- Removed tracking of CHAT_MSG_SPELL_FAILED_LOCALPLAYER
- Removed tracking of CHAT_MSG_SPELL_ITEM_ENCHANTMENTS
- Added an option to stop event tracking on player death
- Added an option to add player health to logged events

1.0.0
- Initial version.
