Archisteamfarm: Status for succeeded key redemption is NoDetail instead of Success

Created on 6 Mar 2017  路  5Comments  路  Source: JustArchiNET/ArchiSteamFarm

Since very recently (idk when it started, possibly after update) every succeeded key redeption gives out the following message:
<bot> Key: key | Status: NoDetail | Items: [123, Game]
The game is in the library afterwards as usual, it's just quite distracting.

Side note: when redeeming more keys than bot count, with all bots set to distribute and such, they will not cycle the leftover keys further after getting from the first to last bot. That makes redeeming with the otherwise good efficiency quite annoying (stacking keys with CTRL+Enter inbetween) as you need to resend all unused keys again and again, so maybe the redemption loop should instead end if the same key went through all bots once, with the result that all bots already have that game.

Not a bug Won't fix

Most helpful comment

@Ryzhehvost SK2 added reverse-engineered headers from Steam client, and this is how Valve named all statuses. Previously ASF would have barely 9-10 recognized statuses based on my own tests, so they were also named after me. Now ASF switched to "official" types specified by Valve, which isn't only crucial compatibility-wise, but also far more complete, since those headers include over 100 different statuses, while ASF had barely 9-10 previously.

If I change something, I always have a very good reason behind it. I don't like this generic NoDetail either, and I could "patch it up" to return something better, but I intentionally don't want to do this, since ASF should return status as compatible with Valve status as possible, instead of what I think "looks better".

All 5 comments

Sorry, just realized that that is intended as is.

Well, I liked previous status codes better, but if I understend it right - it's not up to ASF, it's just the codes SteamKit2 returns changed.

@Ryzhehvost SK2 added reverse-engineered headers from Steam client, and this is how Valve named all statuses. Previously ASF would have barely 9-10 recognized statuses based on my own tests, so they were also named after me. Now ASF switched to "official" types specified by Valve, which isn't only crucial compatibility-wise, but also far more complete, since those headers include over 100 different statuses, while ASF had barely 9-10 previously.

If I change something, I always have a very good reason behind it. I don't like this generic NoDetail either, and I could "patch it up" to return something better, but I intentionally don't want to do this, since ASF should return status as compatible with Valve status as possible, instead of what I think "looks better".

Thanks for the explanation! I wasn't aware there are so many different statuses, might want to examine what they got there.

Be my guest 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

guihkx picture guihkx  路  4Comments

Sirogabober picture Sirogabober  路  4Comments

Revadike picture Revadike  路  3Comments

JustArchi picture JustArchi  路  4Comments

zypA13510 picture zypA13510  路  3Comments