Pedify guide
Troubleshoot an invisible or crashing ped
Separate resource-loading failures from model-name, client-streaming and asset-compatibility problems. Change one thing at a time and keep a known-good copy.
The menu cannot find the model
Check the active server’s resources path and exact folder name in server.cfg. Read the console after start. Use the exported model name, including spelling and underscores. If the menu has a whitelist, check its server-side permission and model list.
The model spawns but is invisible
Test with a clean client after reconnecting so stale streamed data is not reused. Check that the resource contains the complete export set; do not move only the visible YFT and leave related textures or metadata behind. Review client F8 and server console for missing files or parse errors. Then test the untouched ZIP in a separate resource folder with only one copy of the model enabled.
The client or server crashes
Disable the ped resource and see whether the crash stops. Re-enable only that resource on a private server, review the first relevant error, and compare the files with project validation messages. Do not repeatedly restart a production server to probe a crash. If a failure follows one model or texture, retain the source files and export summary for a focused report.
Clothing, face or textures look wrong
Check that the spawned model is the one whose components you edited. Inspect each component and resolve validation errors about missing texture references or numbering before export. Test on a clean client and verify the game edition and resource format. A successful ZIP extraction is not native readback or a gameplay test.
Share useful evidence
Report the Pedify page/version, game edition, server build, export type, model name and first relevant log lines. Remove player identifiers and private server data. Do not post purchased or third-party source assets unless you have permission.
Read export error codes and next steps. Ask Pedify support on Discord. Discord