Question FiveM — Resource Thread Name Extraction for Lua Injection

[byte_corvus]

Been digging into the CitizenFX core trying to figure out a reliable way to map out resource threads. The goal is simple: targeted Lua injection into a specific thread rather than just broadcasting or hooking the standard execution flow. If you've ever tried to target a specific resource in FiveM for internal work, you've probably hit a wall trying to resolve the actual thread names properly.

The Technical Bottleneck
Working with m_runningThreads suggests you're already looking at the scheduler, but mapping those back to human-readable resource names isn't always straightforward. Most public bases just hook the main state, but for a clean internal, we need precision.

Proposed Methods

1. Scanning the Lua registry for

   LUA_TTHREAD

   objects — technically this should be the most robust way to find every state the VM is tracking.
2. Memory iteration of m_runningThreads — it's the standard path, but can be noisy depending on how the resource manager is handling cleanup.
3. Registry lookups — the idea is to find the association between the thread and the resource name stored in the manifest registry.

Spoiler: Internal Logic Thoughts

Finding the lua_State for a specific resource is usually the first hurdle. Once you have that, you can iterate the registry. The challenge is usually finding where the resource name is stored relative to the thread object in memory. If we can pull the string metadata from the resource manifest, cross-referencing it with the thread state should be the way to go.

If you've reversed the latest CitizenFX build, does m_runningThreads still hold the full list or are they obfuscating the thread manager now? Drop your findings below.