Well, I'm -sloooowly- working on a shell/GUI for ASF's WCF mode, i've thought some useful properties to extend the existing getStatus() command (!api):
Property: /Bots/\
Source: BotConfig.FarmingOrder
Use: The external app can show the bot's selected farming algorithm. Could possibly be paired with my other suggestion here #368.
Property: /Bots/\
Source: BotConfig.IsBotAccount
Uses: The external app can show or hide bots from display, while keeping master account visible. Also, statistics can be broken down to a "master+bots" design where master's data would be verbose and bots' data would be more compact (summarized).
Property: /Bots/\
Source: SteamClient.SteamID ❓
Uses: The app can use steamID64 to retrieve bot's avatar easily. It's useful to link to bot's profile page or subpages (wishlist) or even retrieve and parse bot's game list -assuming the app also has an API key.
The first two are dead easy for you to include, i guess. While both properties can be retrieved from bot's .config file, this eliminates the need for the external app to read (and mess with) ASF's files. The third property might be a bit complicated but highly useful since id64 cannot be retrieved without a third party API, afaik.
What do you think of them? 😀
I don't have anything against those 3 extra properties, why not. I'll probably add them soon.
Most helpful comment
I don't have anything against those 3 extra properties, why not. I'll probably add them soon.