Archisteamfarm: Export maFiles

Created on 18 Aug 2020  路  5Comments  路  Source: JustArchiNET/ArchiSteamFarm

Feature request

Purpose

If you have a large amount of bots and you _have to_ use a new phone under the same number exporting maFiles could be a useful not to repeat all the extracting procedure again (ArchiSteamFarm deleted the extracted files) and import your accounts into Steam Desktop Authenticator.
_(since there's no page in ArchiSteamFarm to accept or deny Steam Community Market transactions)_

Solution

Why currently available solutions are not sufficient?

There's no page in ArchiSteamFarm to accept or deny Steam Community Market transactions and users might want to use maFiles for development purposes or with additional tools.

Does your suggestion fall into ASF scope?

Yes, ofc. It's about trading.

Is your suggestion abiding to Steam guidelines?

Yes, I just want to uninstall the Steam app and use a Steam Desktop Authenticator.

I know Steam Support won't provide me help with whatever happens because of it.
Enhancement Not going to happen Not possible Out of the scope

All 5 comments

ASF can accept or deny Steam Community Market transactions.
ASF does not store all necessary data from mafile, so export is not possible.

ASF can confirm market orders.
ASF-ui: bots -> bot -> 2FA (lock icon) -> accept all trades
ASF API: curl -H "Authentication: ..." http://localhost:1242/Api/Bot/$botname/TwoFactorAuthentication/Confirmations/Accept -d ''

As stated above.

There's no page in ArchiSteamFarm to accept or deny Steam Community Market transactions

There are 2fa, 2faok and 2fano commands, along with IPC API endpoints achieving the same, recently even enhanced to allow more customization.

import your accounts into Steam Desktop Authenticator.

This is not possible. ASF never stored all the details needed to convert ASF 2FA into a fully functional Steam authenticator, but with recent change automating device_id field and therefore dropping even that from the files themselves, you don't even have enough details to handle confirmations themselves without a fully functional Steam client capable of retrieving device_id of your authenticator.

Also, exporting ASF 2FA as general authenticators is not just impossible, but out of the scope of ASF. ASF is not "Steam authenticators manager" to have such functionality. Import is one-way only. Steam allows you to transfer authenticator through different devices, you should use that option for moving authenticator from one phone to another, and that to the best of my knowledge does not require purging ASF 2FA, as only device_id field changes, the one which ASF doesn't store anymore, as it's capable of retrieving it on-demand.

I dare to mention, that I implemented moving of steam auth to SDA too, you can get my fork here: https://github.com/Ryzhehvost/SteamDesktopAuthenticator/releases/tag/1.1.1
(I sent a PR to official SDA, but it's not merged yet).

ASF API: curl -H "Authentication: ..." http://localhost:1242/Api/Bot/$botname/TwoFactorAuthentication/Confirmations/Accept -d ''

<2
Thank you so much :P

Was this page helpful?
0 / 5 - 0 ratings

Related issues

light444 picture light444  路  3Comments

zypA13510 picture zypA13510  路  3Comments

undefo picture undefo  路  4Comments

Sirogabober picture Sirogabober  路  4Comments

jat001 picture jat001  路  4Comments