From 9703336e81f8c776de691a7e965e97e81a617870 Mon Sep 17 00:00:00 2001 From: JustArchi Date: Mon, 13 Apr 2020 13:39:22 +0200 Subject: [PATCH] Update ExamplePlugin.cs --- ArchiSteamFarm.CustomPlugins.ExamplePlugin/ExamplePlugin.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ArchiSteamFarm.CustomPlugins.ExamplePlugin/ExamplePlugin.cs b/ArchiSteamFarm.CustomPlugins.ExamplePlugin/ExamplePlugin.cs index a276745ba..56c9f85f6 100644 --- a/ArchiSteamFarm.CustomPlugins.ExamplePlugin/ExamplePlugin.cs +++ b/ArchiSteamFarm.CustomPlugins.ExamplePlugin/ExamplePlugin.cs @@ -139,7 +139,7 @@ namespace ArchiSteamFarm.CustomPlugins.ExamplePlugin { // You can use either ASF's default functions for that, or implement your own logic as you please // If you do not intend to return any response to user, just return null/empty and ASF will proceed with the silence as usual public Task OnBotMessage(Bot bot, ulong steamID, string message) { - // Normally ASF will expect from you async-capable responses, such as Task. This allows you to make your code fully asynchronous which is a core fundament on which ASF is built upon + // Normally ASF will expect from you async-capable responses, such as Task. This allows you to make your code fully asynchronous which is a core foundation on which ASF is built upon // Since in this method we're not doing any async stuff, instead of defining this method as async (pointless), we just need to wrap our responses in Task.FromResult<>() // As a starter, we can for example ignore messages sent from our own bots, since otherwise they can run into a possible infinite loop of answering themselves