Cannot kick a non-local Player from a LocalScript

What the message means

Players.Builderman.PlayerGui.AdminPanel.KickButton.LocalScript:9: Cannot kick a non-local Player from a LocalScript

If a LocalScript could kick anyone, any player running a cheat could empty your server, because a cheater controls every LocalScript on their own device. So Roblox only lets a client remove itself.

Kicking yourself from a LocalScript is allowed and sometimes useful, for example after a client-side check fails, but it only ever affects the device the script runs on.

Causes and fixes

Three things cause this error in practice. Each one below has the smallest code that triggers it, then the fix.

• An admin button kicks the target from its LocalScript
• A client-side check kicks other players
• A ModuleScript that kicks is required from a LocalScript

An admin button kicks the target from its LocalScript

GUI buttons run LocalScripts, so the click handler is on the client. Finding the target with Players:FindFirstChild(name) works there, but Kick on that player does not.

local Players = game:GetService("Players")

local button = script.Parent :: TextButton
local nameBox = button.Parent:WaitForChild("NameBox") :: TextBox

button.Activated:Connect(function()
	local target = Players:FindFirstChild(nameBox.Text)
	if target and target:IsA("Player") then
		-- Cannot kick a non-local Player from a LocalScript
		target:Kick("Kicked by an admin")
	end
end)

Move the kick to a server Script. The button's LocalScript only asks, with kickRequest:FireServer(nameBox.Text) on a RemoteEvent named KickRequest in ReplicatedStorage. The server checks who is asking against a list it keeps itself, checks the type of what was sent, and only then kicks. Without that check any player could fire the remote and kick anyone, because RemoteEvents in ReplicatedStorage are visible to every client.

local Players = game:GetService("Players")
local ReplicatedStorage = game:GetService("ReplicatedStorage")

local kickRequest = ReplicatedStorage:WaitForChild("KickRequest") :: RemoteEvent

-- UserIds allowed to kick. Kept on the server, where players cannot read or change it.
local ADMINS: { [number]: boolean } = {
	[156] = true,
}

kickRequest.OnServerEvent:Connect(function(sender: Player, targetName: unknown)
	if not ADMINS[sender.UserId] then
		return
	end
	if typeof(targetName) ~= "string" then
		return
	end
	local target = Players:FindFirstChild(targetName)
	if target and target:IsA("Player") and target ~= sender then
		target:Kick("You were removed by an admin.")
	end
end)

Put your own UserId in ADMINS (it is the number in the address of your Roblox profile page). The admin panel guide builds a full panel with ranks, kick and BanAsync, and the RemoteEvents guide explains the checks.

A client-side check kicks other players

A LocalScript that watches every player, for example a speed check or a ban list, and kicks the ones it does not like, runs into the same rule. It would also be easy to switch off, since it runs on a device the player controls.

local Players = game:GetService("Players")

local BANNED_NAMES = { "SomeRuleBreaker" }

Players.PlayerAdded:Connect(function(player: Player)
	if table.find(BANNED_NAMES, player.Name) then
		-- Cannot kick a non-local Player from a LocalScript
		player:Kick("You are banned from this game.")
	end
end)

Run checks like this in a server Script, and check UserIds rather than names, because players can change their name.

local Players = game:GetService("Players")

local BANNED_USER_IDS: { [number]: boolean } = {
	[123456789] = true,
}

Players.PlayerAdded:Connect(function(player: Player)
	if BANNED_USER_IDS[player.UserId] then
		player:Kick("You are banned from this game.")
	end
end)

For bans that last across servers, Players:BanAsync on the server stores the ban for you, as the admin panel guide shows.

A ModuleScript that kicks is required from a LocalScript

A ModuleScript runs wherever it is required. The same moderation module that works from a server Script fails when a LocalScript requires it and calls its kick function.

local Moderation = {}

function Moderation.remove(player: Player, reason: string)
	-- fine from a server Script; from a LocalScript, for anyone but LocalPlayer:
	-- Cannot kick a non-local Player from a LocalScript
	player:Kick(reason)
end

return Moderation

Keep moderation modules in ServerScriptService or ServerStorage, where LocalScripts cannot require them, and call them only from server Scripts.

local Moderation = {}

-- Lives in ServerScriptService, so only server Scripts can require it
function Moderation.remove(player: Player, reason: string)
	player:Kick(reason)
end

return Moderation

How to find the line that causes it

1. The path in the message names the LocalScript, often inside PlayerGui, which is where StarterGui's scripts run during play.
2. Click the line in Output to open it at the Kick call, then move that call to a server Script as shown above.

Questions

Sources and further reading

• Roblox Creator Docs: Player:Kick. kicking from the server and the local player from the client
• Roblox Creator Docs: Players:BanAsync
• Roblox Creator Docs: Securing the client-server boundary. never trusting what a client sends

How the code was checked: every block marked Fixed passes Luau's strict type checker against Roblox's API definitions (luau-lsp, 5 November 2026), and every block marked Breaks compiles and fails only when it runs. The message wording was checked against the message strings in Roblox Studio itself (macOS build installed 2 November 2026) and the Player:Kick reference on 5 November 2026. A type check catches misspelt APIs and wrong types, not game logic, so playtest in Studio before you publish.