Releases: lost-ark-dev/loa-details
1.2.5
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.2.5
- UI now saving horizontal/vertical scroll position when navigating within a session (resets when going back to session list)
1.2.4
- Fix esther not displayed in live
1.2.3
Esther update
- Esther will now be displayed in "dmg" tab
- Can be toggle on/off in
settings->damage meter->functionality->display esther
- Color can be customized in
settings->damage meter->functionality->esther color
meter-core (mostly for devs)
- guess player is only called on skill start (it'll prevent some unknown projectiles to be considered as player -> happened while you were inside shandi's world in g6 brel for ex)
- StatusEffect expiration fixes
- Esther support
- upgrade to typescript 5
- build config has been modified as i realized tsup bundle wasn't only type checking called methods
meter-data
- esther support
1.2.2
Shield tracking update by @Henjuro
-
4 new tabs:
- SHIELD D: Shield done (to you and other players)
- SHIELD G: Shield gotten (from you and other players)
- ESHIELD D: Effective shield done - shield done that has been consumed by damage
- ESHIELD G: Effective shield gotten - shield gotten that has been consumed by damage
-
You can toggle those tabs on and off in the settings
-
You can see overall value for each metric in the 1st column, and details per skills/source in the others
-
Those values will be available for all logs made after 1.2.0 after reparse
Regarding the rising number of tabs & columns
We are aware that live version is starting to be overloaded, but that this data is still interesting to see, and some of you might want to only enable some features for parse. We are currently reworking the settings format and will include a way to enable each settings independently for live & parse with that update
1.2.1
- Hotfixed meter live view not showing for some users (settings issue)
1.2.0
New log format
- Binary log format, allow for more data in a smaller space
- No more intermediate format when live parsing
- No more loa-details-log-parser
- The log file now contains content similar to raw packets, so it'll allow more data to be extracted from older logs when we add new features/fixes
loa-details
- Removed option to allow overkill -> now it'll always ignore overkill
- Improved back/front attack display: now only show for hits that could have been back/front attack (unless the target can't be back/front attacked)
- Upgraded dependencies (especially electron to 24.1.2 (node 18))
- Removed now unused dependencies (loa-details-log-parser, uuid, plateform-folders, worker-farm, lodash)
- Fixed Artist not being considered as a support
For devs
- You now can't look into log files by hand directly, you'll have to use meter-core and ReplayLogger class to parse log file into objects similar to packet objects. From that you can process it the same way it was done in LegacyLogger.
- But you can review all (known) packets with all their mapped fields using the log files, which may contain useful information that you lost with the previous format
About old logs
Old logs will just be ignored by loa details, you can delete them or save them in a folder if you want. Old log format won't be officially supported anymore, but you still could use the old version, if you edit it not to autoupdate.
Parsed format hasn't changed yet, but it is planned to be reworked soon. You'll just have to reparsed you raw logs when it's released and won't lose your logs again.
1.2.4
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.2.4
- Fix esther not displayed in live
1.2.3
Esther update
- Esther will now be displayed in "dmg" tab
- Can be toggle on/off in
settings->damage meter->functionality->display esther
- Color can be customized in
settings->damage meter->functionality->esther color
meter-core (mostly for devs)
- guess player is only called on skill start (it'll prevent some unknown projectiles to be considered as player -> happened while you were inside shandi's world in g6 brel for ex)
- StatusEffect expiration fixes
- Esther support
- upgrade to typescript 5
- build config has been modified as i realized tsup bundle wasn't only type checking called methods
meter-data
- esther support
1.2.2
Shield tracking update by @Henjuro
-
4 new tabs:
- SHIELD D: Shield done (to you and other players)
- SHIELD G: Shield gotten (from you and other players)
- ESHIELD D: Effective shield done - shield done that has been consumed by damage
- ESHIELD G: Effective shield gotten - shield gotten that has been consumed by damage
-
You can toggle those tabs on and off in the settings
-
You can see overall value for each metric in the 1st column, and details per skills/source in the others
-
Those values will be available for all logs made after 1.2.0 after reparse
Regarding the rising number of tabs & columns
We are aware that live version is starting to be overloaded, but that this data is still interesting to see, and some of you might want to only enable some features for parse. We are currently reworking the settings format and will include a way to enable each settings independently for live & parse with that update
1.2.1
- Hotfixed meter live view not showing for some users (settings issue)
1.2.0
New log format
- Binary log format, allow for more data in a smaller space
- No more intermediate format when live parsing
- No more loa-details-log-parser
- The log file now contains content similar to raw packets, so it'll allow more data to be extracted from older logs when we add new features/fixes
loa-details
- Removed option to allow overkill -> now it'll always ignore overkill
- Improved back/front attack display: now only show for hits that could have been back/front attack (unless the target can't be back/front attacked)
- Upgraded dependencies (especially electron to 24.1.2 (node 18))
- Removed now unused dependencies (loa-details-log-parser, uuid, plateform-folders, worker-farm, lodash)
- Fixed Artist not being considered as a support
For devs
- You now can't look into log files by hand directly, you'll have to use meter-core and ReplayLogger class to parse log file into objects similar to packet objects. From that you can process it the same way it was done in LegacyLogger.
- But you can review all (known) packets with all their mapped fields using the log files, which may contain useful information that you lost with the previous format
About old logs
Old logs will just be ignored by loa details, you can delete them or save them in a folder if you want. Old log format won't be officially supported anymore, but you still could use the old version, if you edit it not to autoupdate.
Parsed format hasn't changed yet, but it is planned to be reworked soon. You'll just have to reparsed you raw logs when it's released and won't lose your logs again.
1.2.3
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.2.3
Esther update
- Esther will now be displayed in "dmg" tab
- Can be toggle on/off in
settings->damage meter->functionality->display esther
- Color can be customized in
settings->damage meter->functionality->esther color
meter-core (mostly for devs)
- guess player is only called on skill start (it'll prevent some unknown projectiles to be considered as player -> happened while you were inside shandi's world in g6 brel for ex)
- StatusEffect expiration fixes
- Esther support
- upgrade to typescript 5
- build config has been modified as i realized tsup bundle wasn't only type checking called methods
meter-data
- esther support
1.2.2
Shield tracking update by @Henjuro
-
4 new tabs:
- SHIELD D: Shield done (to you and other players)
- SHIELD G: Shield gotten (from you and other players)
- ESHIELD D: Effective shield done - shield done that has been consumed by damage
- ESHIELD G: Effective shield gotten - shield gotten that has been consumed by damage
-
You can toggle those tabs on and off in the settings
-
You can see overall value for each metric in the 1st column, and details per skills/source in the others
-
Those values will be available for all logs made after 1.2.0 after reparse
Regarding the rising number of tabs & columns
We are aware that live version is starting to be overloaded, but that this data is still interesting to see, and some of you might want to only enable some features for parse. We are currently reworking the settings format and will include a way to enable each settings independently for live & parse with that update
1.2.1
- Hotfixed meter live view not showing for some users (settings issue)
1.2.0
New log format
- Binary log format, allow for more data in a smaller space
- No more intermediate format when live parsing
- No more loa-details-log-parser
- The log file now contains content similar to raw packets, so it'll allow more data to be extracted from older logs when we add new features/fixes
loa-details
- Removed option to allow overkill -> now it'll always ignore overkill
- Improved back/front attack display: now only show for hits that could have been back/front attack (unless the target can't be back/front attacked)
- Upgraded dependencies (especially electron to 24.1.2 (node 18))
- Removed now unused dependencies (loa-details-log-parser, uuid, plateform-folders, worker-farm, lodash)
- Fixed Artist not being considered as a support
For devs
- You now can't look into log files by hand directly, you'll have to use meter-core and ReplayLogger class to parse log file into objects similar to packet objects. From that you can process it the same way it was done in LegacyLogger.
- But you can review all (known) packets with all their mapped fields using the log files, which may contain useful information that you lost with the previous format
About old logs
Old logs will just be ignored by loa details, you can delete them or save them in a folder if you want. Old log format won't be officially supported anymore, but you still could use the old version, if you edit it not to autoupdate.
Parsed format hasn't changed yet, but it is planned to be reworked soon. You'll just have to reparsed you raw logs when it's released and won't lose your logs again.
1.2.2
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.2.2
Shield tracking update by @Henjuro
-
4 new tabs:
- SHIELD D: Shield done (to you and other players)
- SHIELD G: Shield gotten (from you and other players)
- ESHIELD D: Effective shield done - shield done that has been consumed by damage
- ESHIELD G: Effective shield gotten - shield gotten that has been consumed by damage
-
You can toggle those tabs on and off in the settings
-
You can see overall value for each metric in the 1st column, and details per skills/source in the others
-
Those values will be available for all logs made after 1.2.0 after reparse
Regarding the rising number of tabs & columns
We are aware that live version is starting to be overloaded, but that this data is still interesting to see, and some of you might want to only enable some features for parse. We are currently reworking the settings format and will include a way to enable each settings independently for live & parse with that update
1.2.1
- Hotfixed meter live view not showing for some users (settings issue)
1.2.0
New log format
- Binary log format, allow for more data in a smaller space
- No more intermediate format when live parsing
- No more loa-details-log-parser
- The log file now contains content similar to raw packets, so it'll allow more data to be extracted from older logs when we add new features/fixes
loa-details
- Removed option to allow overkill -> now it'll always ignore overkill
- Improved back/front attack display: now only show for hits that could have been back/front attack (unless the target can't be back/front attacked)
- Upgraded dependencies (especially electron to 24.1.2 (node 18))
- Removed now unused dependencies (loa-details-log-parser, uuid, plateform-folders, worker-farm, lodash)
- Fixed Artist not being considered as a support
For devs
- You now can't look into log files by hand directly, you'll have to use meter-core and ReplayLogger class to parse log file into objects similar to packet objects. From that you can process it the same way it was done in LegacyLogger.
- But you can review all (known) packets with all their mapped fields using the log files, which may contain useful information that you lost with the previous format
About old logs
Old logs will just be ignored by loa details, you can delete them or save them in a folder if you want. Old log format won't be officially supported anymore, but you still could use the old version, if you edit it not to autoupdate.
Parsed format hasn't changed yet, but it is planned to be reworked soon. You'll just have to reparsed you raw logs when it's released and won't lose your logs again.
1.2.1
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.2.1
- Hotfixed meter live view not showing for some users (settings issue)
1.2.0
New log format
- Binary log format, allow for more data in a smaller space
- No more intermediate format when live parsing
- No more loa-details-log-parser
- The log file now contains content similar to raw packets, so it'll allow more data to be extracted from older logs when we add new features/fixes
loa-details
- Removed option to allow overkill -> now it'll always ignore overkill
- Improved back/front attack display: now only show for hits that could have been back/front attack (unless the target can't be back/front attacked)
- Upgraded dependencies (especially electron to 24.1.2 (node 18))
- Removed now unused dependencies (loa-details-log-parser, uuid, plateform-folders, worker-farm, lodash)
- Fixed Artist not being considered as a support
For devs
- You now can't look into log files by hand directly, you'll have to use meter-core and ReplayLogger class to parse log file into objects similar to packet objects. From that you can process it the same way it was done in LegacyLogger.
- But you can review all (known) packets with all their mapped fields using the log files, which may contain useful information that you lost with the previous format
About old logs
Old logs will just be ignored by loa details, you can delete them or save them in a folder if you want. Old log format won't be officially supported anymore, but you still could use the old version, if you edit it not to autoupdate.
Parsed format hasn't changed yet, but it is planned to be reworked soon. You'll just have to reparsed you raw logs when it's released and won't lose your logs again.
1.1.15
- Support for game update: 12/04/2023 - Spring
- Add new guardian to encounters
- Improvements & fixes to buff tracking by @Henjuro
1.2.0
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.2.0
New log format
- Binary log format, allow for more data in a smaller space
- No more intermediate format when live parsing
- No more loa-details-log-parser
- The log file now contains content similar to raw packets, so it'll allow more data to be extracted from older logs when we add new features/fixes
loa-details
- Removed option to allow overkill -> now it'll always ignore overkill
- Improved back/front attack display: now only show for hits that could have been back/front attack (unless the target can't be back/front attacked)
- Upgraded dependencies (especially electron to 24.1.2 (node 18))
- Removed now unused dependencies (loa-details-log-parser, uuid, plateform-folders, worker-farm, lodash)
- Fixed Artist not being considered as a support
For devs
- You now can't look into log files by hand directly, you'll have to use meter-core and ReplayLogger class to parse log file into objects similar to packet objects. From that you can process it the same way it was done in LegacyLogger.
- But you can review all (known) packets with all their mapped fields using the log files, which may contain useful information that you lost with the previous format
About old logs
Old logs will just be ignored by loa details, you can delete them or save them in a folder if you want. Old log format won't be officially supported anymore, but you still could use the old version, if you edit it not to autoupdate.
Parsed format hasn't changed yet, but it is planned to be reworked soon. You'll just have to reparsed you raw logs when it's released and won't lose your logs again.
1.1.15
- Support for game update: 12/04/2023 - Spring
- Add new guardian to encounters
- Improvements & fixes to buff tracking by @Henjuro
1.1.15
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.1.15
- Support for game update: 12/04/2023 - Spring
- Add new guardian to encounters
- Improvements & fixes to buff tracking by @Henjuro
1.1.14
- Fix hp tracking for some npc summons (like valtan ghost phase)
1.1.13
- April fool settings hotfix
1.1.12
- Fix boss hp not being update properly after soft reset (made vykas g2,3 and many other 2nd boss hp wrongly displayed)
1.1.11
-
Changes to how current boss hp is displayed (should show the latest damaged boss). It means it'll show valtan g1 purple & ghost phase properly
-
Changes for buff skill source being wrongly assigned sometimes (thinking about arcana's cards, but some others as well)
-
Fix raid-global buffs (from items & bracelets) being displayed for 1 party only (meter-core): thx @Henjuro#1528
-
Ability to see buffs for the other party (seems that it's now possible unline during the initial research)
-
Added multithread parsing back so you'll see the usual log parse progress BUT it won't be as efficient as it used to be (because of the meter-data requirement in log parser now). I'm still thinking of better ways to do that.
---> Added a setting inSettings->Logs->Parser
to enable/disable multithread log parsing in case you are experiencing issues with it
1.1.10
- Improvements to skill source (especially for summons control)
- Added a new way to get localplayer & update info from Partyinfo. // Requirement is back to START METER BEFORE ENTERING RAID. (before means before the loading start, not during loading)
meter-core
- Slightly improved tcp reconstruction
raw socket
- Lowered chance of capture hang when using raw socket
- Improved buffer size to handle bigger packet burst
- Changes that should improve behaviour when having high bandwidth usage with other apps
- Improvement to sniffer that allow more accurate data to be captured
1.1.14
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.1.14
- Fix hp tracking for some npc summons (like valtan ghost phase)
1.1.13
- April fool settings hotfix
1.1.12
- Fix boss hp not being update properly after soft reset (made vykas g2,3 and many other 2nd boss hp wrongly displayed)
1.1.11
-
Changes to how current boss hp is displayed (should show the latest damaged boss). It means it'll show valtan g1 purple & ghost phase properly
-
Changes for buff skill source being wrongly assigned sometimes (thinking about arcana's cards, but some others as well)
-
Fix raid-global buffs (from items & bracelets) being displayed for 1 party only (meter-core): thx @Henjuro#1528
-
Ability to see buffs for the other party (seems that it's now possible unline during the initial research)
-
Added multithread parsing back so you'll see the usual log parse progress BUT it won't be as efficient as it used to be (because of the meter-data requirement in log parser now). I'm still thinking of better ways to do that.
---> Added a setting inSettings->Logs->Parser
to enable/disable multithread log parsing in case you are experiencing issues with it
1.1.10
- Improvements to skill source (especially for summons control)
- Added a new way to get localplayer & update info from Partyinfo. // Requirement is back to START METER BEFORE ENTERING RAID. (before means before the loading start, not during loading)
meter-core
- Slightly improved tcp reconstruction
raw socket
- Lowered chance of capture hang when using raw socket
- Improved buffer size to handle bigger packet burst
- Changes that should improve behaviour when having high bandwidth usage with other apps
- Improvement to sniffer that allow more accurate data to be captured
1.1.13
1.1.12
Installation (More info in README)
- Install Npcap with WinPcap compatibilities (Version 1.60 prefered)
- Run LOA-Details installer (You should uninstall previous verisons)
- Future updates will be pushed through the update feature of LOA-Details
Check out our new discord for support or any questions
Changelog
1.1.12
- Fix boss hp not being update properly after soft reset (made vykas g2,3 and many other 2nd boss hp wrongly displayed)
1.1.11
-
Changes to how current boss hp is displayed (should show the latest damaged boss). It means it'll show valtan g1 purple & ghost phase properly
-
Changes for buff skill source being wrongly assigned sometimes (thinking about arcana's cards, but some others as well)
-
Fix raid-global buffs (from items & bracelets) being displayed for 1 party only (meter-core): thx @Henjuro#1528
-
Ability to see buffs for the other party (seems that it's now possible unline during the initial research)
-
Added multithread parsing back so you'll see the usual log parse progress BUT it won't be as efficient as it used to be (because of the meter-data requirement in log parser now). I'm still thinking of better ways to do that.
---> Added a setting inSettings->Logs->Parser
to enable/disable multithread log parsing in case you are experiencing issues with it
1.1.10
- Improvements to skill source (especially for summons control)
- Added a new way to get localplayer & update info from Partyinfo. // Requirement is back to START METER BEFORE ENTERING RAID. (before means before the loading start, not during loading)
meter-core
- Slightly improved tcp reconstruction
raw socket
- Lowered chance of capture hang when using raw socket
- Improved buffer size to handle bigger packet burst
- Changes that should improve behaviour when having high bandwidth usage with other apps
- Improvement to sniffer that allow more accurate data to be captured