The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, coverallsapp/github-action@master. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The variable 'testCommandPrefix' is assigned but its value is never used

Theory method 'SendHelpMessage_MixedParameters_ShouldSendMessage' on test class 'SubCommandBaseTests' does not use parameter 'expectedCallExample'. Use the parameter, or remove the parameter and associated data. (https://xunit.net/xunit.analyzers/rules/xUnit1026)

Theory method 'SendHelpMessage_StringValidValuesHelpMessage_ShouldSendMessage' on test class 'SubCommandBaseTests' does not use parameter 'expectedCallExample'. Use the parameter, or remove the parameter and associated data. (https://xunit.net/xunit.analyzers/rules/xUnit1026)

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.

The variable 'isLoadedPlayerChildSlave' is assigned but its value is never used

Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

The variable 'isLoadedPlayerChildSlave' is assigned but its value is never used

The variable 'testCommandPrefix' is assigned but its value is never used

Theory method 'SendHelpMessage_MixedParameters_ShouldSendMessage' on test class 'SubCommandBaseTests' does not use parameter 'expectedCallExample'. Use the parameter, or remove the parameter and associated data. (https://xunit.net/xunit.analyzers/rules/xUnit1026)

Theory method 'SendHelpMessage_StringValidValuesHelpMessage_ShouldSendMessage' on test class 'SubCommandBaseTests' does not use parameter 'expectedCallExample'. Use the parameter, or remove the parameter and associated data. (https://xunit.net/xunit.analyzers/rules/xUnit1026)