All TShock methods calling the obsolete ForceKick function now use the new one
Subnote: fixes an issue where players would be reported as kicked to the ingame console.
This commit is contained in:
parent
ca5d68b838
commit
8ecabb7f2e
4 changed files with 9 additions and 9 deletions
|
|
@ -672,7 +672,7 @@ namespace TShockAPI
|
|||
|
||||
if (Utils.ActivePlayers() + 1 > Config.MaxSlots + 20)
|
||||
{
|
||||
Utils.ForceKick(player, Config.ServerFullNoReservedReason);
|
||||
Utils.ForceKick(player, Config.ServerFullNoReservedReason, true, false);
|
||||
handler.Handled = true;
|
||||
return;
|
||||
}
|
||||
|
|
@ -684,14 +684,14 @@ namespace TShockAPI
|
|||
|
||||
if (ban != null)
|
||||
{
|
||||
Utils.ForceKick(player, string.Format("You are banned: {0}", ban.Reason));
|
||||
Utils.ForceKick(player, string.Format("You are banned: {0}", ban.Reason), true, false);
|
||||
handler.Handled = true;
|
||||
return;
|
||||
}
|
||||
|
||||
if (!FileTools.OnWhitelist(player.IP))
|
||||
{
|
||||
Utils.ForceKick(player, Config.WhitelistKickReason);
|
||||
Utils.ForceKick(player, Config.WhitelistKickReason, true, false);
|
||||
handler.Handled = true;
|
||||
return;
|
||||
}
|
||||
|
|
@ -704,7 +704,7 @@ namespace TShockAPI
|
|||
{
|
||||
if (Config.KickProxyUsers)
|
||||
{
|
||||
Utils.ForceKick(player, "Proxies are not allowed");
|
||||
Utils.ForceKick(player, "Proxies are not allowed.", true, false);
|
||||
handler.Handled = true;
|
||||
return;
|
||||
}
|
||||
|
|
@ -737,7 +737,7 @@ namespace TShockAPI
|
|||
|
||||
if (ban != null)
|
||||
{
|
||||
Utils.ForceKick(player, string.Format("You are banned: {0}", ban.Reason));
|
||||
Utils.ForceKick(player, string.Format("You are banned: {0}", ban.Reason), true, false);
|
||||
handler.Handled = true;
|
||||
return;
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue