Troubleshooting
Common issues and implementation notes for gcm_pedSystem.
/pedmenu says no permission
Possible Causes
- Player group is not included in
Config.GroupPermissions. - ACE permissions are not configured.
- Framework group lookup is returning default user role.
Fix
- Add your staff role to
Config.GroupPermissions. - Validate ACE permissions for admin roles.
- Confirm framework player group is assigned correctly.
Player forced PED is not applied on login
Possible Causes
- No
forzarSpawn = trueentry exists in player's saved PED list. - DB row for player is missing.
- Player-load integration event is not firing.
Fix
- Set forced PED from admin panel.
- Verify
gcm_pedshas player row and valid JSON. - Confirm configured framework load event names in
Config.Triggers.
PED model is rejected
Possible Causes
- Invalid model name/hash.
- Model streaming timed out in client validation step.
Fix
- Validate model exists in GTA assets.
- Retry with a known valid PED model.
Discord logs are not sent
Possible Causes
Config.Logs.enableisfalse.- Webhook values were not replaced.
Fix
- Enable logs in config.
- Replace webhook values with real URLs.
Implementation Risk Notes
Event Namespace Mismatch
Client load handler triggers gcm_securezone:client:PlayerLoad instead of a PED-specific event name, which is functional but easy to misread and break during refactors.
Recursive PED Reapply Loop
gcm_pedSystem:setearPedDefault can recursively trigger itself when model verification fails repeatedly, which may cause repeated retries under bad model/network conditions.