Something unexpectedly tried to set the parent of X to NULL

What the message means

Something unexpectedly tried to set the parent of Sword to NULL while trying to set the parent of Sword. Current parent is Backpack.

Other forms of the same message:

• Something unexpectedly tried to set the parent of Builderman to NULL while trying to set the parent of Builderman. Current parent is Workspace.

NULL is the engine's word for nil: the second move was trying to remove the object (Parent = nil, which is what Destroy does). The last part, Current parent is ..., is where the object is now.

The first move still happens; only the one made from inside the handler is refused. So the object ends up somewhere you did not expect, such as a tool staying in the Backpack.

Places whose Workspace.SignalBehavior is Deferred run event handlers a moment after the change instead of during it, so they hit this less often. The fixes below work with either setting.

Causes and fixes

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

• A ChildAdded handler destroys or moves the new child
• An AncestryChanged handler puts the object back
• The character is moved or destroyed while it spawns

A ChildAdded handler destroys or moves the new child

A cleanup script that removes anything placed in a folder runs while Roblox is still parenting it.

local Players = game:GetService("Players")

Players.PlayerAdded:Connect(function(player)
	local backpack = player:WaitForChild("Backpack")
	backpack.ChildAdded:Connect(function(tool)
		if tool.Name == "BannedTool" then
			tool:Destroy() -- while it is still being parented: the warning
		end
	end)
end)

Let the first move finish, then act, with task.defer.

local Players = game:GetService("Players")

Players.PlayerAdded:Connect(function(player: Player)
	local backpack = player:WaitForChild("Backpack")
	backpack.ChildAdded:Connect(function(tool: Instance)
		if tool.Name == "BannedTool" then
			task.defer(function()
				tool:Destroy()
			end)
		end
	end)
end)

An AncestryChanged handler puts the object back

A script that keeps a part from being removed (by setting its Parent back when it changes) fights the move that triggered it.

local flag = workspace:WaitForChild("Flag")

flag.AncestryChanged:Connect(function(_, parent)
	if parent == nil then
		flag.Parent = workspace -- during the removal: the warning
	end
end)

Defer the move. Better, keep a copy and clone it back, which also works after Destroy (a destroyed object cannot be parented again).

local flag = workspace:WaitForChild("Flag")
local template = flag:Clone()

local function watch(current: Instance)
	current.AncestryChanged:Connect(function(_, parent)
		if parent == nil then
			task.defer(function()
				local fresh = template:Clone()
				fresh.Parent = workspace
				watch(fresh)
			end)
		end
	end)
end

watch(flag)

The character is moved or destroyed while it spawns

Code on CharacterAdded that parents the character somewhere else, or destroys the old one at the same moment Roblox is placing it, gets refused, often with the player name in the message.

local Players = game:GetService("Players")

local lobby = workspace:WaitForChild("Lobby")

Players.PlayerAdded:Connect(function(player)
	player.CharacterAdded:Connect(function(character)
		character.Parent = lobby -- Roblox is still parenting it to Workspace
	end)
end)

Wait until the character is in Workspace, then move it, or move the character with PivotTo instead of reparenting it.

local Players = game:GetService("Players")

local lobbySpawn = workspace:WaitForChild("LobbySpawn") :: BasePart

Players.PlayerAdded:Connect(function(player: Player)
	player.CharacterAdded:Connect(function(character: Model)
		if not character:IsDescendantOf(workspace) then
			character.AncestryChanged:Wait()
		end
		task.defer(function()
			character:PivotTo(lobbySpawn.CFrame + Vector3.new(0, 4, 0))
		end)
	end)
end)

How to find the line that causes it

1. The warning does not name a script. Use the object name in it (Sword, a player name) and search your scripts for handlers that react to that object moving: Ctrl+Shift+F and search for ChildAdded, AncestryChanged, DescendantAdded and Equipped.
2. In each handler, look for .Parent = or :Destroy() on the object the event gave you.
3. Wrap that line in task.defer and test again. If the warning is gone, that was the one.

Questions

Sources and further reading

• Roblox Creator Docs: Instance.Parent
• Roblox Creator Docs: Instance:Destroy. a destroyed object cannot be parented again
• Roblox Creator Docs: task.defer

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