Releases: PinkGayRobot/OverParse
Release list
OverParse v1.16.2
Always launch OverParse from OverMounter.exe to prevent GameGuard detection.
OverParse needs the following files to be in the following places to function:
- place pso2h.dll in your
pso2_bindirectory - place ddraw.dll in your
pso2_bindirectory - place PSO2DamageDump.dll in your
pso2_bin/pluginsdirectory
If you launch the game using PSO2 Tweaker, it will take care of the first two for you automatically: all you have to do put the PSO2DamageDump.dll from OverParse/Resources in the right place.
During setup, you will be asked if you use the Tweaker. If you don't, OverParse will attempt to install the plugin files automatically: if this doesn't work or causes problems, select "Yes" when asked if you use the Tweaker, and do the install yourself.
If you're booted from the game with an NP1013 error, GameGuard is probably detecting the damage dump plugin. To fix this, open the file in any hex editor, scroll to the bottom, and add or change some of the data at the end of the file. This changes the checksum and prevents GameGuard from recognizing it.
Windows Defender may detect this, or files inside it, as a virus. These are false positives. OverParse's complete source code is available on this page, and the source for PSO2DamageDump.dll is available here.
You can reset OverParse at any time from the Help menu. If you can't reach the Help menu, you can delete AppData/Local/OverParse to reset configuration.
Original changelog:
- Fixes update prompt loop. I'm fucking stupid.
1.16.1 Changelog:
- Trimmed down debug logging. You may want to delete your OverParse/Debug folder, as it's probably bloated with moronic, inefficient logging (mine was over 500MB). My bad.
OverParse v1.16 - Important
Changelog:
- Added a one-time warning about third-party parsing tools and the risk they pose to your account. See below.
Parsing tools and the future of OverParse (please read!)
Sega recently made an official statement confirming that use of third-party parsing tools will be enforced as a bannable offense. After a number of failed attempts to block it via GameGuard, this makes it perfectly clear that OverParse does not activate in the same blind-spot grey area that the Tweaker and other popular tools do.
For the time being, this will be the final OverParse release. The program will only be maintained for the sake of bug fixes, and no support is available. Additionally, if you use the Tweaker, you've probably already noticed that the damage dump plugin was automatically removed. If you'd like to add it back, you can copy PSO2DamageDump.dll from OverParse's Resources folder to pso2_bin\plugins, or follow AIDA's instructions here.
For users without the Tweaker, to remove all third-party plugins, delete pso2_bin\pso2h.dll, pso2_bin\ddraw.dll, and pso2_bin\plugins. If you want to leave your third-party plugins intact, but remove the parsing plugin, simply remove pso2_bin\plugins\PSO2DamageDump.dll.
You may still continue using OverParse and the parsing plugin if you wish. For the time being, SEGA seems unable to detect parsing tools using automated methods, as the latest OverMounter broke their detection method. Their statement seems targeted towards players who are posting parse data publicly, or those who are being abusive with the information. However, this is only speculation and could change at any time. If account safety is your first priority, as always, you should be running a vanilla, unmodified game client with no third-party tools.
I won't speculate on why SEGA is behaving this way: I believe that the positive effects of the parser dwarf the rare negatives. Otherwise, I wouldn't be working on it.
OverParse's impact went far beyond my expectations: with nearly 20,000 downloads between this branch and @nemomomo's Japanese fork, I'm continually inspired to see so many players pushing themselves and analyzing their performance, both solo and in groups. I'm proud to be responsible for OverParse, and I'm proud to have made a mark on the PSO2 community.
However you decide to proceed, please be safe. Thank you for being a part of this.
OverParse v1.15.2
Changelog:
- OverMounter update to dodge GameGuard, again. This should completely invalidate their current detection method. Whether or not they step things up, or when they do so, is entirely up to how much time they want to spend chasing a completely harmless auditing tool.
Siiiiigh.
OverParse v1.15.1
Changelog:
- OverMounter update to dodge GameGuard, again.
OverParse v1.15 - Fuck You NP1013 Edition
Changelog:
- Reworked the method used for directory selection, to prevent problems where the folder picker wasn't showing up.
- Removed a few old dependencies that are no longer used.
- Added
OverMounter.exe, a tool that launches OverParse within itself to bypass GameGuard's NP1013 errors. All credit for this goes to @Zogzer, I did nothing but test it. Let me know if you run into issues.
OverParse v1.14.2
Changelog
- Fixed an issue introduced in 1.14.1 where Ilzonde damage would be classified as AIS damage. Instead of, y'know. AIS damage being counted as AIS damage. This is an option that I use internally while testing separation logic, dunno how it made it into a full release. My bad!
OverParse v1.14.1
Changelog:
- Fixed a bug where percent contribution would be written to detailed logs as
0.0%. Oops. Thanks, Ruchia! - Fixed an ancient bug where raw DPS would be incorrectly written to detailed logs with
Show raw DPSenabled.
OverParse v1.14
Changelog:
- Support for the new damage dump plugin, which tracks and assigns AIS damage correctly! AIS damage can be separated or toggled in
Parsing > AIS options. Tweaker users should force a plugin update from the Plugins menu: vanilla users will be prompted to update when launching OverParse. - When Zanverse is separated, its max hit will now be correctly displayed on the window, and players will no longer have their max hit recorded as Zanverse.
- Fixed an issue where the encounter timer sometimes wouldn't update.
- Fixed an issue where combatants wouldn't be correctly resorted when toggling Zanverse separation.
- Ending and discarding encounters is now much more responsive.
- Trimmed down the debug logs to reduce disk usage.
OverParse v1.13.2
Important update that fixes a number of parse-related bugs introduced in 1.13.
Changelog:
- Fixed an issue where damage percentages could be calculated or displayed incorrectly.
- Fixed an issue where group DPS could be displayed incorrectly.
- Fixed an issue where the encounter log wouldn't fully update after toggling Zanverse separation.
- Fixed an issue where Compact Mode wouldn't display your maximum hit in the status bar.
- When separated, Zanverse is now correctly marked as a percentage of group damage. This was changed to provide a more accurate picture of where your damage is coming from.
Sorry for any confusion!
OverParse v1.13.1
The usual post-update fixes.
Changelog:
- Fixed an issue where log headers would report time in UTC, instead of local time.
- Fixed an issue where the combatant list could become unsorted when toggling Zanverse separation on a past encounter.
Show only playersnow updates instantly when toggled. Snappy.