<name> does not have a resource manifest
A folder in your resources is missing the file that tells the server what it is. Almost always the zip was unpacked one level too deep.
Do this first
Open the folder. If the only thing inside is ANOTHER folder with the same name, move its contents up one level.
What it means
The server found a folder where a resource should be and there is no fxmanifest.lua at its root. Without a manifest the folder is not a resource, so nothing in it can start.
What causes it
Ordered by how often it is the answer.
- 1
The zip was unpacked one level too deep
The classic.
resources/my-script/my-script/fxmanifest.lua— the outer folder is what the server looks at, and it contains only another folder. - 2
The file is named __resource.lua
The pre-2019 name. Modern builds still read it in some cases but many checks look for fxmanifest.lua specifically.
- 3
The file is fxmanifest.lua.txt
Windows hiding known extensions, and the file was created from a text editor.
- 4
It is not a resource folder at all
A stray folder inside
resources/— a backup, a downloaded zip, a.gitdirectory.
How to tell which one is yours
Look inside the folder the message names. If the only thing in it is another folder with the same name, it is cause 1 and it takes ten seconds to fix.
Where to look
resources/<name>/ — the manifest must be directly in there, not in a subfolder.
How to fix it
Move the inner folder's contents up one level so the layout is:
resources/
my-script/
fxmanifest.lua
client/
server/Still stuck on your own code?
This page is what this error usually means. Paste your console into Server Fixer and it will rank everything in it and tell you what to do first, and if you would rather not touch it, ORBIE can repair the script and hand the resource back ready to drop in.
bug_reportOpen Server Fixer