Quasar Store Logo

Commands and Exports

This section lists all available commands, exports, and events included in the script. You’ll find client-side, server-side, and shared functions designed to help developers integrate, extend, or interact with the system easily within their own scripts or frameworks.

Commands

This section lists all available commands included in the script. Each command is designed to simplify administration, player interaction, or debugging tasks. You’ll find detailed descriptions, usage examples, and permission requirements to help you manage and customize your server efficiently.

CommandDescription
/jobOpen multijob player menu.





Server Exports

This section provides all available server exports for the script. These functions allow developers to interact with the system from the server side, manage data, trigger actions, and integrate with other resources. Each export includes a clear description and a practical example to simplify its implementation.

FirePlayerFromJob

This export removes a specific job from a player within the multijob system. When executed, it looks up the player using their source, accesses their list of jobs, and deletes the specified job (in this case 'police'). It does not handle UI updates or notifications by itself—any client refresh or database sync depends on how the resource is implemented internally. It’s typically used for firing systems, faction management, or automated job cleanup.



exports['qs-multijob']:firePlayerFromJob(source, 'police')
FirePlayerFromJobOffline

This export removes a specific job from a player who is offline within the multijob system. Instead of using a live source, it uses the player’s persistent identifier (license, steam, etc.) to locate their data in the database and delete the specified job (in this case 'police'). It does not trigger any client-side updates since the player is not connected; changes will apply the next time they log in.



exports['qs-multijob']:firePlayerFromJobOffline(identifier, 'police')