2.2.0
- Grouped configuration options together into a subcommand
- Added the 'deaths' command, which lists the available reports in the last specified amount of minutes

2.1.0
- Added a shorter slash command: '/exp'
- Added the 'refresh' command, which updates the unit tracking tables if (in rare cases) they are out of date
- Rewrote the basic history storage mechanism
- Expiration now saves copies of the current history when a unit being tracked dies, which are accessable separately later
- Added a new option to control the number of reports saved per unit
- Removed the 'say' option as a valid report channel
- Added the ability to report to custom channels
- Added the ability to whisper reports
- Modified the way the report command works:
usage: /expiration report <name> <report# or 'last'> [dest[:target]] [lines]
name - name of the player or pet to report on.
Just typing /expiration report <name> will list the available reports for that unit.
report# - The report number (from above) or 'last' for the last saved report.
dest[:target] - The destination for the report, along with an optional target.
	Valid destinations are:
	'console' - reports to the console, includes all appropriate combat string tags
	'party' or 'p' - reports to your party
	'raid' or 'r' - reports to your raid
	'guild' or 'g' - reports to guild chat
	'officer' or 'o' - reports to officer chat
	'whisper' or 'w' - reports in a whisper to the specified target
	'channel' or 'c' - reports to the specefied chat channel target
lines - the number of lines (from the death event) to report. Line numbers are listed in the report.
So, for example, the command '/exp report bob last w:sam 10' would report the last 10 events that happened to bob on his latest death report as a whisper to sam.

2.0.0
- Updated to work with patch 2.4
- Filter options removed
- Threshold option added
- Pets are now tracked
- Greatly improved event filtering logic

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.
