Improving script stack traces

Originally published at:

In the past, the Citizen framework scripting runtime would print really messy stack traces such as… this: Stack traces across runtimes. This stack trace goes on for around 3-4 times the displayed length, and is generally… a big mess. You can tell that some resource code is running, like @stest3/sv.lua:20, f.js:8 and @stest1/sv.lua, but everything…


This was definitely needed, thank you FiveM for making the development a better place!


doubt anyone in the LUA dev community will even know what a ‘stack’ is, learn some C normies.

Pro gamers rise up :penguin:

This is great news for us devs!