Console messages - Element Labs

The server console is the first place to look when something is wrong. This page lists the messages Element Labs products print, and where each one leads.

Contract

Messages have a fixed shape:

[WARN ] [    Config] Config file for "controls" missing or invalid.

Part	Meaning
`[WARN ]`	The level. One of `INFO`, `WARN`, `ERROR`, `DEBUG`.
`[ Config]`	The channel: the part of the product the message came from. Padded to a fixed width.
The rest	The message.

Levels mean what they say: INFO records something that happened, WARN reports something that may need attention, ERROR reports something that went wrong. DEBUG is diagnostic detail and is hidden unless you enable it. See Server settings. Messages naming a product resource, such as element_map, come from that product. Everything else comes from the shared behaviour and applies to every product.

Inputs

The channels you can see without enabling debug output:

Channel	Covers
`Dependencies`	Whether the SDK is present, running and a version the product accepts.
`Config`	Reading and converting the files in `configs`.
`Locales`	Reading the files in `locales`.
`VersionCheck`	Comparing your installed versions against published releases.
`Keybinds`	Registering keys a player can rebind.

Outputs

Messages that record normal operation. No action needed.

Message	Meaning
`[<namespace>] migrated config v1 → v2.`	A configuration file you restored from an earlier release was converted to the shape this release expects. The file on disk is unchanged.

Errors

Start-up is blocked

Each of these stops the product before it does anything.

Message	Cause	Fix
`Missing dependency 'element_sdk' (requires <version>).`	The SDK is not installed, or the server does not know about it.	Install it, and add it to `server.cfg` before the product. Install a product
`Dependency 'element_sdk' is not started (state '<state>', requires <version>).`	The SDK is installed but not running: it failed to start, or it was stopped.	Look further up the console for the SDK’s own failure.
`'element_sdk' v<installed> does not satisfy required version <version>.`	The installed SDK is outside the range this product accepts.	Update the SDK. SDK version requirements
`Declared requirement '<constraint>' for '<name>' is not a readable version constraint.`	The requirement in the product’s own `fxmanifest.lua` cannot be read: the file was edited, or the product was copied incompletely.	Reinstall the product from the release. SDK version requirements
`[Sdk] Resource dependencies are not satisfied for '<resource>'.`	Follows any of the four above, naming the product that stopped.	Fix the line above it.
`No supported Framework adapter detected. Checked: [es_extended, qb-core, qbx_core]`	The product needs a framework and none is running. The same shape appears for inventories, databases, menus and text input. A server capability stops the resource; a client one reports in the player’s own console and the product keeps running.	Install one of the listed resources and start it before the product. Supported server resources
`'<capability>' is unavailable for the rest of this session; …`	Follows the line above on the client, where a resource cannot stop itself.	Same fix. Supported server resources
`The declared Framework adapter in "<resource>" is missing: [<methods>]. A declared adapter must implement the whole contract.`	A resource declared `element_adapter '<capability>'` in its `fxmanifest.lua`, but its `elementAdapter` export returned a table that does not implement every method of the contract.	Implement the methods the message names in that resource. A provider of your own
`Resource "<resource>" declares "<capability>" but does not export "elementAdapter".`	The manifest declares an adapter, but the resource never registers the `elementAdapter` export.	Add the export to that resource’s Lua. A provider of your own
`Resource "<resource>" returned nothing from "elementAdapter" for "<capability>".`	The export exists but returned nothing for that capability, usually a branch on the capability name that did not match.	Make the export return the implementation for the capability the manifest declares. A provider of your own

Start-up continues, but something is wrong

Message	Cause	Fix
`Config file for "<namespace>" missing or invalid.`	That configuration file cannot be read. Every setting in it falls back to the value the release shipped.	Correct the syntax, usually a trailing comma or a missing bracket. Configuration changes have no effect
`Config file for "<namespace>" declares scope "<a>" but the release owns it as "<b>"; the scope cannot be changed by editing the file.`	`scope` was edited. It records which side owns the namespace; it does not decide it, so nothing moved.	Put `scope` back as shipped. Configuration
`Config file for "<namespace>" declares namespace "<other>"; the filename decides the namespace.`	`namespace` was edited, or the file was renamed and the field was not.	Make the field match the filename. Configuration
`[<namespace>] missing migration step from v1 → v2; falling back to defaults.`	A configuration file from an earlier release could not be converted. The release defaults are in use.	Rewrite your settings against the current file. Update a product or the SDK
`[<namespace>] migration step v1 → v2 threw; falling back to defaults.`	The conversion was attempted and failed. The release defaults are in use.	As above. Report it if it repeats. Getting help
`[<namespace>] config file from newer version (3 > 2); some keys may be ignored.`	Your configuration file comes from a newer release than the product reading it.	Roll the configuration back to match the product, or update the product.
`Locale file for "<language>" is missing or invalid.`	That language file is absent or cannot be read. Every piece of text falls back to the fallback language.	Check the file exists in `locales` and parses. Text is wrong or missing
`Cannot determine version of 'element_sdk' (requires <version>).`	The SDK is running but its version cannot be read, usually an incomplete copy.	Reinstall the SDK.
`Release catalog request failed with status <n>.`	The update check could not reach the release catalogue. Status `0` usually means the request never left the machine.	Nothing is broken. Turn the check off if your server has no outbound access. Server settings
`Release catalog response is invalid.`	The catalogue was reached but could not be read.	Nothing is broken. It is retried at the next start.
`<resource> is outdated: v<a> installed, v<b> available.`	A newer release exists.	Informational. Update a product or the SDK
`Skipped "<name>", keybinds are unsupported on RedM.`	A product that registers a key was started on a RedM server. Element Labs products are built for FiveM.	Not supported. Server requirements
`"<name>" is already registered, returning existing binding.`	Two keys were registered under the same name, usually a product restarted while its client was connected, or two resources chose the same name. The key registered first keeps working; the second registration is ignored. It appears in the player’s own console, not the server’s.	Nothing to do if the key responds. If it triggers the wrong action, the two resources chose the same name and one of them has to change it.

Messages from Element 3D Map

Message	Cause	Fix
`[Map] Blip coordinates require numeric x and y components.`	Another resource asked the map to add a marker without usable coordinates.	The calling resource is at fault. Exports

Example

A complete failed start, read from the top:

[ERROR] [Dependencies] 'element_sdk' v0.1.0-alpha.1 does not satisfy required version ^0.1.0-alpha.3.
[Sdk] Resource dependencies are not satisfied for 'element_map'.

The first line is the cause and the second names the resource that stopped. Always act on the highest line: the ones below it are usually consequences.

​Contract

​Inputs

​Outputs

​Errors

​Start-up is blocked

​Start-up continues, but something is wrong

​Messages from Element 3D Map

​Example

​Related