How To Fix “Modded Client Rejected” Errors on Your Schedule 1 Server

Note:

When a player attempts to connect to your Schedule 1 dedicated server, they may receive a “Modded Client Rejected” error message on their screen and get disconnected. This happens when the client-side mods installed on the player’s computer violate the server’s mod access rules configured in client_mod_policy.toml.

1. Log In to Your Panel

---

2. Select the ‘Console’ Tab

---

3. Check Console Logs for the Rejected Mod ID

Select the Console tab from the left sidebar navigation menu. Have the affected player attempt to connect to the server again, and watch the live console log output.

Look for a rejection log entry similar to the following:

[ClientModPolicy] Rejected connection from PlayerName (76561198000000000)
[ClientModPolicy] Reason: Mod 'InfiniteMoneyMod' is not permitted by server policy.

Take note of the exact mod ID or assembly name listed in the rejection log

---

4. Stop Your Server

---

5. Select the ‘File’ Tab

---

6. Select the ‘User Data’ Folder

---

7. Select the ‘client_mod_policy.toml‘ File

---

8. Option A: Allow the Rejected Mod (Whitelist)

If the rejected mod is a harmless Quality-of-Life (QoL) mod, add its exact mod ID to the allowed array under [whitelisted_mods]:

[whitelisted_mods]
allowed = [
    "QoL_Minimap",
    "InfiniteMoneyMod"
]

---

8. Option B: Relax Global Mod Restrictions

If default_action is set to "BlockAll" or "RequireMatching", change it to "AllowAll" to permit client mods by default:

[policy]
default_action = "AllowAll"

Note on RequireMatching: If default_action = "RequireMatching", players will be rejected if their local client mods do not match the server’s mod list line-for-line. Switching this to "AllowAll" or "BlockAll" relaxes strict file-hash checking.

---

9. Save the Configuration

---

10. Restart Your Server

Schedule 1 Server Hosting

Starts at $9.99

Was this article helpful?

0 0

Please Share Your Feedback

How Can We Improve This Article?

Submit