Replying to @amia_dev @0fficialxero
* multiple variants of
the same game quest causing http 500 as they send the api requests all at once (which often turned the 15 minutes into 30+ minutes), etc.
Replying to @amia_dev @0fficialxero
- rush complete quests which discord published by mistake and unpublished within minutes
- deal with bugs such as:
* multiple variants of the same activity quest counting the wrong quest (they all share the same activity which relies on a client-side header),
Replying to @amia_dev @0fficialxero
- often play the same activity quest from different regions several times (I did the Forgotten Island quest so many times I started figuring out ways to speedrun it lmao)
- use api shenanigans to enroll into internal quests and some A/B quests
Replying to @amia_dev @0fficialxero
None of this changes the fact that it took a lot of effort to:
- datamine every single new quest
- figure out which country/state it's locked to and vpn to it
- often watch the same video quest from different regions several times
Replying to @VanillaShakeVA @doodletime_
Pjsk uses the same snowflake system for player ids as discord and twitter do, so the creation timestamp is embedded within them and can be extracted easily
Replying to @stiIIvivid
LMAO you're unlucky, they messed up the data for specifically that event years ago (see the missing rank field)
At least you still got the highest reward














