I'm working on a combat log replacement, designed to allow filtering, formatting and redirection of all incoming combat log events.
Events are broken down individually, allow a fairly high level of control over individual events. At this time, events not involving the player are filtered, but the ability to configure them is planned as well.
Events are sorted by direction (incoming/outgoing), prefix and suffix.
Currently handled events are damage, healing and buff gains/losses. This will eventually be expanded to include all combat events.
Each event has 3 options: Text displayed, color and chat frame for output. Criticals for events which can crit are configured separately.
Handling for each event type can be enabled or disabled.
Event text is handled similarly to strings in Pitbull or Parrot, with tags to handle dynamic tags. I'm currently using my own tagging system, but if I can figure out a way to utilize DogTags that makes sense, I'll probably do so.
This is still raw, but there are currently 9 valid tags for events:
[Source] - name of the player who caused the event.
[SourceServer] - name of the player including server, if in a BG.
[Target] - name of the player the event was directed at.
[TargetServer] - name of the player including the server, if in a BG.
[Amount] - numeric amount for the event (healing, damage)
[School] - spell school for the event (Physical, Shadow, etc)
Note that not all tags apply to all events. Eventually I'll properly document this, but for most events, it should be common sense. If a tag is found with no matching event attribute, it will be replaced with "unknown".
By default, the chat tab is set to 2, which is the default combat log. I highly suggest either added a completely empty filter to the combat log (so only the XLog text is added), or creating a new chat tab for use with XLog.
Chat tabs can be set to any available chat tab, or "Inherit". If set to inherit, events will use the parent tab (set under incoming/outgoing). If the incoming/outgoing chat setting is also inherit, it will default to the parent tab (set under General).
Note: Chat frames are scanned on load; if you add a new tab after XLog is loaded it won't be displayed in the list. Reload the ui, or log out/back in to update the list. I'll try and find a better way of handling this in the future.
I need your help!
XLog is still very raw. It doesn't handle all events, and it has limited documentation. If you have suggestions on how you feel something could be made better, please don't hesitate to let me know. In particular, I'm interested in missing events you think should be added, or any incoming/outgoing spells that either don't register, or cause an error.
Coloring is there, its just currently on a event by event setting (ie: SWING_DAMAGE and SPELL_DAMAGE can be different, and are by default). I think what Blood was looking for was the ability to color individual parts of each event; right now the color setting affects the whole line.