Installation

Put the mlr-gameplaycam folder in your resources directory (see Download and install).
Add it to server.cfg:

cfg

ensure mlr-gameplaycam

Restart the server and join. Type /gameplaycam to open the camera.

Note

There is no SQL file. Everyone can use the camera as a player. Press crew and director roles need the permissions in the next section.

#Give roles (optional)

A player gets the highest role they qualify for, by an ACE permission or by a job. The server decides; the client only receives the role name.

By permission:

cfg

# directors
add_ace group.admin mlr-gameplaycam.director allow

# a group for camera crews
add_ace group.cameracrew mlr-gameplaycam.press allow
add_principal identifier.license:xxxxxxxxxxxxxxxx group.cameracrew

By job (QBCore or ESX): list the job names in config/cl_config.lua:

lua

Config.Roles.press.jobs = { 'journalist', 'reporter', 'cameraman' }
Config.Roles.director.jobs = {}

With QBCore the job only counts while the player is on duty (Config.RoleRequireOnDuty).

Type /camrole in game to see your own role.

#Weather and time scripts

The director's scene panel overrides the time and weather on the director's own screen. A weather script keeps writing the clock, so it must be paused while the override is on. The resource does this for qb-weathersync. For another weather script, add its client events to Config.Scene.SyncDisableEvents and Config.Scene.SyncEnableEvents.

#Your HUD

The game's own HUD is hidden in cinematic mode. A HUD made by another resource is hidden through Config.Cinematic.HudIntegrations (an export call) or Config.Cinematic.HudEvents (a client event). mlr_hud is set up by default. See Integrations.