Resources

fxmanifest.lua as a form

fxmanifest.lua opens as a visual editor (Form ↔ Text). Edits are made in place, so your comments stay.

• Identity: runtime (fx_version), game, author, version, description
• Scripts per side (Shared, Client, Server). Files that don't exist are flagged not found, and a pattern shows how many files it matches.
• In-game UI (ui_page) with a Dev server / Build switch
• Files, dependencies and data files
• The add field suggests what each directive takes (Tab takes the first suggestion)

In Text mode, strings complete to what their directive takes: script paths and folder globs, pages, folder/**, resource names for dependencies, and @ox_lib/init.lua.

What runs where

K3 Studio works out what runs on each side from the manifest scripts and what they require. Client modules need to be listed in files {}, while server modules need nothing. When a required file isn't loaded, an editor banner and a form card let you add it to files {} or to a side in one click.

Resources panel and details

The Resources panel lists resources by [category], and you can start, stop, restart and refresh them. You can create, rename and delete categories, and move, rename and delete resources; server.cfg is updated to match.

The details page shows:

• Events: name, side, whether the resource registers or triggers it, how many callers, and live counts
• Exports and callbacks
• Files by side
• Dependencies as a diagram
• Health: events with no handler, and runtime errors

Focus on a resource

Right-click a resource and choose Focus. The explorer, search, problems, console and Git changes then only show that one folder, while the server and Live stay whole. The status bar shows a pill while focus is on, and Esc leaves.

New resource

The new resource wizard has templates for Lua, Lua + ox_lib, Qbox and ESX, and can add the ensure line for you.

Generate documentation

Run › Generate documentation writes one HTML page for a resource, a category or the whole server.