You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that timestamps edited with TrophyIsGood are perfectly detectable by trophy tracking sites.
They use, tipically, scripts in Java that "dump" a PSN profile's trophies ed succeed in identifying edited timestamps.
After a bit of analysis, it seems that, when converting from hh:mm:ss to ticks, TrophyIsGood sets to "0000" the milliseconds of the timestamps (in fact the milliseconds are not editable by user).
If confirmed, is it possible to make the milliseconds editable or to introduce a "randomization" mechanism for the milliseconds part?
The text was updated successfully, but these errors were encountered:
Hi all,
I noticed that timestamps edited with TrophyIsGood are perfectly detectable by trophy tracking sites.
They use, tipically, scripts in Java that "dump" a PSN profile's trophies ed succeed in identifying edited timestamps.
After a bit of analysis, it seems that, when converting from hh:mm:ss to ticks, TrophyIsGood sets to "0000" the milliseconds of the timestamps (in fact the milliseconds are not editable by user).
If confirmed, is it possible to make the milliseconds editable or to introduce a "randomization" mechanism for the milliseconds part?
The text was updated successfully, but these errors were encountered: