Events

All events on this page are client-side and local to the client. Use AddEventHandler to listen and TriggerEvent to raise.

Raised by the map

Event	Arguments	When
`el:pausemenu:ready`	none	The map’s client side has finished loading and its exports are callable.
`el:pausemenu:open`	`view: string`	The map has begun opening, on that view. The camera transition has not finished yet.
`el:pausemenu:close`	none	The map has closed and the camera has returned.
`el:pausemenu:view:enter`	`view: string`	A view is on screen. Raised with `el:pausemenu:open`, and again after a `SwitchView`.
`el:pausemenu:view:ready`	`view: string`	The camera has arrived over that view.
`el:pausemenu:view:params`	`view: string`, `params: any`	The view’s parameters were replaced.
`el:pausemenu:view:leave`	`view: string`	That view is no longer on screen.
`el:pausemenu:stop`	none	The `element_3d_pausemenu` resource is stopping.
`el:pausemenu:page:enter`	`id: string`	A page registered with `RegisterPage` is on screen.
`el:pausemenu:page:leave`	`id: string`	A page was left, or the map closed under it.
`el:pausemenu:page:action`	`action: table`	Something in a page was used. See Pages.

Listened for by the map

Event	Arguments	Effect
`el:pausemenu:blip:meta`	`handle: number`, `fields: table`	Attaches map information to a marker created with the game’s own functions. The same as calling `SetBlipMeta`.
`el:pausemenu:blip:gone`	`handle: number`	Forgets the information attached to that marker.
`el:pausemenu:blip:new`	`handle: number`	Tells the map a marker was created, so it appears without waiting for the next sweep.
`el:pausemenu:blip:touch`	`handle: number`	Tells the map a marker has changed, so its appearance is refreshed.
`el:pausemenu:blip:pulse`	`handle: number`	Plays the marker’s pulse once, as the game’s `PulseBlip` does on its own map.
`el:pausemenu:gps:route`	`active: boolean`, `hudColour?: number`, `x?`, `y?`, `z?: number`	Tells the map a route drawn with the game’s `StartGpsMultiRoute` or `StartGpsCustomRoute` went up or came down, with its HUD colour and its last point. The map then draws the route the game is holding.

An event tells a resource what happened. The one place a resource can refuse something is the beforeOpen hook, which is asked before a view opens. See Views. The listened-for events are what the map’s integration uses. Raising them yourself is supported, and is the alternative to SetBlipMeta when your code cannot reach the export.

Arguments

The page events carry the id you gave RegisterPage. Compare against your own id: every registered page raises the same events. The fields table of el:pausemenu:blip:meta accepts the same keys as SetBlipMeta. See Exports. Repeated calls for one marker are merged.

Timing

el:pausemenu:open is raised as the map starts opening, so a handler runs before the camera has finished moving. Use it to prepare state, not to assume the map is on screen; el:pausemenu:view:ready is the one raised once it is. el:pausemenu:close is raised in every case the map stops being open: the player closed it, the player died, or the resource was stopped. It is also raised if opening failed part way through, so an el:pausemenu:open handler is always followed by an el:pausemenu:close handler. el:pausemenu:open carries the id of the view being opened, so a handler can tell the standard map from a view of its own without asking. With the game’s own map in place of the 3D map (see SetMapMode), the events are the same and carry the same view id. el:pausemenu:view:leave is raised for every view that leaves the screen, including when the map closes and when a resource stop takes it down. el:pausemenu:ready is raised once per resource start. A resource that starts after the map has already started never sees it. Use GetResourceState('element_3d_pausemenu') in that case.

Errors

None of these events report failure. An unknown marker handle is ignored, and an unregistered page id never occurs in the page events because the map only raises ids it was given.

While the map is open

The integration changes one thing in your other resources: while the map is open, the game’s pause-menu check reports that the pause menu is active. The map takes the place of the pause map, so code that pauses on the pause menu behaves the same way for the map. This applies inside every resource the integration was installed into, and only while the map is open. If a resource of yours must tell the two apart, listen for el:pausemenu:open and el:pausemenu:close and track it yourself. See Install an integration for what the integration is and how to install it.

Example

Waiting for the map to be ready, then registering a page and reacting to it:

AddEventHandler('el:pausemenu:ready', function()
  exports.element_3d_pausemenu:RegisterPage({
    id = 'jobs',
    label = 'Jobs',
    order = 2,
    content = { schemaVersion = 1, title = 'Jobs', sections = {} },
  })
end)

AddEventHandler('el:pausemenu:page:action', function(event)
  if event.page == 'jobs' and event.action == 'refresh' then
    exports.element_3d_pausemenu:SetPageContent('jobs', jobsPage())
  end
end)

The content of a page and what it reports are described in Pages. Pausing your own work while the map is open:

local mapOpen = false

AddEventHandler('el:pausemenu:open', function() mapOpen = true end)
AddEventHandler('el:pausemenu:close', function() mapOpen = false end)

Attaching information to a marker without calling the export:

local handle = AddBlipForCoord(-1037.0, -2738.0, 20.0)
TriggerEvent('el:pausemenu:blip:meta', handle, { name = 'Airport', category = 3 })

Get started

Guides

Configuration

For scripters

Troubleshooting

Changelog

Events

Events

Raised by the map

Listened for by the map

Arguments

Timing

Errors

While the map is open

Example

Get started

Guides

Configuration

For scripters

Troubleshooting

Changelog

Events

Raised by the map

Listened for by the map

Arguments

Timing

Errors

While the map is open

Example

Related