Skip to content

Releases: ravahn/FFXIV_ACT_Plugin

Release v1.4.2.20

10 Oct 00:05
Compare
Choose a tag to compare
  • Updated Zone Mapping for 3.4 zones - Unfortunately a failed copy/paste excluded these from the last release
  • Updated line type 0x14 (starts using / starts casting lines from network data) to catch new network identifier
  • Adjusted Nocturnal Field damage shield from 100% to 150%/170% depending on ability used.
  • Minor adjustment to damage down effect for new 3.4 zone to improve DoT tick amounts

Release v1.4.2.19

28 Sep 13:08
Compare
Choose a tag to compare

Includes fixes to support FFXIV patch 3.4, both dx9 and dx11 versions.

Release v1.4.2.17

10 Jun 04:08
Compare
Choose a tag to compare

Released some more 3.3 fixes:

  • Fixed memory-mode parsing post-3.3 - The byte order in memory changed to more closely match network data byte order.
  • Fixed DX9 Parse Filter party detection - the party structure size changed in DX9, but I didn't catch it in my previous update.

The combination of these two should resolve the problems where people are only seeing their own damage, and only seeing autoattack damage.

Release v1.4.2.16

07 Jun 16:07
Compare
Choose a tag to compare

Released v1.4.2.16 to support FFXIV patch 3.3.

Network mode parsing should work - there was a structural change to the packet format for combat data. Memory-only parsing is not yet working, but should be fixed in a couple of days.

Release v1.4.2.9

26 Feb 19:59
Compare
Choose a tag to compare

Changes from v1.4.2.9:

  • Added zone name XML resource back temporarily, since other ACT plugins assumed it was there. This will eventually get removed.
  • Re-added Player stats (STR, VIT, Crit, etc) logging for theorycrafters. Weapon damage is not included.
  • Fixed focus target overlay for DX11 to point to the correct location

Changes from v1.4.2.7:

  • Updated party member record size - increased by 16 bytes, which broke the ACT Parse Filter option
  • Updated offsets for memory mode with dx11 client
  • Modified memory mode (both dx9 & dx11) tracking of 'starts casting' messages to actually use the starts-casting offset. It was using the 'completed casting' offset instead.
  • Replaced Zone Name XML list with a list of instances from the DAT files. This will make it faster to add the new instanced zones after a patch.

Version 1.4.2.6 - FFXIV Patch 3.20

23 Feb 18:25
Compare
Choose a tag to compare

Update with preliminary support for FFXIV patch 3.20.

Memory mode is not functional, but DX9 / DX11 network mode both work.

Release v1.4.2.5

17 Nov 16:48
Compare
Choose a tag to compare

Updated to version 1.4.2.5:

  • Fixed a hard-to-find bug that was causing problems for FFLogs: debuffs (for example, DoTs) were not always getting refreshed properly in the log data. ACT parses were not affected, but parses on FFLogs were missing DoT ticks.
  • FC action buffs are now filtered from the log data, they were causing log inflation.
  • Removed logging of player stats and weapon damage from the log data, these frequently break on updates and have a very limited use. If people really want them back, contact me via email and we’ll talk.
  • Slightly modified buff text in ACT to include the duration that a buff lands for (i.e. “target gains the effect of Phlebotomize from player for 24.00 seconds.”).
  • Minor optimization to network data gathering – the code was storing a list of combat actions on each target that was never getting released.
  • Added some Zone ID’s – thanks to EQ2Flames user Xephero!
  • Fixed Memory Mode DoT simulation so it should work after FFXIV patch 3.1

Release v1.4.2.3

10 Nov 21:40
Compare
Choose a tag to compare

v1.4.2.3 of the FFXIV ACT Plugin is released.

This includes updates to support FFXIV patch 3.1. It is an early release so that the majority of players can start parsing again, and few features have not been fixed yet. I anticipate another release tomorrow.

Here's what is confirmed not to work:

  • Missing Zone IDs - as usual, none of the new zone names are included. Please email the zone ID and name to me (ravahn at hotmail.com) or post them here.
  • Memory Mode DoTs are disabled. It takes significant work to decode the DoT memory structure, and I wanted to get this update out before I spend time on that. The rest of Memory mode should work, but I strongly suggest unchecking the 'Disable Parsing from Network Data' checkbox, and either adding the firewall rule or installing WinPCap instead (http://www.win10pcap.org/). I have added a popup message to this release when the plugin loads to warn when memory mode is turned on. This will be removed when I have fixed DoTs.
  • The plugin previously recorded the current player's stats and weapon damage in the log file. This feature is not currently working, but will be fixed in the next update.
  • I haven't been in any new zones, so there may be issues with buffs and other new features that are not parsed properly.

Release v1.4.2.1

01 Nov 23:20
Compare
Choose a tag to compare

Released v1.4.2.1. Changes include:

  • Added a new feature to network parsing to pull network data from the established WinPCap library, instead of using my own code. This feature requires installing a separate program from http://www.winpcap.org/ or http://www.win10pcap.org/. Consider it a Beta feature for now, but I'm adding it in the hopes that people who cannot get network parsing to work due to issues with conflicting software or windows security may be able to use this instead. It can be enabled by checking the "Use WinPCap" checkbox on the FFXIV Settings tab.
  • Fixed some buff issues with Damage Down effects in some of the Savage zones that were causing incorrect DoT calculations. There may be other buff issues that I need to take a look at, but this was particularly bad.
  • Fixed a bug that prevented some buff durations from being refreshed in the log data. Most notably this affected Foe Requiem, which is refreshed automatically every three seconds.
  • Added back the human-readable log information when buffs are added/removed so that custom triggers work again. This should match what was there before v1.4.2.0, with the addition of the number of buff stacks added to the end of the line.
  • Fixed a network parsing-related bug that was occasionally showing errors about insufficient buffer space.

For those wishing to help me improve the parser, I could use some log data from v1.4.2.1 of the plugin in 8-man zones. As usual, these would be the files named Network_yyyymmdd.log in the C:\Users%USERNAME%\AppData\Roaming\Advanced Combat Tracker\FFXIVLogs folder. You can email them to me at ravahn (at) hotmail.com.

Release v1.4.2.0

27 Oct 01:25
Compare
Choose a tag to compare

This release primarily affects where buff data is pulled from when parsing in network mode. Previously it was pulled from game memory, but now it is retrieved from the network packets directly. This should provide more accurate time synchronization when calculating damage effects and DoT tick amounts.

Other changes include:

  • Added some memory reading features to assist with WitcherMog's new overlay add-on.
  • Modified log writing routines to replace NULL characters with spaces.
  • Implemented correct potency for Death Blossom with / without the enhanced trait.
  • Modified the DoT tick count for Scourge with / without the enhanced trait.
  • Fixed the DoT crit bonus damage amount to correctly snapshot crit buffs at the time of application. Previously it was trying to calculate based on active buffs using the buff timestamp, which could occasionally be problematic.

I'm going to work next on a change to network parsing to optionally retrieve data using the WinPCap network packet capture driver. This may allow people having problems with network parsing mode to get it working. However, it will of course require downloading and installing the free WinPCap driver separately from the FFXIV Plugin.

As I've stated before, the memory parsing mode will miss some combat data, and should not be used except as a last resort. In particular, Wildfire is a problem.