diff --git a/Class/Player.cs b/Class/Player.cs
index 7d85637..0ccd2d8 100644
--- a/Class/Player.cs
+++ b/Class/Player.cs
@@ -13,7 +13,7 @@ public class Player
         public int Damage { get; set; }
 
         // KDA Ratio: (Kills + Assists) / Deaths
-        public float KDA => Deaths == 0 ? Kills : (float)(Kills) / Deaths;
+        public float KDA => Deaths == 0 ? Kills : (float)Kills / Deaths;
 
         // Performance score based on KDA, Damage, and Score
         public float PerformanceScore => KDA * 0.5f + Damage * 0.3f + Score * 0.2f;
diff --git a/Config/Config.cs b/Config/Config.cs
index beffffe..a9d6c1d 100644
--- a/Config/Config.cs
+++ b/Config/Config.cs
@@ -74,10 +74,18 @@ private static void GenerateDefaultConfigFile(string configPath)
                     .AppendLine("score_balance_ratio = 1.6")
                     .AppendLine()
                     .AppendLine("# Whether to use PerformanceScore for balancing.")
+                    .AppendLine("# PerformanceScore is a custom metric that considers KDA (Kills, Deaths, Assists),")
+                    .AppendLine("# damage dealt, and the in-game score to evaluate a player's overall performance.")
+                    .AppendLine("# If set to true, the balance algorithm will use PerformanceScore to evaluate ")
+                    .AppendLine("# players when balancing teams, rather than just the in-game score.")
                     .AppendLine("# Default: true")
                     .AppendLine("use_performance_score = true")
                     .AppendLine()
                     .AppendLine("# Maximum allowed difference in team sizes.")
+                    .AppendLine("# This setting controls how much the team sizes are allowed to differ after balancing.")
+                    .AppendLine("# If set to 1, the algorithm will attempt to ensure that the difference in the number ")
+                    .AppendLine("# of players between the teams is no more than one. This helps prevent one team from")
+                    .AppendLine("# having a significant numerical advantage over the other.")
                     .AppendLine("# Default: 1")
                     .AppendLine("max_team_size_difference = 1");
 
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..9aece93
--- /dev/null
+++ b/README.md
@@ -0,0 +1,89 @@
+# Mesharsky Team Balance Plugin
+
+This plugin is designed to ensure fair and balanced gameplay by intelligently managing team sizes and performance metrics. It's highly configurable to suit the needs of any server.
+
+## Features
+
+- **Intelligent Team Balancing**: Automatically balances teams based on player performance metrics (Kills, Deaths, Damage, and Score).
+- **Configurable Settings**: Fine-tune the balancing behavior with various configuration options.
+- **Performance-Based**: Optionally use a custom `PerformanceScore` to evaluate players and create fairer teams.
+- **Team Size Control**: Ensures the difference in team sizes is kept to a minimum.
+
+## Installation
+
+1. **Download the Plugin**: Clone this repository or download the plugin files directly.
+2. **Upload plugin to your counterstrikesharp folder**: Place the plugin folder inside counterstrikesharp folder. Standard installation.
+3. **Configure the Plugin**: Edit the `TeamBalance.toml` file to adjust the settings according to your server's needs (see below for details).
+4. **Restart Your Server**: Restart the server to load the plugin with your customized settings.
+
+## Configuration
+
+The plugin comes with a configuration file, `TeamBalance.toml`, that allows you to customize its behavior. Below is a detailed explanation of each setting. (Configuration file is inside Module Directory)
+
+```toml
+# Plugin Author - Mesharsky
+# https://csowicze.pl/
+
+# Team Balance Plugin Configuration
+# Make sure to adjust these settings according to your server's needs.
+
+[PluginSettings]
+# The minimum number of players required on the server before the team balance
+# feature activates. This prevents balancing when there are too few players.
+# Default: 4
+minimum_players = 4
+
+# The maximum allowed ratio of scores between teams before triggering a balance.
+# For example, if set to 1.6, the balance will trigger if one team's score is
+# 60% higher than the other team's score. Adjust this value based on how strict
+# you want the balancing to be.
+# Default: 1.6
+score_balance_ratio = 1.6
+
+# Whether to use PerformanceScore for balancing.
+# PerformanceScore is a custom metric that considers KDA (Kills, Deaths, Assists),
+# damage dealt, and the in-game score to evaluate a player's overall performance.
+# If set to true, the balance algorithm will use PerformanceScore to evaluate 
+# players when balancing teams, rather than just the in-game score.
+# Default: true
+use_performance_score = true
+
+# Maximum allowed difference in team sizes.
+# This setting controls how much the team sizes are allowed to differ after balancing.
+# If set to 1, the algorithm will attempt to ensure that the difference in the number 
+# of players between the teams is no more than one. This helps prevent one team from
+# having a significant numerical advantage over the other.
+# Default: 1
+max_team_size_difference = 1
+```
+### Key Settings Explained
+- **`minimum_players`**: The minimum number of players required before the plugin activates. This ensures that balancing doesn't occur when there are too few players to make meaningful adjustments.
+- **`score_balance_ratio`**: Controls the ratio of scores between teams that will trigger a rebalance. For example, a ratio of 1.6 means that if one team’s score is 60% higher than the other’s, a balance will be triggered.
+- **`use_performance_score`**: When enabled, the plugin uses a custom `PerformanceScore` metric (based on KDA, damage, and score) to determine player value during balancing. This typically results in more effective balancing than using the in-game score alone.
+- **`max_team_size_difference`**: Ensures that the team sizes differ by no more than this value after balancing, helping to prevent one team from having a significant player advantage.
+
+### How It Works
+
+1. **Player Stats Collection**: At the start of each round, the plugin collects stats for each player (Kills, Deaths, Damage, Score) and stores them in a cache.
+2. **Balance Check**: The plugin checks whether teams need to be rebalanced based on player count and score ratios.
+3. **Team Balancing**:
+   - If balancing is required, players are evaluated based on their `PerformanceScore` (or in-game score if `use_performance_score` is disabled).
+   - The plugin attempts to distribute players between teams to minimize the score difference while respecting the `max_team_size_difference`.
+   - Only players who need to be moved are affected; those already on the correct team are left in place.
+4. **Feedback**: If a balance is made, players are notified via in-game chat, ensuring transparency.
+
+### Example Scenarios
+
+#### Scenario 1: Uneven Team Sizes
+- **Input**: 10 players on the Terrorist team, 1 player on the Counter-Terrorist team.
+- **Result**: The plugin will move players from the Terrorist team to the Counter-Terrorist team until the difference in team sizes is within the allowed range (defined by `max_team_size_difference`).
+
+#### Scenario 2: High Score Disparity
+- **Input**: Terrorist team has a score that is 70% higher than the Counter-Terrorist team.
+- **Result**: The plugin will trigger a rebalance, moving top-performing players from the Terrorist team to the Counter-Terrorist team to even out the scores.
+
+### Development
+This plugin was developed by Mesharsky. Contributions, issues, and suggestions are welcome! Feel free to open a pull request or issue on GitHub.
+
+### License
+This project is licensed under the MIT License - see the LICENSE file for details.
diff --git a/TeamBalance.toml b/TeamBalance.toml
index a86445c..c5e43e0 100644
--- a/TeamBalance.toml
+++ b/TeamBalance.toml
@@ -18,9 +18,17 @@ minimum_players = 4
 score_balance_ratio = 1.6
 
 # Whether to use PerformanceScore for balancing.
+# PerformanceScore is a custom metric that considers KDA (Kills, Deaths, Assists),
+# damage dealt, and the in-game score to evaluate a player's overall performance.
+# If set to true, the balance algorithm will use PerformanceScore to evaluate 
+# players when balancing teams, rather than just the in-game score.
 # Default: true
 use_performance_score = true
 
 # Maximum allowed difference in team sizes.
+# This setting controls how much the team sizes are allowed to differ after balancing.
+# If set to 1, the algorithm will attempt to ensure that the difference in the number 
+# of players between the teams is no more than one. This helps prevent one team from
+# having a significant numerical advantage over the other.
 # Default: 1
 max_team_size_difference = 1