Archisteamfarm: Add region selection for connecting to steam

[legionpheonix]

I have a firewall block everything.
I personally define to which IP: port domain outgoing / incoming traffic.
Please add the ability to select a region for steam, so that the program immediately tries to connect the IP of my region steam.
If the ArchiSteamFarm program is activated when it is blocked, then it starts searching in order all possible regions.
Or tell me where / in which configuration file this can be done?

[JustArchi]

Please add the ability to select a region for steam, so that the program immediately tries to connect the IP of my region steam.

ASF automatically will prefer to use region of your machine and connect to the closest CM server available. It's not planned to modify this behaviour, as you should never want to change this, in the same way how Steam client does not allow you to have any say in this either. In other words, already possible, and not configurable.

Or tell me where / in which configuration file this can be done?

It's not expected use case to have permanent block on outgoing traffic. IPs of Steam servers can change at any given point of time and you can't hand-pick the server ASF connects to, as ASF will always ask Steam network for list of servers first, then choose the best one. Like stated above, it's not planned to ever add such functionality, as ASF should non-negotiably follow Steam client behaviour in this aspect.

If you want to get a list of all current servers that ASF can try to connect with, then you can execute curl https://api.steampowered.com/ISteamDirectory/GetCMList/v1?cellid=0 from the same machine in order to get IP-personalized list of servers. Afterwards you should either start fresh ASF or remove ASF.db manually, let ASF pick the server and establish connection, after which ASF will cache the list of servers to use in ASF.db, together with CellID that is assigned to this IP.

At this point you can purge your previous list of IPs, cat ASF.db and add all fully-personalized servers that ASF keeps in its cache, which should be very similar to the one with ?cellID=0, but has a potential to be even more accurate than just an IP check. Just like I said, IPs, servers and all settings can change at any given point of time, so it's you ensuring that ASF can connect with the servers that it saved, and it's also you ensuring that any updates to that list are handled by your firewall. If you can't make it happen and you depend on ASF connecting with one particular IP of your choice then this goes against expected Steam client behaviour, therefore won't be implemented by ASF and you should either fork ASF and add such feature yourself, or adapt your environment to match expected ASF use case.