Documentation

Code Smith

Scan FiveM resources for loop abuse, missing waits, and asset clutter.

Code Smith scans a zipped FiveM resource and reports common scripting issues that cause server performance problems.

What it detects

Tight loops with no Wait() call — the most common cause of server thread starvation.
Heavy event handlers that execute expensive logic on every tick.
Missing Citizens.CreateThread wrappers around async-pattern code.
Unused asset references (models registered but never requested).
Deprecated natives still present in the codebase.

Code Smith is a static analyser — it cannot catch runtime bugs or logic errors, only known anti-patterns.

Workflow

1Zip your FiveM resource folder (must include fxmanifest.lua at root).
2Drop the ZIP onto Code Smith.
3Review the report — each finding shows the file, line, and a description.
4Fix the flagged issues, re-zip, and re-scan to confirm.

Open Code Smith and start building

Frequently asked questions

What issues does Code Smith detect?

Performance anti-patterns in a zipped resource — tight loops with no Wait() call, heavy per-tick event handlers, missing CreateThread wrappers, unused asset references, and deprecated natives.

Will Code Smith find every bug in my resource?

No — it's a static analyser, so it catches known anti-patterns, not runtime bugs or logic errors. Use it to clear common performance problems, then test in-game.

What do I upload to Code Smith?

A ZIP of your FiveM resource folder with fxmanifest.lua at the root. Drop it in and each finding shows the file, line, and a description.

How does it help server performance?

The most common cause of server thread starvation is a loop with no Wait() — Code Smith flags those and other heavy patterns so you can fix them before they cause lag.

Discussion