Expected <eof>, got 'end'

What the message means

ServerScriptService.Door:9: Expected <eof>, got 'end'

Other forms of the same message:

• Expected <eof>, got 'else'
• Expected <eof>, got 'elseif'

This is the opposite of Expected 'end' (to close ...), where an end is missing. Here every block is already closed and an extra one remains.

The line number is where the extra end is. But the block it was meant for may be higher up, where an end was put too early.

Causes and fixes

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

• An end before else or elseif
• An extra end after a function
• A leftover end after end)

An end before else or elseif

An if has one end, after its last branch. Putting an end after each branch closes the if early, and the else that follows has nothing to belong to, so Luau reports it (here got 'else') or the extra end after it.

local coins = 50

if coins >= 100 then
	print("rich")
elseif coins >= 50 then
	print("ok")
end
else
	print("poor")
end

Write the whole chain as one block: if, any number of elseif, an optional else, then one end.

local coins = 50

if coins >= 100 then
	print("rich")
elseif coins >= 50 then
	print("ok")
else
	print("poor")
end

An extra end after a function

Copying a block in or deleting an if leaves its end behind.

local function openDoor(door)
	door.Transparency = 0.5
	door.CanCollide = false
end
end

Delete the extra end. Indentation shows which block each end closes.

local function openDoor(door: BasePart)
	door.Transparency = 0.5
	door.CanCollide = false
end

print(openDoor)

A leftover end after end)

An event connection closes with end). Adding a plain end under it, out of habit or after moving code around, is one too many.

local pad = script.Parent

pad.Touched:Connect(function(hit)
	print(hit.Name)
end)
end

Delete the extra end: end) already closes both the function and the Connect( call.

local pad = script.Parent :: BasePart

pad.Touched:Connect(function(hit: BasePart)
	print(hit.Name)
end)

How to find the line that causes it

1. A syntax error stops the whole script before its first line runs, so nothing in that script works, not just the broken line.
2. Open the script. The Script Editor underlines the problem in red; hover over the underline to read the message.
3. Open Script Analysis (View tab) to see every syntax error in every script, with its line number. Double-click one to jump to it.
4. The line number in the message is where Luau gave up, which is often below the real mistake. The (to close ... at line N) part points at the line where the unclosed bracket or block starts.

Questions

Sources and further reading

• Luau: syntax
• Roblox Creator Docs: control structures. if, elseif and else
• Roblox Creator Docs: Script Editor

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 only to fail with the message on this page. The message wording was checked by compiling each broken block on this page with luau-compile, which uses the same Luau parser as Roblox Studio, on 23 October 2026. A type check catches misspelt APIs and wrong types, not game logic, so playtest in Studio before you publish.