Łukasz Domeradzki

https://ptb.discord.com/channels/267292556709068800/332735075315744768/859854787634004049

ref: https://github.com/JustArchiNET/ArchiSteamFarm/issues/2344

Initial idea of ASF API response: Two `Dictionary` fields from each plugin, one for ASF config and one for Bot config. Each entry in a dictionary would be name of...

Good idea actually, there can be plugins view and in that view, optionally, each plugin can list its additional dependencies, like extra config properties. Much more robust than just dedicated...

Our latest discussion with @Aareksio resulted in a bit different approach: Instead of any additional API endpoint, plugins can tag schemas in `swagger.json`, and ASF-ui will know that it needs...

(API endpoint for discovering currently-loaded plugins is still a fine idea, but something entirely different than what we're doing in this issue, and that one indeed needs a standalone API...

Alternatively, and probably the easiest way implementation-wise, maybe SEE could just retry the failed requests automatically after being done with the current queue? You could use a pseudocode like this...

Thanks for your answer @Eilon, I appreciate it. > Hosting a local web server in a cross-platform app is something reasonable (though perhaps not super common), so it's worth considering....

https://github.com/JustArchi/ArchiSteamFarm/blob/master/ArchiSteamFarm/Bot.cs#L246

Just wanted to confirm this issue. `status` expects `int`, while it should be `int?`.