0.2.6

Release Candidate 0.2.6

Fixes

1. Refactored the log watcher, changing the algorithm that deals with partial log entries and removing the need for the flush delay.

0.2.5

Release Candidate 0.2.4

New Features

1. Added new log file settings, allowing the user to tweak the log file timings.
   
   a. Read delay is how often the log file should be checked after completing a read.
   b. Flush delay is how long to wait to flush the read cache after not seeing new log file entries. The reason this exists is to handle partial rendering from the EQ client, where partial log file entries are written.
   c. Error delay describes how long we need to wait before retrying a read operation after a disk failure. This most often occurs when a backup is performed.

Fixes

1. Fixed an issue that caused Nag to stop working after a backup.
2. Improved performance for DPS item rendering.

0.2.4

Release Candidate 0.2.4

Fixes

1. Multiple performance updates.
2. Fixed issues where Nag would stop responding.
3. Fixed encounter reset issues.

0.2.3

Hot fix

Fixes

1. Fixed an issue on TAKP servers causing repeated console errors.

0.2.2

Release Candidate 0.2.2

New features

1. Added an expanding section to the combat settings in the settings tab. The expanded section will allow the user to make changes to the entities.
   
2. Updated the combat stats to track player damage and healing by the target.
3. Added a dropdown menu on the DPS window to allow the user to select the data to view.
   
   

Fixes

1. Fixed issues with combat encounters not resetting consistently.

0.2.1

Release Candidate v0.2.1

New Features

1. Added the Patch Notes window.

Fixes

1. Fixed issues with combat reset times.
2. Synchronized reset times when sharing combat data.
3. Fixed an issue when parsing regular expression characters.
4. Improved NPC death handling to prevent combat encounters resetting mid-fight.
5. Refactored phrase caching, fixing an issue with DoT timers resetting when other players cast the same DoT (and other phrases that use the ${SpellBeingCast} variable.

0.2.0

Release Candidate v0.2.0

New Features

1. Added minimum damage input to register new encounters. If combat does not meet this threshold, the DPS meter and statistics will ignore it.
2. Reworked how combat stats are stored. Now, external combat logs are stored raw alongside your own.
3. Removed the encounter timing settings, now the end of an encounter is determined. This was needed due to log synchronization.
4. Added a record button to the DPS window. Encounters will be saved to disk when the record button is enabled. Future version updates will include options on exporting or viewing this data.
5. Added a footer to the DPS window that shows the current encounter and duration. When combat ends, the duration will be bolded.
6. Keep the combat window open after an encounter.
7. Added a clear button to the combat window to clear the current encounter, and hides the window if that option is enabled in settings.

Fixes

1. Several performance updates to the combat and trigger parse functions.
2. Fixed several issues preventing users from joining log sync servers.
3. Fixed several issues with the DPS window rendering and positioning.
4. Fixed an issue that was syncing all combat logs in real-time, instead of at the end of an encounter.
5. Fixed an issue where combat sync was still engaging even when combat statistics are off.

0.1.77

New Features

1. Log Synchronization (see below)
2. Refactored the file monitor.
3. Refactored logging to include the majority of errors and information in the Nag Console.

Fixes

1. Fixed a null reference error when grabbing a list of disabled triggers for a character.
2. Fixed an issue causing the log watcher to hang if closed when receiving data.
3. Fixed an issue when calling the renderer.
4. Improved the file monitor error handling.
5. Fixed issues with the backFind method.
6. Fix encounter reset timer issues.

Log Synchronization

Added a system that allows players to sync their combat data with other players. You can create or join a server (you can think of this as a chat room for Nag) that will allow your Nag client to communicate with other Nag clients. Only players connected to your server will share log information.
The first time you connect to a server, windows should ask you if you want to allow Nag to use the network.

This uses WebRTC technology. Accordingly, if you have peer to peer (p2p) traffic blocked on your firewall then you'll need to add an exception for Nag. Also, some VPNs may block p2p networks.

Log synchronization works in two ways.
First, your combat statistics will be shared with anyone else connected to the server. This includes your DPS, engagement time, Heals, HPS, but does not include a dump of your combat logs.
Second, once an encounter has ended, you will then share your entire combat logs with everyone connected to the server. This will include every hit on every mob and every heal on every player.

The first change is to the menu. Combat Statistics and FCT have been combined:

There is an icon that will indicate which character is monitoring combat data. Only one character can monitor combat logs at a time.

You can switch by clicking on the button for a different character.

In the combat statistics panel, you'll see the option to create or join a server.

Clicking on create or join, you'll get two different buttons to leave or copy the server link.

Below the server info panel, you'll see the server console.

And finally, you'll have the server trust section. Here you can specify players that you want to trust or block. Receiving a server link from a trusted player will automatically connect you to that server, as long as you aren't already connected to a server. Receiving a server link from a blocked player will be ignored. Any other links will open a dialog to allow you to connect/ignore/trust/block.

0.1.72

New Features

1. (EXPERIMENTAL) Experimental combat statistics features.

Fixes

1. Fixed parsing errors in the FCT parser.
2. Forward application exceptions to the Nag Console.
3. The console now displays system messages as well as trigger parse history.
4. Moved combat statistics and FCT processing to a separate thread, segregated from trigger parsing to improve performance.
5. Added exception catch to sub-actions.
6. Refactored NPC processing to improve performance.

0.1.68

Fixes

1. Fixed an issue that was erroneously applying normal combat hits to the wrong combat groups.