OverParse

[TyroneSama]

Now that the situation has calmed down a bit, I would like to present two ideas. I know OverParse is freezed, so I'm not requesting them:

#1 is possible and something I've thought about myself. #2 is possible, excluding Megiverse, but I have no plans to implement it because HPS is not a useful metric in a damage-race game. ACT does an adequate job, though.

If that is true, then I think there are two or three (evil) things that can be done to prevent future GameGuard Detection:

They gave up as soon as straight-up MD5 checks stopped working on the mounter. I honestly don't think anything further should be necessary, just some kind of utility to dodge hash checks on PSO2DamageDump same as OverMounter. With that said, there is plenty of stuff we can do to foil further attempts if SEGA or GG feel like trying again.

[DrCatco]

Thank you, that's all I wanted to know. I would like to see #1, but there's no hurry.

[Kr1zalid]

....Also faster and less taxing on disc usage. Breaks ACT but who cares about ACT right?....

Maybe I'm the only one but being able to ACT helps me realize some things Overparse cannot do atm, such as "what time a particular type of damage was done" and damage/time graphs.

Being said that Overparse is still nice and this...

....Accessibility is a big goal of mine, after all.

Really...thank you!

EDIT: Wrong quote...sorry

[elryan]

They gave up as soon as straight-up MD5 checks stopped working on the mounter. I honestly don't think anything further should be necessary, just some kind of utility to dodge hash checks on PSO2DamageDump same as OverMounter. With that said, there is plenty of stuff we can do to foil further attempts if SEGA or GG feel like trying again.

Maybe it's just me but I'm those types of paranoid programmers. Because I feel the next thing SEGA will do instead of preventing OverParse from running is:

IF (There are damage logs in existing folder) OR (There is an executable / dll named ...) THEN { ban player }

So doing in-memory parsing and obfuscating process name is probably paramount for account security. The memory protection is overkill and just for giggles though.

[TaigaUC]

It'd be funny doing overkill just to see if SEGA ever manages to catch up.

[FireswordRus]

They gave up as soon as straight-up MD5 checks stopped working on the mounter. I honestly don't think anything further should be necessary, just some kind of utility to dodge hash checks on PSO2DamageDump same as OverMounter. With that said, there is plenty of stuff we can do to foil further attempts if SEGA or GG feel like trying again.

i am need that new version with PSO2DamageDump protect

[TyroneSama]

i am need that new version with PSO2DamageDump protect

For now, you can grab Variant's new version, or hex edit it yourself and add some random data onto the end.

[milranduil]

since i haven't seen the number stated and i don't have OP anymore, can someone who does tell me XH odin's HP in the LQ?

[Kr1zalid]

since i haven't seen the number stated and i don't have OP anymore, can someone who does tell me XH odin's HP in the LQ?

Total HP should be around 12-12.5M, not sure when he'll do the "ultimate quest auto fail skill" tho (too much Gurens from other players since the beginning of fight)...will try check if you want

[milranduil]

Total HP should be around 12-12.5M, not sure when he'll do the "ultimate quest auto fail skill" tho (too much Gurens from other players since the beginning of fight)...will try check if you want

that sounds right based off of a few solos i've watched. thanks.