The FiveTrace SDK
One resource, two lines in your manifest. It captures unhandled Lua errors and sends the log lines your scripts write, and it is the same file for both products.
current version 0.2.0 · MIT · runs on Lua 5.3 and 5.4
Four short steps, and they differ by which product you are here for, so they are written once in the docs for that half rather than a second time on this page. An install written in two places is an install that disagrees with itself the first time one of them changes, and the copy nobody is reading is the one that goes stale.
Live logs: a log key in server.cfg, and the SDK loaded into the resources you want lines from. For the server you run.
Error tracking: a DSN and one init call, inside the script you sell. For the servers you never see.
Selling a script that reports errors? Send your customers to this page rather than bundling a copy. A bundled SDK becomes the version they are stuck on, and the one thing you cannot do from your side is update the file on somebody else’s server.
Your dashboard says when a server of yours is behind, and how much it matters. Every request carries the version, so that is a thing it knows rather than a thing it guesses.
0.2.0
2026-09-10updatecurrentA log field called n could hang your server.
- A field named n holding a number was expanded into an array of that length by the FiveM JSON encoder. A large one built a huge string and an infinite one never finished, which stops the resource that logged it.
- A line with no fields, or with a nested table in one, was refused by the API together with every other line in the same batch.
- Log batches were a fifth of what the API accepts, so a busy server dropped lines it did not need to.
- Timestamps now carry milliseconds, so two lines in the same second stay in the order your server wrote them.
- The SDK no longer runs in the client state, where it could never send anything and took client errors off your console.
0.1.0
2026-09-04changesThe first release.
- Error capture, log lines, batching and retry.