Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Non-nullable property 'userName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'userId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'CharacterName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'JobPrototype' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Player' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'MostSeenPlayers' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'MostAntagPlayers' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'MostHuntedPlayer' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Map' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Gamemode' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Url' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Provider' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Nullability of reference types in type of parameter 'state' of 'void DataController.CheckInactiveConnections(object state)' doesn't match the target delegate 'TimerCallback' (possibly because of nullability attributes).

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.

Possible null reference assignment.

Possible null reference assignment.

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 'e' is declared but 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.