ArchiSteamFarm V2.1
Pre-releaseNOTICE: Pre-releases are experimental versions that often contain unpatched bugs, work-in-progress features or rewritten implementations. If you don't consider yourself advanced user, please download latest stable release instead. Pre-release versions are dedicated to users who know how to report bugs, deal with issues and give feedback. No technical support will be given.
PLEASE MAKE BACKUPS
ArchiSteamFarm V2.1
After a little over 3 months since last V2.0 release, there is another major ASF version ready - 2.1, which contains some crucial changes.
Before updating, I strongly recommend to create a backup of your ASF. While everything should work out of the box (as usual), this release contains breaking change that will modify existing structure and break backwards compatibility. It's always a good idea to make a backup every once in a while as well.
ASF 2FA rewrite
When ASF 2FA was firstly introduced, the whole 2FA concept was rather new and older users of ASF can still remember that not everything worked right away. Now the time has come to end old ASF 2FA "v1" and introduce new ASF 2FA "v2". The major difference between those two versions is the fact that old ASF 2FA was purely based on SteamAuth module written by developers of SteamDesktopAuthenticator. It works quite decent, but has it's own limitations such as not being SteamParental-friendly, running into unhandled steam issues and having rather poor "ASAP" implementation that comes from nearly half a year back when we all needed something that works.
Unfortunately it seems that developers more or less abandoned the library, therefore I decided to drop it and write my own ASF-integrated 2FA module that includes the same functionality, done in much better, faster, smarter and error-aware optimized way. While previous library was more "universal" and worked with nearly all 2FA features, current one is ASF-centered and provides the functionality that ASF needs, rather than being general-purpose for SDA or WinAuth programs. It's still in somehow beta stage, but it already works much better than the old implementation, and will benefit ASF in long-run.
Some important changes include:
- [!] Incompatibility with previous versions of ASF - Bot's database will be converted from old V1 into new V2 format, which means that newly generated Bot's database will not run correctly with previous versions of ASF.
- [!] Removed support for linking new authenticator and delinking existing ones, effectively removing
UseAsfAsMobileAuthenticator
Bot config property and!2faoff
command. - Added support for SteamParental in 2FA sessions. New ASF 2FA uses existing ASF mechanism of
SteamParentalPIN
to unlock and operate on such accounts, no action is needed. - Improved security of ASF 2FA - 2FA module will now only accept confirmations ASF directly creates, and not all of them.
!2faok
command is not affected and still accepts everything. - Many internal optimizations, bugfixes, improvements and general code review of ASF 2FA.
Point 2 is most important - until now ASF 2FA could potentially work in "solo" mode, called ASF 2FA (only) which was possible to achieve with UseAsfAsMobileAuthenticator
and linking new authenticator. That mode is no longer available, and you're expected to link your authenticator firstly in either SDA or WinAuth. This is a security measure followed by the fact that ASF 2FA is a module designed for ASF, and not general-purpose authenticator. Every already linked authenticator will remain active and work properly, but if you used ASF 2FA "solo" mode, you're strongly encouraged to re-add your authenticator to SDA or WinAuth and keep a copy there, in addition to using it in ASF 2FA. This is more convenient for both you as an user, and me as a developer, because ASF instead of implementing extra unneeded features can focus on remaining compatible with SDA and WinAuth, working with their data and ensuring that you have a backup plan in case something goes wrong.
.NET 4.6.1
Until now ASF was targetting .NET 4.5.1 framework, this was mainly because latest stable Mono version was 4.2 and it didn't support any more recent framework version. Things have changed, as Mono devs recently released version 4.4, which supports latest .NET framework 4.6.1, therefore ASF from now on uses this version as both compile environment and runtime.
Majority of users should be unaffected. Make sure you're using latest .NET on Windows, and latest Mono (4.4+) with other OSes.
Latest .NET framework ensures that ASF apart from using recently added features, can operate in better environment, which should improve things such as performance or memory usage.
Apart from major changes above, usual changelog:
- Massive portion of code improvements, optimizations and bugfixes.
ASF is available for free. If you're grateful for what we're doing, please consider donating. Developing ASF requires massive amount of time and knowledge, especially when it comes to Steam. Even smallest amount is highly appreciated!