Troubleshooting

Common issues and implementation notes for gcm_pausemenu.

Possible Causes

Keymapping is not registered as expected.
Player is not loaded (LocalPlayer.state.isLoggedIn false in QB).
Another UI keeps NUI focus locked.

Fix

Rebind keymapping for pausemenu in client settings.
Confirm player load state and framework detection.
Close conflicting NUI resources and retry.

Data panel shows empty name/job/money

Possible Causes

Framework object not detected.
Framework-specific player data is unavailable at open time.

Fix

Confirm qb-core or es_extended is started before this resource.
Open menu after full character load.

Disconnect action kicks with unexpected text

Possible Causes

Config.ServerName not customized.

Fix

Set a production-friendly Config.ServerName value in config.

Implementation Risk Notes

Command and Keymapping Name Mismatch

The command is registered as pauseMenu but keymapping references pausemenu, which can cause confusion when remapping or debugging.

Typo in Config Key

Config.Buttoms is used intentionally in code; renaming it in config without refactoring code will break button rendering.