HGL
diverse-rose
Comet not unlocking achievements
13 Replies
diverse-roseOP•2y ago
@Linguin
optimistic-gold•2y ago
hmm
header 15 is a
GET_USER_STATS_REQUEST
23 is a GET_USER_ACHIEVEMENTS_REQUEST
request 25 is the one that's supposed to unlock the achievementdiverse-roseOP•2y ago
so for some reason it thinks i already have it?
optimistic-gold•2y ago
probably, or the SDK doesn't like comet's responses
since it tries to get the achievements multiple times
I'm going to refactor comet to be faster and capable to work offline eventually, current Python code does http request for each call with no caching, which is noop apparently
diverse-roseOP•2y ago
what language
python again?
optimistic-gold•2y ago
Rust
the branch is up already (only auth is call implemented though)
diverse-roseOP•2y ago
ah okay i take it you wont want to try to debug this issue then
i could probably use the galaxy offline emu for achievement tracking rn
i think its called nemiritingas galaxy emu or something
optimistic-gold•2y ago
yeah, sorry I can't help. This is probably due to comet taking too long to respond thus SDK never accepts the data
diverse-roseOP•2y ago
does the gog api allow uploading the unlock time or something
optimistic-gold•2y ago
only through comm service provided by Galaxy
which comet aims to implement for Linux users
diverse-roseOP•2y ago
so if i use that local galaxy emu which saves the time of unlock to a json file comet could tell gog I unlocked the achievement x days ago in the past and itd show up as that
oops
wrong reply
optimistic-gold•2y ago
no, it doesn't work that way I think
although
technically
it may be possible
I don't know how microservices would interpret that
diverse-roseOP•2y ago
well in the code its just setting achievement.unlock_time to a unix epoch value and those will always be in the past
plus theres also the fact that galaxy has offline achievement support
so it has to accept achievements from in the past
so it probably will work